Den 03/05/16 kl. 20:31 skrev hasse@xxxxxxxxxxxxxxxx: > Den 03/05/16 kl. 18:30 skrev Duncan: >> Hugo Mills posted on Tue, 03 May 2016 10:27:46 +0000 as excerpted: >> >>> Given those symptoms (mount doesn't report errors, but no mount >>> happens), I would guess that your problem is with systemd. It has a bug >>> where it sometimes unmounts things immediately after you've mounted >>> them. >> >> FWIW, I have some personal experience with that "bug" myself. But I >> suspect the systemd devs might call it a "feature", not a bug. Based on >> my own experience and understanding... . . . > Thanks for the very extensive explanation. I did find out systemd did > the umount by looking in /var/log/syslog. Now I wil try to fixup systemd > unit files and I will try not boot in either rescue or emergency mode. I > believe it is fixable without it. It seems systemd thinks it is my old > LVM setup(which now are moved to btrfs) which should be used and > immediately unmounts the filesystem again because it cannot find the > "LVM device". But I must say I find it a little bit stupid that systemd > doesn't monitor /etc/fstab now that it behind the users back are > generating its own unit files (I have actually seen the mount.xxx units > etc when looking at running units...but have never looked into how it > works...so I would now have to study that) > I have found the easy solution. From https://bbs.archlinux.org/viewtopic.php?id=192991 First: # systemctl daemon-reload followed by: # systemctl restart remote-fs.target or # systemctl restart local-fs.target depending on filesystem type I still think it is pretty stupid that systemd doesn't monitor /etc/fstab (when choosing to create it own secret files) :) -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
