Thanks for quick reply Kyle, fsck just shows a RED fail during boot check and restarts within 5 seconds, issuing a second fsck proving that it has fixed the problem. I couldn't find a log. Is there not supposed to be an fsck.log somewhere?
Anyway, I just replicated the problem and, instead of issuing a touch /forcefsck, I did a manual fsck -f in recovery mode with read-only mount (I don't know how safe this is or how close this matches a clean fsck in a pure unmount situation). Here's what I got... Pass 1: ... Pass 2: ... Pass 3: ... Pass 4: ... Pass 5: Checking group summary information /dev/hda1: ***** FILE SYSTEM WAS MODIFIED ****** /dev/hda1: ***** REBOOT LINUX ***** /dev/hda1: 24129/610432 (1.0% non-contiguous), 181696/1220932 I have manually typed this from server screen as accurately as possible. As I said, this happens with an EXT3 partition but not a REISER (I didn't check EXT2). Rgds, Vincent -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kyle McMartin Sent: 08 February 2007 15:39 To: [EMAIL PROTECTED] Subject: [Bug 83982] Re: Deleting large files corrupts EXT3 file system You didn't include the error messages fsck returned. Please include that. -- Deleting large files corrupts EXT3 file system https://launchpad.net/bugs/83982 -- Deleting large files corrupts EXT3 file system https://launchpad.net/bugs/83982 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
