From owner-freebsd-doc@FreeBSD.ORG Mon Sep 13 21:13:04 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BA3116A4CE; Mon, 13 Sep 2004 21:13:04 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDACC43D45; Mon, 13 Sep 2004 21:13:03 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id i8DLDkMD015011; Mon, 13 Sep 2004 14:13:47 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id i8DLDkpU015010; Mon, 13 Sep 2004 14:13:46 -0700 Date: Mon, 13 Sep 2004 14:13:46 -0700 From: Brooks Davis To: "Simon L. Nielsen" Message-ID: <20040913211346.GB11005@odin.ac.hmc.edu> References: <20040913202107.GA5175@odin.ac.hmc.edu> <20040913204958.GE766@zaphod.nitro.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0ntfKIWw70PvrIHh" Content-Disposition: inline In-Reply-To: <20040913204958.GE766@zaphod.nitro.dk> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=HTML_MESSAGE autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: doc@FreeBSD.org Subject: Re: review request: 2TB disk limit in disks chapter X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2004 21:13:04 -0000 --0ntfKIWw70PvrIHh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 13, 2004 at 10:49:58PM +0200, Simon L. Nielsen wrote: > On 2004.09.13 13:21:07 -0700, Brooks Davis wrote: > > People are starting to build disk arrays larger then 2TB and then > > finding they can't label them. I'd like to add some text like the > > following to the handbook section on adding disks. A table of >=20 > Great, documenting this is very useful! >=20 > > capabilities would probably be useful and could be an intresting project > > for someone who wanted to do a little research, but I'm specificaly > > trying to address bsdlabel at this point. > >=20 > > Please review my changes below. >=20 > All the entities should be closed, e.g. "&man.bsdlabel.8" should be > "&man.bsdlabel.8;". Doh. > > Index: chapter.sgml > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/disks/chapter.s= gml,v > > retrieving revision 1.220 > > diff -u -p -r1.220 chapter.sgml > > --- chapter.sgml 25 Aug 2004 10:33:59 -0000 1.220 > > +++ chapter.sgml 13 Sep 2004 20:14:19 -0000 > > @@ -202,6 +202,12 @@ > > case, the drive will be added simply as > > /dev/da1e. > > =20 > > + Due to the use of 32-bit integers to store the number of sec= tors,=20 >=20 > I think there is trailing whitespace on this line (unless it's just my > MUA/editor). Yah, I've fixed that here. > > + &man.bsdlabel.8, &man.disklabel.8, &man.fdisk.8, and >=20 > Isn't disklabel just a link to the local label (bsdlabel/sunlabel > etc.) now? The rest of the file seems to list both of them and the limitation applies to 4.x where there is only disklabel. I don't have a strong oppinion on this one. > > + sunlabel are all limited to 2^32-1 >=20 > You should also use a manual page entity for sunlabel. Fixed. > > + sectors. This usually translates to a 2TB limit on disk size. > > + For larger disks, &man.gpt.8 partitions may be used. >=20 > Shouldn't that be "2TB limits on partition size.", since you can AFAIR? > make multiple <2TB partitions on one "disk"(/RAID)? It's more complicated then that, which means I need to revise this documentation. In bsdlabel, the size of the disk in sectors is also recorded capping the format at 2TB. In fdisk, the format appears to limit the partition size to 2TB and the offset to 2TB so around 4TB. This doesn't work at the moment because fdisk doesn't correctly use 64-bit types internally. sunlabel appears to allow up to 16TB disks with 2TB partitions. Here's a new version. -- Brooks Index: chapter.sgml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v retrieving revision 1.220 diff -u -p -r1.220 chapter.sgml --- chapter.sgml 25 Aug 2004 10:33:59 -0000 1.220 +++ chapter.sgml 13 Sep 2004 21:12:20 -0000 @@ -202,6 +202,15 @@ case, the drive will be added simply as /dev/da1e. =20 + Due to the use of 32-bit integers to store the number of sectors + &man.bsdlabel.8; is limited to 2^32-1 sectors per disk or 2TB + in most cases. The &man.fdisk.8; format is allows a starting + sector of no more than 2^32-1 and a length of no more than 2^32-1, + limiting partitions to 2TB and disks to 4TB in most cases. The + &man.sunlabel.8; format is limited to 2^32-1 sectors per parition + and 8 partitions for a total of 16TB. larger disks, &man.gpt.8 + partitions may be used. + Using &man.sysinstall.8; --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --0ntfKIWw70PvrIHh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBRg2KXY6L6fI4GtQRAqZrAKCKSDLNzerzguVjMVocHfYp/uOL7ACdH89v lp5SG03crCtIUkM5cPPbKV4= =FwXN -----END PGP SIGNATURE----- --0ntfKIWw70PvrIHh--