Bug 805252
Summary: | systemd automount seems to be broken in recent F17 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | awilliam, braden, gholms, hongjiu.lu, johannbg, kchamart, metherid, mschmidt, notting, plautrba, systemd-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-15 19:29:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Adam Williamson
2012-03-20 18:13:36 UTC
Sorry for the extremely delayed response, but no, it doesn't. That seems to be in current NM in F17: [adamw@adam ~]$ ls /lib/systemd/system/remote-fs-pre.target.wants/NetworkManager-wait-online.service /lib/systemd/system/remote-fs-pre.target.wants/NetworkManager-wait-online.service [adamw@adam ~]$ rpm -qf /lib/systemd/system/remote-fs-pre.target.wants/NetworkManager-wait-online.service NetworkManager-0.9.4.0-9.git20120521.fc17.x86_64 (so that bug should probably be closed now), but: [adamw@adam ~]$ ls /share/data/ [adamw@adam ~]$ (note the conspicuous lack of automounting). It's just broken. Has been this whole time. Is this bug specific to cifs mounts? Can you try an automount of anything else? No, and I already did: ircproxy:/ /home/adamw/irclogs nfs noauto,comment=systemd.automount0 0 [adamw@adam ~]$ ls /home/adamw/irclogs/ [adamw@adam ~]$ Both these used to work. the lack of a space between systemd.automount and 0 0 is a paste artifact, there's really a tab between them. This is still broken for me in F18. Let's look at one mount: //192.168.1.13/Volume_1 /share/data cifs rsize=8192,wsize=8192,nosuid,soft,user=guest,guest,noauto,iocharset=utf8,mapchars,comment=systemd.automount 0 0 systemd-fstab-generator seems to run on it. I have /run/systemd/generator/share-data.mount and /run/systemd/generator/share-data.automount files. content: share-data.mount ---------------- # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab DefaultDependencies=no After=remote-fs-pre.target Wants=remote-fs-pre.target Conflicts=umount.target Before=umount.target [Mount] What=//192.168.1.13/Volume_1 Where=/share/data Type=cifs FsckPassNo=0 Options=rsize=8192,wsize=8192,nosuid,soft,user=guest,guest,noauto,iocharset=utf8,mapchars,comment=systemd.automount share-data.automount -------------------- # Automatically generated by systemd-fstab-generator [Unit] SourcePath=/etc/fstab DefaultDependencies=no Conflicts=umount.target Before=umount.target remote-fs.target [Automount] Where=/share/data So that much is working. 'systemctl status share-data.mount' and 'systemctl status share-data.automount' give what looks like sane output: [root@adam irclogs]# systemctl status share-data.mount share-data.mount - /share/data Loaded: loaded (/etc/fstab) Active: inactive (dead) Where: /share/data What: //192.168.1.13/Volume_1 CGroup: name=systemd:/system/share-data.mount [root@adam irclogs]# systemctl status share-data.automount share-data.automount Loaded: loaded (/etc/fstab) Active: inactive (dead) Where: /share/data But if I do 'ls /share/data': [root@adam irclogs]# ls /share/data/ [root@adam irclogs]# nothing, at all. No error message. Nothing in /var/log/messages or journalctl. Not sure what else to look at now. 'systemctl start share-data.mount' seems to bring up the mount fine. Could you retest and confirm if you are you still experiencing this with latest systemd release in F17/F18/F19? Thanks Oh hey, I forgot I filed a bug on this. I actually came back to this yesterday and finally figured it out: all it needed was a 'systemctl enable remote-fs.target'. I have no idea how it ever got disabled, but that was all it needed. |