Date: Wed, 29 Mar 1995 19:14:28 +1000 From: Bruce Evans <bde@zeta.org.au> To: gvrooij@mmra1.ms.philips.nl, pst@shockwave.com Cc: freebsd-bugs@freefall.cdrom.com, jkh@freefall.cdrom.com Subject: Re: kern/280: new slice manager totally confused about old slice disks Message-ID: <199503290914.TAA24895@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
> > The gratuitous kernel printfs when accessing the label are a bit much,
> > do they only happen when booting in verbose mode?
> >
> > sd0s1: start 32, end = 511999, size 511968: OK
> > sd0s4: start 512000, end = 3514367, size 3002368: OK
These printfs happen whenever a device on a sliced drive is opened and there
are no other devices on the drive open (all slice tables and labels for the
drive are forgotten - this is unfortunately currently the only mechanism for
picking up changes to the on-disk slice tables (the "DOS" partition tables
for i386ish systems)).
> > sd0: rejecting partition in BSD label: it isn't entirely within the slice
These printfs happen whenever a device on a BSD-labeled slice is opened
and the label for the slice is not already in core and there is an error.
Labels are kept in core across closes of all devices on the slice, except
they are forgotten after all devices on the drive are closed, as above.
> What exactly does this message mean? And, more important, what are its
> consequences on operation?
>Yes, the message is quite ambiguious and the printf's are debugging and
>need to go.
The error messages should have more punctuation:
> > sd0: rejecting partition in BSD label: it isn't entirely within the slice:
^
[2 more lines not quoted].
> > This is not going to be fun to support, but I have to admit that it's
> > far nicer than the old organization. Kudos to all.
It would be worse if we supported nested^N partitions within other OS's
partitions! There should only be one layer of partitioning.
Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503290914.TAA24895>