| Summary: | systemd automatically unmounts fuse file systems with default names | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Aaron Jacobs <jacobsa> |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED NOTOURBUG | QA Contact: | systemd-bugs |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
Which version of systemd are you encountering this with? Note that there have been a number of fixes in this area in v220. Sorry, I really should have provided that info.
% systemd --version
systemd 219
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN
% uname -a
Linux ubuntu 3.19.0-16-generic #16-Ubuntu SMP Thu Apr 30 16:09:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.04
Release: 15.04
Codename: vivid
Do you have newbie instructions for updating to v220 on Ubuntu? And any links
to the bug threads or fixes you mention? Thanks!
Updating to v220 is something your distribution needs to prepare for you, you cannot do this on your own. Please ask your distribution for help on this. Thanks. Okay, thanks. Do you have any references on the fixes you mentioned, though? |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
The default name for a file system mounted using fusermount without setting the fsname option is "/dev/fuse". This interacts poorly with systemd, which appears to think that it should automatically unmount any such file system. For example, [1] is a bug thread for a fuse library whose tests are affected by this. They are flaky on Ubuntu 15.04, often seeing that the file system has been unmounted out from underneath them. This looks like the following in /var/syslog: Jun 8 06:39:41 ubuntu systemd[1]: Unit tmp-fusetest301566509.mount is bound to inactive unit dev-fuse.device. Stopping, too. Jun 8 06:39:41 ubuntu systemd[1]: Unmounting /tmp/fusetest301566509... If the tests are modified to set an fsname option, this behavior goes away. That is a fine workaround, but given the default behavior of fusermount these tests will not be the last to trip over this. I am far from a systemd expert, so I'm not confident what the correct answer is here. But at first glance it seems rude for systemd to be interfering with fuse file systems with default names. [1]: https://github.com/bazil/fuse/issues/89