Re: Bug#651720: new ZFS installs completely broken in Wheezy/Sid

[Steven Chamberlain <steven@pyro.eu.org>]

found 651720 src:partman-zfs/23
thanks

[adding debian-bsd@ back into Cc:]

Hi!

> Generating grub.cfg ...
> Found kernel of FreeBSD: /boot/kfreebsd-9.0-2-amd64.gz
> Found kernel module directory: /lib/modules/9.0-2-amd64
> ls: cannot access /boot/zfs/zpool.cache: No such file or directory

Maybe the zpool.cache is generated too early, and so your UFS /boot gets
mounted over the top?

If /boot had been created as a ZFS volume it wouldn't have mattered, if
its that triggered the re-creation of zpool.cache again after mounting.
 And so with any other filesystem /boot would seem empty.


There's another possibility though.  Maybe partman-zfs /actually/
creates the zpool.cache in the d-i MFS root (ramdisk), which is later
copied into the /target/boot.

I noticed some relevant code in the grub-installer script that seems to
do that:

> if [ "$bootfstype" = "zfs" ]; then
> 	# Required by update-grub on ZFS
> 	mkdir -p $ROOT/boot/zfs
> 	cp /boot/zfs/zpool.cache $ROOT/boot/zfs/
> fi

but of course that will only work where /boot itself resides on ZFS.
Maybe this needs to also match where $rootfstype is "zfs".

Regards,
-- 
Steven Chamberlain
steven@pyro.eu.org