Your message dated Thu, 28 Jan 2016 23:58:13 +0100
with message-id <[email protected]>
and subject line Re: systemd: should reboot even it umount / fails
has caused the Debian Bug report #756725,
regarding systemd: should reboot even it umount / fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
756725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756725
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 44-11+deb7u4
Severity: normal
Today I had a server fail to restart when I ran the "reboot" command. When I
got to it I saw the following on the console:
Could not remount as read-only /: Device or resource busy
Not all file systems unmounted, 1 left.
Cannot finalize remaining file systems and devices, giving up.
Then it hung, presumably indefinitely.
I think it should do a forced reboot in that situation so that we have a usable
system. Having it hang on a "shutdown" would usually be OK but on a reboot
the sysadmin wants the system to run again.
-- System Information:
Debian Release: 7.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii dpkg 1.16.15
ii initscripts 2.88dsf-41+deb7u1
ii libacl1 2.2.51-8
ii libaudit0 1:1.7.18-1.1
ii libc6 2.19-7
ii libcap2 1:2.22-1.2
ii libcryptsetup4 2:1.4.3-4
ii libdbus-1-3 1.6.8-1+deb7u3
ii libkmod2 9-3
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.3-7.1
ii libselinux1 2.1.9-5
ii libsystemd-daemon0 44-11+deb7u4
ii libsystemd-id128-0 44-11+deb7u4
ii libsystemd-journal0 44-11+deb7u4
ii libsystemd-login0 44-11+deb7u4
ii libudev0 175-7.2
ii libwrap0 7.6.q-24
ii udev 175-7.2
ii util-linux 2.20.1-5.3
Versions of packages systemd recommends:
ii libpam-systemd 44-11+deb7u4
Versions of packages systemd suggests:
ii python 2.7.8-1
pn python-cairo <none>
pn python-dbus <none>
pn systemd-gui <none>
-- Configuration Files:
/etc/systemd/systemd-journald.conf changed:
[Journal]
SystemMaxUse=50M
ImportKernel=no
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Russel
On Fri, 01 Aug 2014 13:46:58 +1000 Russell Coker <[email protected]>
wrote:
> Package: systemd
> Version: 44-11+deb7u4
> Severity: normal
>
> Today I had a server fail to restart when I ran the "reboot" command. When I
> got to it I saw the following on the console:
> Could not remount as read-only /: Device or resource busy
> Not all file systems unmounted, 1 left.
> Cannot finalize remaining file systems and devices, giving up.
>
> Then it hung, presumably indefinitely.
>
> I think it should do a forced reboot in that situation so that we have a
> usable
> system. Having it hang on a "shutdown" would usually be OK but on a reboot
> the sysadmin wants the system to run again.
I looked at the current code [1] in src/core/shutdown. If systemd fails
to unmount partitions, it will eventually give up and continue with the
shutdown.
Since the version you reported this issue against is rather ancient and
the current code looks fine, I'm going to close this bug report.
If you still run into issue, please file a new bug report.
Regards,
Michael
[1] https://github.com/systemd/systemd/blob/master/src/core/shutdown.c#L228
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
