ubuntu 7.10 64bit: mount / is busy after last 11 security update: disk corruptions

Bug #161862 reported by Paolo Bernard on 2007-11-10
Affects Status Importance Assigned to Milestone
glibc (Ubuntu)
glibc (tuXlab)

Bug Description

Ubuntu 7.10 64bit version on Asus striker extreme, nvidia 100.14.19 video driver, 4Gb ram, 2 sata 500 Gb drive all on reiserfs 3.6, 1 sata dvd burner, 1 ide cd burner, 1 ide dvd burner.
I'm using the stock kernel no recompilation, no external modules except nvidia only ubuntu installed on machine.

On 6 november 2007 I did the 11 security and recomended updates for my ubuntu box, then I restarted the machine.
During the shutdown process I noticed that during the unmounting local filesystem there were a mount error for device / who said mount / is busy, then the system restarted.
After the reeboot reiserfs begin a replay of many transactions (606), the disk was corrupt.
I did it again after (restoring form previous backup), same problem at next boot (202, 304, transcations replayed).
Now I'm on backup waiting before doing again the 11 updates.

Thanks, Paolo

Paolo Bernard (berny) wrote :

I try to use sync before restarting but always I got the same errors with less transactions, even logging out from kde was not helping.

This problem is present in both the AMD64 as well as x86 version of Gutsy (I noticed it in the server installations). The problem is with the libc6 package in gutsy-updates, and I've posted an inquiry about it in the forums: http://ubuntuforums.org/showthread.php?t=646490
This problem still exists as of 1/26/08, presumably because the package is the same as when the problem was first reported.

The question I raised in the forum about this: is the unmountability of / (and subsequent fsck) a necessary evil of upgrading libc6, or is there a fixable problem with the package?

Changed in glibc (tuXlab):
status: New → Won't Fix
Changed in glibc (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers