Date: Sun, 13 Aug 1995 21:40:42 -0400 (EDT) From: -Vince- <vince@penzance.econ.yale.edu> To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> Cc: jmb@kryten.atinc.com, msmith@atrad.adelaide.edu.au, john@zyqad.co.uk, freebsd-hardware@freebsd.org Subject: Re: Upgrade to my machine Message-ID: <Pine.LNX.3.91.950813213750.9552w-100000@penzance.econ.yale.edu> In-Reply-To: <199508122015.NAA06728@gndrsh.aac.dev.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 12 Aug 1995, Rodney W. Grimes wrote: > > > > On Sat, 12 Aug 1995, Rodney W. Grimes wrote: > > > > > > > > > > > > I hope mine is too... > > > > > > > > > > Now my question is how do you figure out what the mounting point > > > > > is for each drive? > > > > > > > > > > > > unionfs ? > > > > > > This is below the fs layer, this is _virtual_ disk type devices. You > > > end up with /dev/cdX under 4.4 lite (sic, conflicts with scsi cdrom > > > driver on many platforms :-(). On an Auspex it is /dev/vdX or is > > > that /dev/vnX, been a few months, unionfs can not do what this > > > does, and that is scatter blocks accross partitions (yes, you can > > > stripe to one disk, though that makes a very slow disk, it makes > > > it cheap to work on the code.) > > > > Now this would be neat but what will the output of df look like? > > If you have never been around a stipe disk I suppose these questions > are not out of line. However I don't have a lot of time to answer > questions at this level. This is the last one I will answer about the > fundementals of disk stripe operation. If Terry Lambert or one of the > others here cares to pick this tread up and explain what these things > are, by all means, please do, but I am not going to have time to do > that and work on any code :-(. Hopefully someone else can pick this thread off since we're very fortunate to see your contributions in the code for such a great OS on a PC platform =) > Here is what df looks like on my box when I am not playing with > stripe code: > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/sd0a 15871 11210 3391 77% / > /dev/sd0d 15871 1217 13384 8% /tmp > /dev/sd0e 15871 6522 8079 45% /var > /dev/sd0f 95311 59505 28181 68% /usr > /dev/sd0g 158863 121944 24209 83% /usr/src > /dev/sd0h 173727 137736 22092 86% /a > /dev/sd1h 475599 410211 27340 94% /b > /dev/sd2h 475599 432456 5095 99% /c > /dev/sd1a 15871 1 14600 0% /tmp2 > /dev/sd2a 15871 1 14600 0% /tmp3 > > And here is what it looks like when I have my 2 wide stripe running > on /dev/sd1a /dev/sd2a: > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/sd0a 15871 11210 3391 77% / > /dev/sd0d 15871 1217 13384 8% /tmp > /dev/sd0e 15871 6522 8079 45% /var > /dev/sd0f 95311 59505 28181 68% /usr > /dev/sd0g 158863 121944 24209 83% /usr/src > /dev/sd0h 173727 137736 22092 86% /a > /dev/sd1h 475599 410211 27340 94% /b > /dev/sd2h 475599 432456 5095 99% /c > /dev/vd0a 31742 1 29200 0% /tmp2 > > [Note, this is faked since I don't have that code compile into > the kernel on gndrsh.] My question is where does vd0a actually pick up from the other drives mounted, does it just give space when the other /dev's need it? Cheers, -Vince- vince@kbrown.oldcampus.yale.edu - GUS Mailing Lists Admin UCLA Physics/Electrical Engineering - UC Berkeley Fall '95 SysAdmin bigbang.HIP.Berkeley.EDU - Running FreeBSD, Real UN*X for Free! Chabot Observatory & Science Center
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.3.91.950813213750.9552w-100000>