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
Opened by name withheld (Gullible Jones) - Saturday, 06 May 2006, 17:42 GMT
|
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
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?
# 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
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.