Hung shutdown/reboot due to failing cifs unmount

dtjohnst · 2017-07-29 19:58:17

I suspect I'm having a similar problem as described here:

https://bbs.archlinux.org/viewtopic.php?id=198540

Except in my case it doesn't take 2 minutes, it hangs indefinitely and I have to pull the power and force a reboot. I really don't think that's ideal and I'd really rather not do it. The solutions listed were to add _netdev to the mount options, which I had already done, and to switch to netctl, which I am already using. My fstab entry is as such:

//myhost/share     /mnt/share        cifs    credentials=/etc/security/credentials,x-systemd.automount,x-systemd.device-timeout=5,_netdev,x-systemd.requires=network-online.target,rw,  0 0

I have x-systemd.requires=network-online.target in there btw because nothing else seems to ensure that I am actually online before trying to connect (and this barely works as it had to add "myhost" to my hosts file instead of just getting it from DNS - which I would prefer if anyone happens to know how to make that happen at the same time).

I figure I've just forgotten something simple and the gurus here will have it solved in 2 minutes.... Seems to always be the case.

seth · 2017-07-29 22:26:12

The device should only mount on first approach (x-systemd.automount), so "something™" will use the path in the very early boot process.
This "something™" may also be accessing the FS until a late stage of the shutdown process, blocking the umount when the network is disconnected.

dtjohnst · 2017-07-30 01:06:54

seth wrote:

The device should only mount on first approach (x-systemd.automount), so "something™" will use the path in the very early boot process.
This "something™" may also be accessing the FS until a late stage of the shutdown process, blocking the umount when the network is disconnected.

Interesting. Without the requirement of "network-online.target", it was being loaded VERY early in the boot process. Despite _netdev being there, systemd was trying to mount it before any network components. I do have one service (the deluge daemon) that is starting at boot that "require" it to be mounted (I just used a drop-in with "requires=mnt-share.mount" and "after" the same). How can I ensure this service is going down in a timely fashion, or that it should be going down BEFORE umounting is attempted?

seth · 2017-07-30 06:44:13

First try whether it's the cause. Stop the deluge service and try to shudown.
You could try to "BindsTo" either instead of "Requires" or just the network target.

dtjohnst · 2017-07-30 22:25:32

seth wrote:

First try whether it's the cause. Stop the deluge service and try to shudown.
You could try to "BindsTo" either instead of "Requires" or just the network target.

I will try modifying my deluged unit file by adding BindsTo and After to link it to my mount, although in reality I'd prefer to do it the other way around (binding my mount to deluged), but that doesn't to be allowed.

I'm not sure what the etiquette is in a case like this... Do I mark it solved and just unsolve it later if this doesn't resolve anything, or mark it pending, or testing...?

Last edited by dtjohnst (2017-07-30 23:21:06)

Arch Linux

#1 2017-07-29 19:58:17

Hung shutdown/reboot due to failing cifs unmount

#2 2017-07-29 22:26:12

Re: Hung shutdown/reboot due to failing cifs unmount

#3 2017-07-30 01:06:54

Re: Hung shutdown/reboot due to failing cifs unmount

#4 2017-07-30 06:44:13

Re: Hung shutdown/reboot due to failing cifs unmount

#5 2017-07-30 22:25:32

Re: Hung shutdown/reboot due to failing cifs unmount

Board footer