From owner-freebsd-current Fri May 3 12:45:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA06839 for current-outgoing; Fri, 3 May 1996 12:45:18 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA06832 for ; Fri, 3 May 1996 12:45:13 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id MAA29103; Fri, 3 May 1996 12:44:32 -0700 (PDT) Date: Fri, 3 May 1996 12:44:32 -0700 (PDT) Message-Id: <199605031944.MAA29103@silvia.HIP.Berkeley.EDU> To: rgrimes@GndRsh.aac.dev.com CC: current@freebsd.org, ccd@stampede.cs.berkeley.edu In-reply-to: <199605031502.IAA00805@GndRsh.aac.dev.com> (rgrimes@GndRsh.aac.dev.com) Subject: Re: ccd offset, please review + test From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * And /dev/sd237c should _not_ be used. You should manually go add a * /dev/sd237a and use that for the ccd, this should eliminate your problem. For the whole slice, or with an offset? In other words, is sdXc special because of its name, or because it is the only partition that starts at the beginning? Wait, the latter doesn't make sense, all the machines here have the root filesystem starting at offset 0 (within the slice). So you're saying sdXc is special because it has the letter `c' in it? * Conventient, but wrong to do. UNIX has reserved xxYc for as long as * I can remeber, using it for file systems is a sure fire way to burn * yourself. Well I don't think that is true, the SunOS machines I was administering back in Tokyo (about 6 years ago) didn't mind us using sdXc for the whole disk. In fact, I still have a login there. :) Here it is: === >> uname -a SunOS rabbit 4.1.1-JL 1 sun4c >> df Filesystem kbytes used avail capacity Mounted on /dev/sd0a 7508 5259 1498 78% / /dev/sd0g 63956 55322 2238 96% /usr /dev/sd3c 299621 258672 10986 96% /usr/share /dev/sd1c 95421 55909 29969 65% /usr/ishare nami:/home1 299621 252019 17639 93% /amd/home/nami1 poplar:/home2 299621 97636 172022 36% /amd/home/poplar2 jay:/usr/share2 577773 501744 18252 96% /amd/vol/share2 === Note the sd3c and sd1c. These filesystems have been used this way for 7 years (I set this machine up :). BTW, here's some piece of history: === >> dmesg | grep sd sd0 at esp0 target 3 lun 0 sd0: sd1 at esp0 target 1 lun 0 sd1: sd3 at esp0 target 0 lun 0 sd3: : === (Wow :) Anyway, I just tried creating a regular filesystem on /dev/sd237c (actually sd1c, but who's counting) on our FreeBSD machine. It seems to work, are you sure it isn't supposed to? * Novice system admins should be let close to $64,000 disk arrays. :-) I meant novice to FreeBSD. :) Satoshi