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!
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!
FS#1759 - File System Corruption after System Update - Upgrade
Attached to Project:
Arch Linux
Opened by Jason Porter (jayptr) - Monday, 08 November 2004, 13:46 GMT
Last edited by Judd Vinet (judd) - Thursday, 11 November 2004, 19:21 GMT
Opened by Jason Porter (jayptr) - Monday, 08 November 2004, 13:46 GMT
Last edited by Judd Vinet (judd) - Thursday, 11 November 2004, 19:21 GMT
|
DetailsI did an install of 0.6 Widget, and the install was successful. All I installed was the base packages from the CD nothing more. After install, I then proceeded to do a system update to current so that all packages would be updated. After all packages that were newer were updated successfully I rebooted the machine. When the machine shuts down, the system is unable to unmount the file system properly. It displays busy for all mounted partitions, but proceeds to reboot anyways, resulting in file system errors that sometimes can be automatically corrected when the machines starts back up or has to be manually checked and repaired using the install/rescue cd. It doesn't matter if it is a shutdown or reboot, the result is the same. I thought at first perhaps it was a change with the kernel between 2.6.3 and 2.6.9 but leaving the kernel out of the update to current doesn’t resolve the problem. The only thing else I can think of is it has something to do with linux utilities used for mounting and unmounting, etc. I almost decided to not report this problem, but felt possible file corruption could be serious. This may not be an issue in the 0.7 beta release because the packages will be more up to date, and an update to current may not be necessary.
|
This task depends upon
Closed by Judd Vinet (judd)
Wednesday, 02 February 2005, 03:01 GMT
Reason for closing: Works for me
Additional comments about closing: Closing. Open a new bug if it happens again.
Wednesday, 02 February 2005, 03:01 GMT
Reason for closing: Works for me
Additional comments about closing: Closing. Open a new bug if it happens again.
What filesystems do you use?
My partition structure
125M /boot
1024M swap partition
renaming space /
I was using the default fstab as was configured by the install program during setup.
I installed 0.6 Widget (base only), then --sysupgrade'ed all packages. The first reboot did not successfully umount filesystems, and the ext3 had to be recovered from journal. fsck also scanned the ext3 / and ext2 /boot partitions on bootup, but that is standard for a new install, I think.
The second reboot was fine, partitions were all umounted successfully.
As a possible solution, you could edit /etc/rc.shutdown and change the block that says "Unmounting Filesystems" to be something like the following:
stat_busy "Unmounting Filesystems"
/bin/umount -a
while [ $? -gt 0 ]; do
/usr/bin/sleep 2
/bin/umount -a
done
stat_done
Note that /usr will have to be mounted to the script to use the sleep utility.
See if that loops forever, or if the script can eventually umount your filesystems.
Thanks Judd