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
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
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
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.
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
, 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
Package: ifenslave-2.6
Version: 2.5
The bonding option 'packets_per_slave' remains unobserved while
configuring a bond interface.
I would like to introduce this possibility with the following patch:
--
--- ifenslave.if-pre-up.orig2014-08-22 20:42:36.436616102 +0200
+++
On Sat, 2010-08-14 at 12:05 +0100, Martin Michlmayr wrote:
* John Holland john.holl...@cellent-fs.de [2010-08-11 19:46]:
and my /etc/fstab / entry looks like:
/dev/root / ubifs defaults,noatime,ro 0 0
Is this even valid gien that /dev/root doesn't exist
I too use ubifs on a kirkwood platform: eSATA Sheevaplug.
Although the error message is annoying, it's not troublesome.
If resolving root for a specific device fails, couldn't we pick it up
from /proc/cmdline?
* Martin Michlmayr t...@cyrius.com [2010-08-07 19:50:07 -0400]
I'm sort of leaning
8 matches
Mail list logo
