Let's back out LOADER_ZFS_SUPPORT from STABLE

[John Baldwin]

On Sunday 14 June 2009 7:08:50 pm Daniel Eischen wrote:
> On Sun, 14 Jun 2009, Dan Allen wrote:
> 
> >
> > On 14 Jun 2009, at 1:27 AM, Daniel Eischen wrote:
> >
> >> From one of your older emails, you mention you are using
> >> ad0s2a as / and ad0s2b as swap, and then say that ad0s2c
> >> is unused (I may have the ad0s2 part wrong).  But ad0s2c
> >> should be the entire slice (or partition depending on
> >> the wording you are used to).
> >> 
> >> How about posting a relevent fdisk and disklabel (or
> >> gpart show) so we can see what your slices and partitions
> >> look like (fdisk /dev/ad0, disklabel /dev/ad0s2).
> >
> > ad0s2c is the entire slice as you thought it should be.
> >
> > Here is fdisk and bsdlabel /dev/ad0s2:
> >
> > ******* Working on device /dev/ad0 *******
> > parameters extracted from in-core disklabel are:
> > cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl)
> >
> > Figures below won't work with BIOS for partitions not in cyl 1
> > parameters to be used for BIOS calculations are:
> > cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl)
> >
> > Media sector size is 512
> > Warning: BIOS sector numbering starts with sector 1
> > Information from DOS bootblock is:
> > The data for partition 1 is:
> > sysid 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX)
> >   start 63, size 188747622 (92161 Meg), flag 0
> > 	beg: cyl 0/ head 1/ sector 1;
> > 	end: cyl 1023/ head 10/ sector 63
> > The data for partition 2 is:
> > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
> >   start 188747685, size 45688860 (22309 Meg), flag 80 (active)
> > 	beg: cyl 1023/ head 255/ sector 63;
> > 	end: cyl 1023/ head 14/ sector 63
> > The data for partition 3 is:
> > <UNUSED>
> > The data for partition 4 is:
> > <UNUSED>
> >
> >
> >
> > # /dev/ad0s2:
> > 8 partitions:
> > #        size   offset    fstype   [fsize bsize bps/cpg]
> > a: 43591708  2097152    4.2BSD        0     0     0
> > b:  2097152        0      swap
> > c: 45688860        0    unused        0     0         # "raw" part, don't 
> > edit
> 
> Seems weird to see swap at offset 0 and partition a after swap.
> I wonder if that is screwing things up.  And shouldn't the offset
> for your first slice start at offset 188747685 (from fdisk)?

swap at offset 0 will probably break.  The first 16 sectors hold the BSD 
disklabel and boot code.  FFS filesystems leave the first 16 sectors unused, 
so if you let 'a' start at 0, it actually starts at 16 and you are ok.  
However, if you let swap start at 0, it actually uses sector 0 and the first 
time you swap you will trash your filesystem label (yes, this arrangement is 
exceedingly lame).  You could fix this by either letting 'a' come first or 
changing the swap to start at sector 16 instead of 0.

-- 
John Baldwin