From owner-freebsd-hackers Tue Jun 30 16:30:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00154 for freebsd-hackers-outgoing; Tue, 30 Jun 1998 16:30:26 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00143 for ; Tue, 30 Jun 1998 16:30:18 -0700 (PDT) (envelope-from ian@gamespot.com) Received: from localhost (ian@localhost) by mail.gamespot.com (8.9.0/8.9.0) with SMTP id QAA26730 for ; Tue, 30 Jun 1998 16:29:58 -0700 (PDT) Date: Tue, 30 Jun 1998 16:29:57 -0700 (PDT) From: Ian Kallen To: freebsd-hackers@FreeBSD.ORG Subject: ccd & disklabel Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After ccd'ing together two of my 4 st19191n's (9 gig barracuda's), sd1 & sd2 as ccd0, I went to slice and label the other two, sd3 & sd 4, and, being lazy as I am, did it in sysinstall. Nothing seemed unusual there but when I could neither newfs those two ccd'd together, as ccd1, nor individually I looked at the disklabels. The latter two labels were totally different from the first two so, being lazy as I am, I dumped the disklabel from sd1 (which is functionally identical to sd2) and restored & edited that onto sd3 & sd4. I'm currently newfs'ing ccd1 which is built of sd3 & sd4 but this difficulty with the disklabels has me concerned. I'm using 2.2.6 on this installation though it's about to get wiped in favor of current & CAM... is it voodoo? -- Fascinating is a word I use for the unexpected. -- Spock, "The Squire of Gothos", stardate 2124.5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message