Bug 34019

Summary:	having upgraded from 230 or 231 to 234, NFS is not unmounted when halting
Product:	Sisyphus	Reporter:	Ivan Zakharyaschev <imz>
Component:	udev	Assignee:	Alexey Shabalin <shaba>
Status:	CLOSED FIXED	QA Contact:	qa-sisyphus
Severity:	major
Priority:	P3	CC:	arseny, shaba
Version:	unstable
Hardware:	all
OS:	Linux
Bug Depends on:	34031
Bug Blocks:

Description Ivan Zakharyaschev 2017-10-16 22:26:50 MSK

This is actually quite annoying on remote machines: that they don't reboot cleanly after such an upgrade.

When changing between the two sets of releases:

# rpm -qa | fgrep 234
udev-hwdb-234-alt3.noarch
pam_systemd-234-alt3.x86_64
libsystemd-shared-234-alt3.x86_64
udev-234-alt3.x86_64
udev-rule-generator-net-234-alt3.noarch
udev-rules-234-alt3.noarch
libnss-mymachines-234-alt3.x86_64
systemd-services-234-alt3.x86_64
systemd-utils-234-alt3.x86_64
journalctl-234-alt3.x86_64
# 

and

apt> install udev=1:230-alt1.M80P.6 udev-rule-generator-net=1:230-alt1.M80P.6 systemd-services=1:230-alt1.M80P.6 libnss-mymachines=1:230-alt1.M80P.6 pam_systemd=1:230-alt1.M80P.6 systemd-utils=1:230-alt1.M80P.6 udev-rules=1:230-alt1.M80P.6 udev-hwdb=1:230-alt1.M80P.6 journalctl=1:230-alt1.M80P.6 


and then trying to reboot when an NFS is mounted, the system doesn't successfully reboot. It hangs on unmounting /space (which is NFS in my system).

This happens on a system without systemd, rather with SysV init.

If one unmounts NFS early, the reboot succeeds.

Comment 1 Repository Robot 2017-10-22 17:55:55 MSK

systemd-1:234-alt4 -> sisyphus:

Thu Oct 19 2017 Ivan Zakharyaschev <imz@altlinux.org> 1:234-alt4
- udevd.init (SysV): fix creating static device inodes (ALT: #34031).
  (Use an option introduced in v209 for "unsafe" tmpfiles actions,
  because the static devices are listed as such by kmod.)
- This also helps the unmounting of NFS when halting after having
  upgraded/reinstalled udev (& other) on a system with SysV init
  (ALT: #34019) by a lucky coincidence.