2 ms·

To the best of my knowledge, the intention is to deprecate fstab(5) entirely in favor of automatic GPT partition discovery. Where this isn't possible, systemd-f

To the best of my knowledge, the intention is to deprecate fstab(5) entirely in favor of automatic GPT partition discovery. Where this isn't possible, systemd-fstab-generator(8) will translate the contents of fstab(5) into native systemd units (mount, automount, swap...) and henceforth the semantics will be subject to the ordering and scheduling policies of systemd itself. Mount and swap units are in theory supposed to just be wrappers to the regular system tools that merely extend them to the Unit semantics, but as a whole I'm unsurprised that these assumptions may not play well with more complex storage configurations. That's always been a recurring systemd pain point.

rogerbinns 11y ago
My frustration is that systemd isn't working in this case, that it is trying to do something pointless (check an already mounted filesystem), AND that I have no way to diagnose or correct it since there is no useful information to work with. When I had my drives on different controllers things were even worse because btrfs device scan didn't complete running before systemd then tried to mount an incomplete filesystem. Automatic partition discovery is going to have its own issues. For example plugging in a drive from another system/backups is not something you want mounted in the right places on the wrong system! fstab is also a nice place to put non-physical filesystems like tmpfs (I use it for /tmp /var/tmp $HOME/.cache $HOME/.ccache /space/work). Having to create separate .mount files for each of those would be a big pain. I really want to use and like systemd, but it does fundamentally need to work first.
- baghira 11y ago
  There is no need to create mount units, all those thing will work from /etc/fstab, which overrides the generator. And I don't think the intent is to deprecated /etc/fstab. The list of possible automounts is limited: http://www.freedesktop.org/software/systemd/man/systemd-gpt-auto-generator.html http://www.freedesktop.org/software/systemd/man/systemd-gpt-... the point really being that of having a system that can boot without /etc. I've read quite a few complaints about Ubuntu 15.04+btrfs problems, for what is worth I had no problems with Fedora22 and Opensuse Tumbleweed.

rogerbinns 11y ago

My frustration is that systemd isn't working in this case, that it is trying to do something pointless (check an already mounted filesystem), AND that I have no way to diagnose or correct it since there is no useful information to work with. When I had my drives on different controllers things were even worse because btrfs device scan didn't complete running before systemd then tried to mount an incomplete filesystem. Automatic partition discovery is going to have its own issues. For example plugging in a drive from another system/backups is not something you want mounted in the right places on the wrong system! fstab is also a nice place to put non-physical filesystems like tmpfs (I use it for /tmp /var/tmp $HOME/.cache $HOME/.ccache /space/work). Having to create separate .mount files for each of those would be a big pain. I really want to use and like systemd, but it does fundamentally need to work first.

baghira 11y ago
There is no need to create mount units, all those thing will work from /etc/fstab, which overrides the generator. And I don't think the intent is to deprecated /etc/fstab. The list of possible automounts is limited: http://www.freedesktop.org/software/systemd/man/systemd-gpt-auto-generator.html http://www.freedesktop.org/software/systemd/man/systemd-gpt-... the point really being that of having a system that can boot without /etc. I've read quite a few complaints about Ubuntu 15.04+btrfs problems, for what is worth I had no problems with Fedora22 and Opensuse Tumbleweed.