Bug#767893: Info received (more info)

[John Holland]

I have tested more, I realized the problem I mentioned of ZFS
filesystems going away is due to my not building them from UUIDs
instead of device names like /dev/vdb - that is, the device names are
bad because they're not consistently mapped from boot to boot.


My bug is produced in the following way:

install jessie netinst in a kvm vm, all in one partition, two spare
virtio disks to use later for zfs - minimal packages

apt-get update, apt-get upgrade

Install desktop environment (KDE, I don't like gnome 3)

(apt-get install plasma-desktop, which takes a while)

shutdown and copy disk image to backup




apt-get install linux-headers-amd64

apt-get install linux-image (version to match headers)   and chromium

browse to zfsonlinux.org

download .deb for jessie , follow instructions to install

apt-get install cryptsetup plymouth plymouth-themes

edit /etc/plymouth/plymouthd.conf so that theme = details

make sure it runs update-initramfs   (or run update-initramfs -uk all)

cryptsetup luksFormat /dev/vdb  and again for /dev/vdc

edit /etc/crypttab to:
vdbb /dev/vdb none luks
vdcc /dev/vdc none luks


cryptsetup luksOpen /dev/vdb vdbb
cryptsetup luksOpen /dev/vdc vdcc

zpool create encpool /dev/mapper/vdbb /dev/mapper/vdcc 

mkdir /mnt/b

zfs create encpool/b

zfs set mountpoint=/mnt/b encpool/b

reboot, system prompts for passwords for encrypted volumes and /mnt/b
is mounted 

zfs create encpool/varr

mv /var /oldvar

mkdir /var

zfs set mountpoint=/var enchome/varr

cp -a /oldvar/* /var/


reboot - cryptsetup prompts are overwritten and it is difficult to
enter the passwords
/var is not mounted because it has been written to already.
Manual cryptsetup and mount commands etc needed to work at this point.


John Goerzen wrote something about this at
http://changelog.complete.org/
and he said that putting the zfs var volume on mountpoint=legacy and
mounting it in  /etc/fstab would work, but it has not for me. 
What I'm finding is that any zfs entry in fstab makes the password
entry at boot impossible and if it is a filesystem that is needed to
start up this creates a lot of problems.