Our bootloader implementation does not know how to read gang blocks.
Compare the code from OpenSolaris' variant of grub with what we have
and find the differences:
Search for zio_read_data here:
http://bitbucket.org/osunix/osunix-gate/src/1cca4617b3a8/usr/src/grub/grub-0.97/stage2/fsys_zfs.c
And compare with our zio_read here:
http://fxr.watson.org/fxr/source/boot/zfs/zfsimpl.c?im=excerpts#L900
We seem to be missing gang block check. That would explain why zfsboot
works only sometimes. If all the files are written using regular
blocks, then we're OK. However, some time later (i.e. during upgrade
or after an edit), some data can end up written to disk in a gang
block and that would make zfsboot choke.
--Artem
On Fri, Sep 25, 2009 at 1:57 PM, Stefan Bethke <stb@lassitu.de> wrote:
> Am 25.09.2009 um 17:41 schrieb Ollivier Robert:
>
>> According to Ollivier Robert:
>>>
>>> By popular demand:
>>> http://www.keltia.net/howtos/zfsboot
>>
>> I've succeeded in booting off raidz!
>>
>> There is a remaining issue with /boot/loader getting zfs errors at boot
>> time
>> resulting in loader.conf not being read. After setting the various
>> variables
>> manually (vm.kmem_size, vfs.root.mountfrom) and loading zfs, it works...
>>
>> http://static.keltia.net/download/raidz-boot.png
>>
>> I've updated the howto to reflect that.
>>
>> Any help in tackling the last issue is welcome.
>
> In my various experiments, I sometimes got a setup that would load many, but
> not all files. However, re-running the script to re-create the zpool, or
> copying files to the filesystem would make any successive reboots not work
> anymore.
>
>
> Stefan
>
> --
> Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
>
>
>
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>