FS#41126 - [nfs-utils] [shutdown] rpc-statd-notify.service should not run after network-online.target?
Attached to Project:
Arch Linux
Opened by Patrick Donnelly (batrick) - Monday, 07 July 2014, 19:56 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 24 February 2015, 07:46 GMT
Opened by Patrick Donnelly (batrick) - Monday, 07 July 2014, 19:56 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 24 February 2015, 07:46 GMT
|
Details
Using nfs-utils 1.3.0-3, rpc-statd-notify.service hangs if
the systemd-networkd-wait-online.service does not finish.
Using:
After=network.target nss-lookup.target instead of After=network-online.target nss-lookup.target corrects the problem. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Tuesday, 24 February 2015, 07:46 GMT
Reason for closing: Fixed
Additional comments about closing: upstream fix added to 1.3.2-4
Tuesday, 24 February 2015, 07:46 GMT
Reason for closing: Fixed
Additional comments about closing: upstream fix added to 1.3.2-4
The pertinent portions of my fstab:
192.168.1.11:/mnt/pnas/media /mnt/media nfs rw,noatime,noauto,nofail,x-systemd.automount,x-systemd.device-timeout=10,timeo=14 0 0
192.168.1.11:/mnt/pnas/music /mnt/music nfs ro,noatime,noauto,nofail,x-systemd.automount,x-systemd.device-timeout=10,timeo=14 0 0
192.168.1.11:/mnt/pnas/backups /mnt/backups nfs rw,noatime,noauto,nofail,x-systemd.automount,x-systemd.device-timeout=10,timeo=14 0 0
192.168.1.11:/mnt/pnas/watch /mnt/watch nfs rw,noatime,noauto,nofail,x-systemd.automount,x-systemd.device-timeout=10,timeo=14 0 0
Prior to this, the following would happen very consistently: systemd would hang at "Reached Shutdown Target" (if I hadn't run 'sudo umount /mnt/*' beforehand),
and wait ~1:30 before presumably killing the offending process and proceeding to actually poweroff/reboot. I just tried this modification out and it worked multiple times in a row,
with nfsiostat being used to verify before each shutdown that at least one share was indeed mounted.
Anyways, is the patch in question viable for application? Or is network-online.target preferable for some reason? If the former is the case, then I'd be happy to report this upstream. It doesn't look like any fixes have been commited for the service file in question:
http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=history;f=systemd/rpc-statd-notify.service;h=6b13b323e7585059cd526649c8dccdd70a623119;hb=HEAD
Edit: It's worth mentioning that changing network-online.target to network.target does somewhat fix the issue. NFS mounts are unmounted before shutdown, so there's no stop job, but if I boot with my rfkill switch on then I get 4 nfs mount failures in journald. nofail is a flag for all nfs mounts so it's not a huge issue, but not everyone uses those flags.