Date: Thu, 28 Oct 1999 08:30:54 +1000 From: Brendon Meyer <Brendon_Meyer@fmi.com> To: "Kenneth D. Merry" <ken@kdm.org> Cc: Don <don@calis.blacksun.org>, Bernd Walter <ticso@cicely.de>, Greg Lehey <grog@lemis.com>, Alfred Perlstein <bright@wintelcom.net>, freebsd-fs@FreeBSD.ORG Subject: Re: Journaling Message-ID: <38177D1E.56435DBE@fmi.com> References: <199910272138.PAA11180@panzer.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--------------FFF05FC985896B3780AEFBC8 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Kenneth D. Merry" wrote: > Don wrote... > > > The Limit of 7 partionions is not of any interest if you use vinum. > > > Vinum should be able to manage in 1 partion more volumes than you will want. > > Ok nevermind :) Either way vinum is not up to snuff. It still has a way to > > go before it can be used in a production environment. My question then > > becomes what causes the 7 (partition, mount point, slice, whatever) limit? > > FreeBSD, OpenBSD and Solaris all share this limitation. Since they only > > share UFS (AFAIK) I had assumed it was the fault of UFS. > > Actually, it's technically 8 partitions, a-h, but c is "special", and > shouldn't normally be used. > > This is a disklabel limitation, not a filesystem limitation. I believe > that Solaris x86 may be able to do 16 partitions (or so a guy at Sun told > me). Excuse the mixing of terms here but System V Release 4 and System V Release 4.2 have a VTOC (Volume Table Of Contents) which has 16 partitions/slices. Like the BSD disklabel scheme, one of the partitions is reserved to represent the entire volume. In System V Release 4 they actually used a separate slice to represent hotfixing areas as well but that appeared to be depreciated in SVR4.2. -- Brendon Meyer (Brendon_Meyer@fmi.com) PT Mineserve International / PT Freeport Indonesia / Freeport McMoran Timika, Tembagapura, Jakarta, Singapore, Cairns, New Orleans --------------FFF05FC985896B3780AEFBC8 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> "Kenneth D. Merry" wrote: <blockquote TYPE=CITE>Don wrote... <br>> > The Limit of 7 partionions is not of any interest if you use vinum. <br>> > Vinum should be able to manage in 1 partion more volumes than you will want. <br>> Ok nevermind :) Either way vinum is not up to snuff. It still has a way to <br>> go before it can be used in a production environment. My question then <br>> becomes what causes the 7 (partition, mount point, slice, whatever) limit? <br>> FreeBSD, OpenBSD and Solaris all share this limitation. Since they only <br>> share UFS (AFAIK) I had assumed it was the fault of UFS. <p>Actually, it's technically 8 partitions, a-h, but c is "special", and <br>shouldn't normally be used. <p>This is a disklabel limitation, not a filesystem limitation. I believe <br>that Solaris x86 may be able to do 16 partitions (or so a guy at Sun told <br>me).</blockquote> <p><br>Excuse the mixing of terms here but System V Release 4 and System V Release 4.2 have a VTOC (Volume Table Of Contents) which has 16 partitions/slices. <p>Like the BSD disklabel scheme, one of the partitions is reserved to represent the entire volume. <p>In System V Release 4 they actually used a separate slice to represent hotfixing areas as well but that appeared to be depreciated in SVR4.2. <br> <pre>-- Brendon Meyer (Brendon_Meyer@fmi.com) PT Mineserve International / PT Freeport Indonesia / Freeport McMoran Timika, Tembagapura, Jakarta, Singapore, Cairns, New Orleans</pre> </html> --------------FFF05FC985896B3780AEFBC8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38177D1E.56435DBE>