Am 01.11.2015 um 02:09 schrieb Brian May: > Michael Biebl <bi...@debian.org> writes: > >> That's most likely, why the device is not considered ready by >> udev/systemd, so no mount attempt is made. > > Ok. That makes sense. > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=74020 > > Sure this bug is the one you wanted to point me to? "Spontaneous Reboots" > >> and >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747629 >> might be related / the same issue. > > Yes, that does look likely. > > So if I understand correctly, something is marking SYSTEMD_READY=0 - > either rightly or wrongly - and this value doesn't change even though > the device does appear to be ready. > > Wonder if there is anyway of manually invoking the udev builtin and > checking its state? > > IMPORT{builtin}="btrfs ready $devnode" > > I also note that when it does work /dev/sdb1 still has ID_BTRFS_READY=0
So, I'm not sure if this a problem of the systemd btrfs builtin doing something stupid or if it's a kernel/btrfs bug. I don't use btrfs myself, so I don't have any experience with it. It might be worth a try to test with the lastest systemd version (v227) from unstable and if the problem is reproducible, file the but upstream. Regards, Michael
signature.asc
Description: OpenPGP digital signature
