From owner-freebsd-bugs  Tue Mar 28 23:47:51 1995
Return-Path: bugs-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11277 for bugs-outgoing; Tue, 28 Mar 1995 23:47:51 -0800
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA11271; Tue, 28 Mar 1995 23:47:50 -0800
Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id XAA00441; Tue, 28 Mar 1995 23:46:57 -0800
Message-Id: <199503290746.XAA00441@precipice.shockwave.com>
To: gvrooij@mmra1.ms.philips.nl (Guido van Rooij)
cc: jkh@freefall.cdrom.com, freebsd-bugs@freefall.cdrom.com
Subject: Re: kern/280: new slice manager totally confused about old slice disks 
In-reply-to: Your message of "Wed, 29 Mar 1995 09:00:39 +0200."
             <9503290700.AA23134@mmra1.ms.philips.nl> 
Date: Tue, 28 Mar 1995 23:46:57 -0800
From: Paul Traina <pst@shockwave.com>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


  From: gvrooij@mmra1.ms.philips.nl (Guido van Rooij)
  Subject: Re: kern/280: new slice manager totally confused about old slice dis
>>ks
  > 
  > Aha, ok, this worked for me, I now understand a lot more about the slice
  > scheme (took only 30 seconds wall clock time and 1 second CPU time).
  > 
  
  I still dont get it completely. At first I thought the slices referred
  to `fdisk partition' and partitions to `BSD partitions'.
  But now I'm not sure anymore, as I saw slice 5 as well. Or do we support
  extended slices now?

Yes, and they seem to even work. :-)

  Further: I *know* 2.0R made releases where disklable would complain about
  partition c and d extending past the end of the drive (due to the total
  #sec > #secpertrack * #heads * #cyl. I guess the option to use the rest
  of the drive for a partition took all sectors left, while not checking
  the consistency of all drive params).
  How is that handled by this new scheme?

Dunno... Bruce?
  
  > I would suggest documenting the living hell out of this.
  > 
  
  Yep.
  
  > 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
  > sd0: rejecting partition in BSD label: it isn't entirely within the slice
  
  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.
  
  > 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 looks nice at first sight, but I haven't got the feeling that I completely
  understand it (yet).
  
  -Guido