unclean unmount during shutdown/reboot

[tekkenlord]

I am using Kubuntu 10.04 64-bit and have disabled plymouth in order to see what exactly is going on during
startup/shutdown.

Almost everytime I shutdown/reboot my computer I see the following msg:

Unmounting weak filesystems...
mount :/ is busy

and then the computer shuts down.

On startup, I receive the msg that the drive (sda1 in my case) needs to be recovered.

I found a similar report here:

https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/616287

but applies to the 10.10 release, which is why I decided to file a report for Lucid.

I am worried that this can cause data corruption or loss. Please also note that many users may be unaware of the problem since most have plymouth enabled (therefore there are no msgs appearing during shutdown)

Please let me know if you need any more information. Thanks.

Description: Ubuntu 10.04.1 LTS
Release: 10.04

[tekkenlord (linuxfever)]

Need to mention that problems started when I installed KDE 4.5, did not have any unmounting problems with 4.4.2. I have also filed a report to KDE:

https://bugs.kde.org/show_bug.cgi?id=248539

Now, if I boot in recovery mode, drop to root console with network and login to my desktop from there, then shutdown/rebooting is clean and all devices are unmounted properly. Is that any helpful?

I attach an output of "lsof" taken right before the unmounting takes place.

[tekkenlord (linuxfever)]

I also found out that it is not necessary to drop to root shell. You can also choose "resume normal boot", login and start KDE.

[Bud Rogers (budr)]

I can confirm this bug. running kubuntu lucid with kde 4.5.0 from launchpad.

[ 2.979045] EXT4-fs (sda3): INFO: recovery required on readonly filesystem
[ 2.979049] EXT4-fs (sda3): write access will be enabled during recovery
[ 6.303769] EXT4-fs (sda3): orphan cleanup on readonly fs
[ 6.303776] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1606559
[ 6.303867] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1594128
[ 6.303897] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1606536
[ 6.303915] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1593843
[ 6.303953] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1594187
[ 6.303969] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1606439
[ 6.303978] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1606438
[ 6.303987] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1606510
[ 6.303996] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1606512
[ 6.304022] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1606516
[ 6.319997] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1604596
[ 6.320026] EXT4-fs (sda3): ext4_orphan_cleanup: deleting unreferenced inode 1604598
[ 6.320040] EXT4-fs (sda3): 12 orphan inodes deleted
[ 6.320043] EXT4-fs (sda3): recovery complete
[ 6.558636] EXT4-fs (sda3): mounted filesystem with ordered data mode

[Bud Rogers (budr)]

Should have added that I'm running lucid 32 bit.

[Jonathan Wiltshire (jwiltshire)]

Assigning to the sysvinit package, and setting confirmed since it is experienced by more than one reporter.

[Corrado Mella (c-mella)]

It's happening to me too, since upgrading KDE to 4.5 from Kubuntu's backports PPA.

Since upgrading to 4.5, I have no graphic screen on shutdown, only the text console, and I can see the
[..]
mount: / is busy
[..]
just before shutdown.

It causes a recovery on boot
[..]
Sep 15 08:51:25 Satellite kernel: [ 2.944822] EXT3-fs: INFO: recovery required on readonly filesystem.
Sep 15 08:51:25 Satellite kernel: [ 2.944825] EXT3-fs: write access will be enabled during recovery.
Sep 15 08:51:25 Satellite kernel: [ 7.186038] kjournald starting. Commit interval 5 seconds
Sep 15 08:51:25 Satellite kernel: [ 7.186055] EXT3-fs: recovery complete.
Sep 15 08:51:25 Satellite kernel: [ 7.186835] EXT3-fs: mounted filesystem with ordered data mode.
[..]

This is serious, please press for a solution ASAP.

[tekkenlord (linuxfever)]

Corrado, can you plese try the following?

1) Turn on your computer
2) When you get to kdm, switch to virtual terminal ( Ctrl+Alt+F1 )
3) type sudo restart kdm
4) Login to KDE
5) and thest whether reboot/shutdown works fine now

thanks

[Corrado Mella (c-mella)]

The suggested workaround is effective, but just for that specific session.

During shutdown, the text console appears briefly, and then the Plymouth shutdown graphic screen stays on with the dots "counting" down until power off. This has always been the behaviour on shutdown since a fresh 10.04 install with the stock KDE 4.4.x coming with the Kubuntu CD ISO.

No
[..]
mount: / is busy
[..]
can be seen in the brief flash of the text console.
No trace of an unclean shutdown on reboot, ext3 loads clean immediately.

BUT a subsequent shutdown/restart cycle brings back to the same scenario.

No Plymouth graphic shutdown "countdown", only text console output, and the
[..]
mount: / is busy
[..]
is back, with an ext3 recovery on the next boot.

Does that help pinpointing where the problem lies?

[tekkenlord (linuxfever)]

The way to make this workaround permanent is to add "restart kdm" to "/etc/rc.local".

Also tried this with gnome (restart gdm) and also works!

[tekkenlord (linuxfever)]

After yesterday's updates ( including many of the kde packages and a new kernel version (2.6.32-25) ), I do not seem to have this problem anymore. Anyone else noticed that?

[Thomas Meyer (thomas--meyer)]

Yes, I noticed it too. I have an Ubuntustudio 10.04 installation with gnome. With the newest updates and the 2.6.32-24 lowlatency kernel, the problem disappeared. Unfortunately, the newer lowlatency, preemtitive and rt-kernels produce a sizzling noise when playing sound with my m-audio audiophile 2496 soundcard. So I cannot use them for my purposes.

[Gard Spreemann (gspreemann)]

tekkenlord: Adding restart kdm doesn't solve the problem for me. Are you sure it does for you? I mean, are you certain you didn't just immediately reboot to test it? If possible, try using the system for a few days with your workaround in place and see if the problem persists.

[tekkenlord (linuxfever)]

Well, I have removed the workaround ever since the updates (see comment #10). Nevertheless, I was using the workaround in 3 different computers for about a week and the problem never occured again.

[Gard Spreemann (gspreemann)]

tekkenlord: Ah, oops, I must have mixed up this bug report with the one for 10.10 (#616287). I'm running 10.10 and am still seeing the problem. I'll comment there instead. Sorry :-)