[Bug 1019347] Re: A message: "mount: / is busy" appears every time shutting down or rebooting.
tuhu
1019347 at bugs.launchpad.net
Wed Aug 1 12:25:53 UTC 2012
Hi, I was browsing on the net and found this link:
http://ubuntuforums.org/showthread.php?t=2008576 . I think my problem is
related to the "freezing plymouthd" that does not get killed on
rebooting or shutting down.
As instructed in the link, I put a bash script which content was:
#! /bin/sh
ps -Af >> process.log
in /etc/rc6.d before the "S60umountroot" script file. I opened the
"process.log" file in root directory and find this:
root 2842 2 0 18:27 ? 00:00:00 [kworker/0:3]
root 2854 1 1 18:27 ? 00:00:00 /sbin/plymouthd --mode=shutdown
root 2890 2 0 18:27 ? 00:00:00 [kworker/u:0]
I did the first solution on the link. What I did was:
1. I renamed the file of "S60umountroot" that is in /etc/rc6.d and /etc/rc0.d to "S61umountroot".
2. Created a file named "S60perso-script" and set it to be executable in /etc/rc6.d and /etc/rc0.d .
The content of the "S60perso-script" was as follows:
#! /bin/sh
### BEGIN INIT INFO
# Provides:
# Required-Start:
# Required-Stop:
# Should-Stop:
# Default-Start:
# Default-Stop: 0 6
# Short-Description: Kill freezing plymouthd
### END INIT INFO
PATH=/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
case "$1" in
start)
killall -9 plymouthd
;;
restart|reload|force-reload)
;;
stop)
killall -9 plymouthd
;;
*)
;;
esac
:
{Source: http://ubuntuforums.org/showthread.php?t=2008576 }
That's it! And, the "mount:/ busy message" does not appear again on
shutting down or rebooting. And I think the problem was not in upstart.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1019347
Title:
A message: "mount: / is busy" appears every time shutting down or
rebooting.
Status in “upstart” package in Ubuntu:
Confirmed
Bug description:
I arrived here from bug 963106
[https://bugs.launchpad.net/bugs/963106]. I thought that it was a
problem with network-manager, but it was not.
I was suggested that it is probably a problem with upstart : "that
modemmanager simply hasn't had time to complete the shutdown process
before umountroot is run. Since modemmanager is an upstart job,
sendsigs doesn't kill it."
lsb_release -rd:
Description: Ubuntu 12.04 LTS
Release: 12.04
apt-cache policy upstart:
upstart:
Installed: 1.5-0ubuntu7
Candidate: 1.5-0ubuntu7
Version table:
*** 1.5-0ubuntu7 0
500 http://kambing.ui.ac.id/ubuntu/ precise-updates/main amd64 Packages
100 /var/lib/dpkg/status
1.5-0ubuntu5 0
500 http://kambing.ui.ac.id/ubuntu/ precise/main amd64 Packages
Hope this will be fixed. Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: upstart 1.5-0ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Sat Jun 30 00:08:18 2012
InstallationMedia: Custom Live CD - Release amd64
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1019347/+subscriptions
More information about the foundations-bugs
mailing list