Re: 2.5.46 ext3 errors

[Stephen Rothwell <sfr@canb.auug.org.au>]

On Wed, 6 Nov 2002 09:26:58 +0100 Jens Axboe <axboe@suse.de> wrote:
>
> On Wed, Nov 06 2002, Jens Axboe wrote:
> > Hi,
> > 
> > Doing a kernel compile, the file system suddenly turned read-only.
> > Following messages appeared in log:
> > 
> > EXT3-fs error (device ide1(22,1)): ext3_new_inode: Free inodes count corrupted in group 688 Aborting journal on device ide1(22,1).
> > ext3_new_inode: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device ide1(22,1)) in ext3_new_inode: Journal has aborted
> > EXT3-fs error (device ide1(22,1)) in ext3_create: Journal has aborted ext3_abort called.
> > EXT3-fs abort (device ide1(22,1)): ext3_journal_start: Detected aborted journal
> > Remounting filesystem read-only
> 
> fsck gave, for that group:
> 
> Free inodes count wrong for group #688 (65534, counted=0)

I got the same error, but on reboot, the journal was played and
then the fsck found no errors.

All I did on that filesystem was
	log in
	make modules_install in a kernel tree
	edit a file in the kernel tree (this file had at least two links)
	make modules - which discovered the files system read only.

After the reboot, the file was as I had changed it, so I lost nothing.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/