Date: Wed, 29 Mar 1995 11:25:58 +0100 (BST) From: Paul Richards <paul@isl.cf.ac.uk> To: bde@zeta.org.au (Bruce Evans) Cc: bde@zeta.org.au, gvrooij@mmra1.ms.philips.nl, freebsd-bugs@freefall.cdrom.com, jkh@freefall.cdrom.com, pst@shockwave.com Subject: Re: kern/280: new slice manager totally confused about old slice disks Message-ID: <199503291025.LAA18458@isl.cf.ac.uk> In-Reply-To: <199503290933.TAA25301@godzilla.zeta.org.au> from "Bruce Evans" at Mar 29, 95 07:33:09 pm
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Bruce Evans who said > > >> I think sysinstall creates a valid disk label with size > >> #secpertrack * #heads * #cyl in both the d_secperunit and the 'd' partition > >> size fields. The problem occurs when the sd driver blows away the 'd' > >> partition size field (replacing it with the total #sec) without touching > >> the d_secperunit field. The wd driver is more careful and verbose. It > > >Might well explain what we see indeed. But the same holds for the c partition. > > Maybe sysinstall set the size of the c partition correctly to extend to > the end of the disk, and d_secperunit to match. Old versions of > `disklabel -e' rounded down d_secperunit to a cylinder boundary so running > `disklabel -e' could cause the problem. I doubt sysinstall is doing anything right anymore. It certainly won't be setting the c partition to cover the whole disk. It's still setting d to cover the whole disk and c to the BSD slice. -- Paul Richards, FreeBSD core team member. Internet: paul@FreeBSD.org, URL: http://isl.cf.ac.uk/~paul/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home) Dept. Mechanical Engineering, University of Wales, College Cardiff.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503291025.LAA18458>