Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#4585 - "filesystem busy" error on rebooting after glibc upgrade

Attached to Project: Arch Linux
Opened by name withheld (Gullible Jones) - Saturday, 06 May 2006, 17:42 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To No-one
Architecture not specified
Severity Critical
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When rebooting following a glibc upgrade, I noticed my system was claiming that it couldn't unmount / as / was busy - quite bizarre, because I had run 'sync' after the upgrade was complete. After the reboot I tried it again, and the same thing happened... And again, a third time. After installation of the new glibc package, your root filesystem will be busy (or appear so) even after syncing. I'm guessing that something about the package's install routine produces low-grade HDD activity that lasts quite a while.

(FWIW, it's not an accident that I've flagged this critical, since it could lead to data loss if there actually is activity going on. If it's not as bad as it looks it should probably be modded down.)
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 12 June 2006, 11:59 GMT
Reason for closing:  Works for me
Comment by Jan de Groot (JGC) - Saturday, 06 May 2006, 21:56 GMT
This cannot be caused by a glibc upgrade, as it doesn't leave anything running in the background after upgrading. Synching the root filesystem will not make it not-in-use, so that makes no sense. What is going on on your system is a hanging application that doesn't respond to the TERM and the KILL signals.

The only thing I can think of are NSS modules on your system other than the standard ones. Could you post the contents of /etc/nsswitch.conf?
Comment by name withheld (Gullible Jones) - Saturday, 06 May 2006, 22:06 GMT
Haven't altered anything there, and as I said, this occurs only following a glibc upgrade...

# Begin /etc/nsswitch.conf

passwd: files
group: files
shadow: files

publickey: files

hosts: files dns
networks: files

protocols: db files
services: db files
ethers: db files
rpc: db files

netgroup: db files

# End /etc/nsswitch.conf
Comment by James Rayner (iphitus) - Saturday, 06 May 2006, 23:51 GMT
run 'mount' before you shutdown and tell us what it says. This mostly occurs when there's a mount still hanging.

This isnt critical, as any processes that would be working on the partition are killed, and the kernel syncs all data to disk before shutting off.

Loading...