FS#6498 - umount / fails after package update
Attached to Project:
Arch Linux
Opened by Pierre Schmitz (Pierre) - Tuesday, 27 February 2007, 20:49 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 27 February 2007, 21:24 GMT
Opened by Pierre Schmitz (Pierre) - Tuesday, 27 February 2007, 20:49 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 27 February 2007, 21:24 GMT
|
Details
After updating the glibc package (not sure if this problem
is related to glibc) the "umount -a" statement in
rc.shutdown fails to umount /. The script ignores this and
powers the computer off. At the next boot a lot of
transaction have to be replayed due to the unclean shutdown.
I think this is quite a critical problem because it might result in some data loss. You can reproduce this by: 1) downgrade glibc to a version from pacman-cache 2) type "poweroff" and see the failing umount before the pc turns off 3) restart and you`ll see that some transactions have to be replayed Even if this is a problem of the glibc package: rc.shutdown should never just turn the computer off when umounting a filesystem fails! |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 04 March 2007, 14:04 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 2.5-6
Sunday, 04 March 2007, 14:04 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 2.5-6
Ah, so it should just exit without shutting your system down, having killed all processes and umounted all filesystems that did umount? How would you recover from that? The only option is to reboot, having the same effect.
but what at all should happen if umount fails? isn't it enough to force "sync" before umount fails?
"