Arch Linux

Description:
i have been bitten a few times by this so i enter a new bug. it is similar to  FS#16368  but not quite exactly the same though.


Every time i see the infamous message "mount: / is busy can't unmount" (from memory) at shutdown, i have the prompt CTRL-D or enter root password because fsck failed on root partition at the next boot.

so the "mount: / is busy" is a long standing "bug" that cause no harm for anybody for quite some time now. and i never had any issue with that expect it is not "clean". But now, somehow it seems to mark the / partition unclean in some way. I have switched to ext4 (upgraded from ext3) for my / partition. I had no problem for a while. and it seems this problem appearred with the next 2.6.31.

I had to reboot and make a fsck from another partition every time and it "seems" there is no corruption. It "seems" just marked unclean.

[side-note: when booting from arch live-cd. and doing a fsck right away cause *another problem*. ext4 seems very picky about date of last mount and fsck so if you did not set correctly your timezone, you get another error at next reboot: "superblock time stamp in future ! doooh]

so the issue (if can call it like that or more an annoyance) seems to be a combination of ext4 and latest kernel (for me).

i would like to hear others on this.
the mount / is busy happen when i let my pc up some days in a row with an uptime of 3 or 4 days when i shut it sdown.