Date: Fri, 7 Aug 1998 09:40:28 +0930 From: Greg Lehey <grog@lemis.com> To: djv@bedford.net, freebsd-questions@FreeBSD.ORG Subject: Re: CCD newbie Q Message-ID: <19980807094028.P9620@freebie.lemis.com> In-Reply-To: <199808061528.LAA07381@lucy.bedford.net>; from djv@bedford.net on Thu, Aug 06, 1998 at 11:28:31AM -0400 References: <199808061528.LAA07381@lucy.bedford.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 6 August 1998 at 11:28:31 -0400, djv@bedford.net wrote: > Recently, filled with ccd-zeal, I decided to give it a try, relying > upon man ccd and man ccdconfig and a fearless attitude towards a certain > disk. > > System: PPro 200, 2.2.6R, scsi disk. (Seagate st32550W on AIC-7880). > Compiled new kernel, with 4 ccd pseudo devices. > Did MAKEDEV ccd0, creating devices [r]ccd0[a-h]. Strange, there's > no ccd0 or rccd0 devices... why not? You need to make them separately. > Sliced the disk in twain, approximately 1GB each. (Not identical). > > Disklabeled the slices, with one partition (e) covering each whole > slice. -- just as if I were not about to ccdconfig them. (There was > also an unused 'c' part. of the same size.) Slice c is the "whole disk". It's always there. > newfs'd those two rsd1s[12]e partitions. (Could mount and fool with them). > > ccdconfig ccd0 0 none /dev/sd1s1e /dev/sd1s2e > > No error. > > Now what? > I eventually managed to disklabel ccd0c, one (e) partition covering > both slices. This part is verrrrrry mysterious. Why? > I could not imagine proceeding without doing this, though. Right. > I attempted to newfs this ccd0e partition, and repeatably drew an > immediate kernel panic (page fault in kernel mode). IIRC, it was > newfs /dev/rccd0e > > Hints? Well, first, where's the dump? Oh. Next, what does the ccd0 "disk label" look like? > Let's say that I restart this process with: > > dd if=/dev/zero of=/dev/sd1 bs=512 count=100 > reboot (to flush out "in-kernel disklabels" and other strangeness. > (should that be of=/dev/rsd1 ? I want to stomp it back to > "factory virgin" if possible -- no partition table, boot blox, > no nada.) Don't worry about what's on the original disks. That gets forgotten. > What should happen to result in a ccd made of two concatenated > unequal slices? I'm not sure I understand the question. I thought that's what you did. How about the last part of 'disklabel -r' for the original devices and your ccd device? The part I mean is: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 81920 344064 4.2BSD 0 0 0 # (Cyl. 240*- 297*) b: 262144 81920 swap # (Cyl. 57*- 240*) c: 4226725 0 unused 0 0 # (Cyl. 0 - 2955*) e: 81920 0 4.2BSD 0 0 0 # (Cyl. 0 - 57*) f: 1900000 425984 4.2BSD 0 0 0 # (Cyl. 297*- 1626*) g: 1900741 2325984 4.2BSD 0 0 0 # (Cyl. 1626*- 2955*) > (Yeah, I know this is strange, but it's for the > esthetic/pedagogic experience. I told a trusting soul yesterday that > this stuff worked, and (unlike my usual practice) hadn't tried it > myself first.) Well, it will. You might also like to try vinum, which you might find easier to handle. http://www.lemis.com/vinum.html. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980807094028.P9620>