You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2007-12-07 10:50:44
- arnuld
- Member
- From: INDIA
- Registered: 2005-12-19
- Posts: 220
- Website
/ is busy
on 50% of the times when I shutdown or reboot my computer, I get this message thrown at me just before the computer powers off or reboots:
mount: / is busy
Power Offand at next boot it says something like:
root system was not shutdown cleanly.
recovery-mode. read/write access will enabled during recoveryand it sucks lots of my time there and it happens lots of times. I simply use poweroff/reboot commands then why do I get this message so often. this problem started with the 1st release of Don't Panic and it is still here.
Offline
#2 2007-12-07 12:09:10
- Gilneas
- Member
- From: Netherlands
- Registered: 2006-10-22
- Posts: 320
Re: / is busy
That happens to me too, but the recovery thing only takes 1 or 2 seconds, IIRC. At least not like a disk check every 38 reboots/1xx days.
Offline
#3 2007-12-07 17:15:17
- phrakture
- Arch Overlord
- From: behind you
- Registered: 2003-10-29
- Posts: 7,879
- Website
Re: / is busy
I have a feeling some background daemon/app doesn't shut down properly. Try killing different processes and shutting down - you should be able to narrow things down
Offline
#4 2007-12-07 18:22:13
- Pierre
- Developer
- From: Bonn
- Registered: 2004-07-05
- Posts: 1,964
- Website
Re: / is busy
I had seen this issue when not exiting a chroot etc.. Anyway: the initscripts shouldn't just poweroff or reboot when a device could not be unmounted.
Offline
#5 2007-12-08 01:18:56
- mico
- Member
- From: Slovenia
- Registered: 2004-02-08
- Posts: 247
Re: / is busy
... Anyway: the initscripts shouldn't just poweroff or reboot when a device could not be unmounted.
I agree.
I had a few of those unclean shutdowns too, it was usually after a system upgrade, especially after I did the upgrade when the system was already running for some time. I don't think I ever experienced this when I did pacman -Syu right after system startup.
Offline
#6 2007-12-08 01:29:54
- delphiki
- Member
- Registered: 2007-11-17
- Posts: 66
- Website
Re: / is busy
Perhaps this is a hit or miss thing? I once upgraded two separate machines, and one of them had this strange issue, while the other continued to reboot and function normally.
Offline
#7 2007-12-08 04:10:02
- byte
- Member
- From: Düsseldorf (DE)
- Registered: 2006-05-01
- Posts: 2,046
Re: / is busy
I think the only times where I've seen this, is after a glibc upgrade ("reloading init").
1000
Offline
#8 2007-12-10 15:52:09
- arnuld
- Member
- From: INDIA
- Registered: 2005-12-19
- Posts: 220
- Website
Re: / is busy
That happens to me too, but the recovery thing only takes 1 or 2 seconds, IIRC. At least not like a disk check every 38 reboots/1xx days.
1-2 seconds ?
you are lucky then 
. for me, it eats my time, not to mention the unnecesssary frustration.
Offline
#9 2007-12-10 15:53:53
- arnuld
- Member
- From: INDIA
- Registered: 2005-12-19
- Posts: 220
- Website
Re: / is busy
I think the only times where I've seen this, is after a glibc upgrade ("reloading init").
it SURELY happens onoce when you try to reboot/poweroff after upgrade <pacman -Syu> but to me it also happens at other times. you can say in case of 15% of shutdowns.
Offline
#10 2007-12-10 17:05:11
- Rokixz
- Member
- From: Šiauliai, Lithuania
- Registered: 2007-04-21
- Posts: 251
- Website
Re: / is busy
ex.: /dev/hda3 / ext3 defaults 0 0
Try to change to sda3
http://ispconfig.lt - ISPConfig 3 based hosting. Coming Soon!
Offline
#11 2007-12-10 23:02:27
- mico
- Member
- From: Slovenia
- Registered: 2004-02-08
- Posts: 247
Re: / is busy
I don't have any /dev/hd* in /etc/fstab and still had a few of those can't remount issues.
Perhaps we should first figure out what is going on just before unclean reboot:
--- rc.shutdown 2007-12-10 23:39:44.000000000 +0100
+++ rc.shutdown.new 2007-12-10 23:38:54.000000000 +0100
@@ -111,6 +111,14 @@
stat_busy "Remounting Root Filesystem Read-only"
/bin/mount -n -o remount,ro /
+if [ $? -ne 0 ]; then
+ /bin/ps aux >>"/root/ps-aux.$(/bin/date +%Y-%m-%d)" 2>&1
+ /sbin/killall5 -15 >> "/root/sigterm.$(/bin/date +%Y-%m-%d)" 2>&1
+ /bin/sleep 5
+ /sbin/killall5 -9 >> "/root/sigkill.$(/bin/date +%Y-%m-%d)" 2>&1
+ /bin/sleep 1
+ /bin/mount -n -o remount,ro /
+fi
stat_done
# Power off or rebootThen after a failed read-only remount of / filesystem one would know which processes were running and if killall5 gave any errors. Maybe sleep time should be increased to a few minutes so data would more likely be written to disk and not just cached.
Offline
#12 2007-12-15 12:23:00
- solstice
- Member
- Registered: 2006-10-27
- Posts: 237
- Website
Re: / is busy
it happened to me a lot of time that mount: / is busy ... poweroff.
generally it got no fsck at reboot (or i didn't notice)
but sure it is rather disturbing to see that the system is being shutdown in such unsafely way...
i am getting used to it and still not have lost any data ... but ...
is it related to the problem about daemon rc files?? :
when you launch manually a /etc/rc.d/ files it is not cleanly shutdown when the pc shutdown
that's an old bug still not closed ?
or when you manually shutdown a daemon with /etc/rc.d file it is still shutdown at shutdown time while it should not ?
i have not tested that idea
Last edited by solstice (2007-12-15 12:23:34)
Offline
Pages: 1