[systemd-devel] BUG: Huge Problem: systemd does not mount all filesystems on Boot
Moin, Systemd 231, Archlinux current The concept is /home is to be mounted from nfs server. Works. For performance reasons (email thunderbird, kde/plasma 5.8.x i.e odr gnome are unusable if home is pure nfs) the user sub dirs .local, .cache, .config, .thunderbird etc. are mounts from local fs (btrfs subvolume). Network is without NetWorkmanager (masked), fixed configured via systemd-networkd. The Problem is, after boot /home is mounted or not, random result. WTF?!? The BUG is: The btrfs subvols are i.g. mounted - disobeying the x-systemd.requires=home.mount rule. I have this fstab ## Grundsystem LABEL=pc11root / btrfs rw,relatime,compress=lzo,ssd_spread,discard,space_cache,subvol=rootfs 0 0 LABEL=pc11root /vm btrfs rw,relatime,compress=lzo,ssd_spread,discard,space_cache,subvol=vm 0 0 LABEL=pc11root /pc11 btrfs rw,relatime,compress=lzo,ssd_spread,discard,space_cache,subvol=/,noauto 0 0 LABEL=swap noneswapdefaults0 0 192.168.11.10:/home/home nfs nofail,x-systemd.device-timeout=1,x-systemd.requires=network-online.target 0 0 LABEL=pc11root /home/leander/.cache btrfs ssd,ssd_spread,discard,compress=lzo,noatime,subvol=user/leander/cache,x-systemd.requires=home.mount 0 0 LABEL=pc11root /home/leander/.config btrfs ssd,ssd_spread,discard,compress=lzo,noatime,subvol=user/leander/config,x-systemd.requires=home.mount 0 0 LABEL=pc11root /home/leander/.kde4btrfs ssd,ssd_spread,discard,compress=lzo,noatime,subvol=user/leander/kde4,x-systemd.requires=home.mount 0 0 LABEL=pc11root /home/leander/.local btrfs ssd,ssd_spread,discard,compress=lzo,noatime,subvol=user/leander/local,x-systemd.requires=home.mount 0 0 LABEL=pc11root /home/leander/.thumbnails btrfs ssd,ssd_spread,discard,compress=lzo,noatime,subvol=user/leander/thumbnails,x-systemd.requires=home.mount 0 0 LABEL=pc11root /home/leander/.thunderbird btrfs ssd,ssd_spread,discard,compress=lzo,noatime,subvol=user/leander/thunderbird,x-systemd.requires=home.mount 0 0 LABEL=pc11root /home/leander/.winebtrfs ssd,ssd_spread,discard,compress=lzo,noatime,subvol=user/leander/wine,x-systemd.requires=home.mount 0 0 How to fix? mit freundlichen Grüßen Jürgen Sauer -- Jürgen Sauer - automatiX GmbH, +49-4209-4699, juergen.sa...@automatix.de Geschäftsführer: Jürgen Sauer, Gerichtstand: Amtsgericht Walsrode • HRB 120986 Ust-Id: DE191468481 • St.Nr.: 36/211/08000 GPG Public Key zur Signaturprüfung: http://www.automatix.de/juergen_sauer_publickey.gpg signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Bugreport got stuck? fstab generator/systemd.mount fails on local mounts which depend of nfs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 13.10.2015 um 18:23 schrieb Lennart Poettering: > On Tue, 13.10.15 11:01, Juergen Sauer (juergen.sa...@automatix.de) wro te: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Moin, >> this Bug is rather critical to us, but it seems to be got stuck/forgo tte >> n? >> >> https://github.com/systemd/systemd/issues/1401 > > Well, quite frankly, this is community project and the best way to > ensure that we spend our time on a bug is writing a good bug report, > that is concise, doesn't mix up tons of different issues and is to the > point, and that provides us with isolated test cases. > > Your bug report is the complete opposite of that: it's a big bundle of > chaos, with no minimal testcases, no minimal logs, no minimal > nothing. If a bug report already lists "bug 1, bug 2, bug 3" in it, > this should be indication enough that something is very wrong with > it... > > We only have limited time at our hands to work on things like this. If > we are looking for a bug to fix, and there's one bug report that gets > all this right, and one that doesn't, which one do you think we'll > pick? > > Sorry, > > Lennart Sorry Lennart, but I can only recognize, that systemd is critical broken. I proved to you follwoing Bugs: #1: systemd disobeys fstab #2: systemd does wrong mounts #3: systemd does not stop on error, if a mount fails and does not drop to debug, maintainace level "S" #4: systemd modifies a filesystem by creating directories at the wrong place. Well. What now? mit freundlichen Grüßen Jürgen Sauer - -- Jürgen Sauer - automatiX GmbH, +49-4209-4699, juergen.sa...@automatix.de Geschäftsführer: Jürgen Sauer, Gerichtstand: Amtsgericht Walsrode • HRB 120986 Ust-Id: DE191468481 • St.Nr.: 36/211/08000 GPG Public Key zur Signaturprüfung: http://www.automatix.de/juergen_sauer_publickey.gpg mit freundlichen Grüßen Jürgen Sauer - -- Jürgen Sauer - automatiX GmbH, +49-4209-4699, juergen.sa...@automatix.de Geschäftsführer: Jürgen Sauer, Gerichtstand: Amtsgericht Walsrode • HRB 120986 Ust-Id: DE191468481 • St.Nr.: 36/211/08000 GPG Public Key zur Signaturprüfung: http://www.automatix.de/juergen_sauer_publickey.gpg -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlYd+34ACgkQW7UKI9EqarFqfwCcDHAyci4+A6Dzh4p3dsOMHxUw 0KEAoNiq5gJg2epqAvsTsxdzRwIxx45A =1EYh -END PGP SIGNATURE- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Bugreport got stuck? fstab generator/systemd.mount fails on local mounts which depend of nfs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Moin, this Bug is rather critical to us, but it seems to be got stuck/forgotte n? https://github.com/systemd/systemd/issues/1401 mit freundlichen Grüßen Jürgen Sauer - -- Jürgen Sauer - automatiX GmbH, +49-4209-4699, juergen.sa...@automatix.de Geschäftsführer: Jürgen Sauer, Gerichtstand: Amtsgericht Walsrode • HRB 120986 Ust-Id: DE191468481 • St.Nr.: 36/211/08000 GPG Public Key zur Signaturprüfung: http://www.automatix.de/juergen_sauer_publickey.gpg -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlYcyHgACgkQW7UKI9EqarFfZwCeJ1i4DLODRRHStoBBMp4XdMAC n3QAoNocsueQQtMERy4AaYOE0vWN73Ub =/Ogb -END PGP SIGNATURE- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel