Bug#767893: systemd cannot mount zfs filesystems from fstab

2014-11-03 Thread John Holland
, Nov 03, 2014 at 05:51:57AM -0500, John Holland wrote: I created luks volumes, installed zfsonlinux.org packages, created a zpool out of the luks volumes. When ZFS is managing the mounting of the fs's it works. If I put a zfs filesystem in /etc/fstab the prompts to enter passwords for the luks

Bug#767893: systemd cannot mount zfs filesystems from fstab

2014-11-05 Thread John Holland
On November 3, 2014 9:36:49 AM EST, Michael Biebl bi...@debian.org wrote: Am 03.11.2014 um 15:06 schrieb John Holland: It seems like it is unable to mount a zfs volume given in fstab during boot. Strangely the presence of such an entry in fstab also seems to cause the password entry problem

Bug#767893: systemd cannot mount zfs filesystems from fstab

2014-11-12 Thread John Holland
I looked at this a little more. I found someone saying setting plymouth.conf to theme=detail would help, so I tried that. I also apt-get update'd and apt-get dist-upgrade'd. Basically, there are two issues. The prompts to enter passwords for luks encrypted volumes are mixed in with boot messages.

Bug#767893: more info

2014-11-14 Thread John Holland
filesystems and pools. This is hard to test but it really seems to be consistently happening. Rebooting with sysvinit does not have this behavior. -- John Holland jholl...@vin-dit.org gpg public key ID 0xEFAF0D15 ___ Pkg-systemd-maintainers mailing

Bug#767893: Info received (more info)

2014-11-16 Thread 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