FS#35671 - [systemd] fails to unmount CIFS network share on shutdown/reboot
Attached to Project:
Arch Linux
Opened by david (stryder) - Thursday, 06 June 2013, 07:12 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 24 December 2013, 21:05 GMT
Opened by david (stryder) - Thursday, 06 June 2013, 07:12 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 24 December 2013, 21:05 GMT
|
Details
Description:
systemd fails to umount manually mounted samba shares upon reboot/poweroff. Shutdown occurs only after a couple of minutes, probably with timeout. Same samba shares that are auto-mounted (via fstab entry) are umounted without problems. There is a short but inconclusive discussion here: https://bbs.archlinux.org/viewtopic.php?id=162236 Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: Entry in fstab to mount samba share: set to automount -> no problem; noauto, manually mounted -> poweroff/reboot takes a couple of minutes waiting for the share to be umounted. |
This task depends upon
Closed by Dave Reisner (falconindy)
Tuesday, 24 December 2013, 21:05 GMT
Reason for closing: Upstream
Additional comments about closing: Potentially fixed in 208-8, otherwise this will be fixed in a fabled v209.
Tuesday, 24 December 2013, 21:05 GMT
Reason for closing: Upstream
Additional comments about closing: Potentially fixed in 208-8, otherwise this will be fixed in a fabled v209.
## samba shares
//192.168.1.88/shuttle /media/shuttle3 cifs credentials=/root/credentials.txt,defaults,user,noauto 0 0
## nfs shares
192.168.1.88:/media/data3 /mnt/pcache nfs4 defaults,users,rsize=8192,wsize=8192,timeo=14,intr,noauto 0 0
This is a fresh install so the rest are just standard entries generated by genfstab. No problems with nfs shares. Oh, there is a vboxsf entry too in case that's relevant.
-Before=umount.target remote-fs.target
+Before=local-fs.target umount.target
Where the manual mount is missing Before=remote-fs.target, but it does have the appropriate After= ordering dependencies.
Unfortunately, I don't know much about systemd, so I left it at that. Could someone confirm this?
However, that doesn't quite fit with what you describe, as you do have a mount unit (in /run/systemd/generator) before mounting manually, so you should be getting the correct dependencies as far as I can tell...
https://bugs.freedesktop.org/show_bug.cgi?id=70002
And this was subsequently fixed in git:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=77009452cfd25