Message-ID: <3DD03CDC.562D7C0@digeo.com>
Date: Mon, 11 Nov 2002 15:27:24 -0800
From: Andrew Morton <akpm@digeo.com>
MIME-Version: 1.0
To: CaT <cat@zip.com.au>
CC: linux-kernel@vger.kernel.org
Subject: Re: 2.5.47 / unusual ext3 fs errors
References: <20021111231053.GA1518@zip.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1298
Lines: 28

CaT wrote:
> 
> Under 2.5.x I seem to be getting a lot of fs errors on fsck, mainly
> dealing with bad inode counts in groups. Just now though, I had /var
> remounted read-only due to the following:
> 
> t_transaction: Journal has aborted
> EXT3-fs error (device ide0(3,9)) in start_transaction: Journal has aborted
> EXT3-fs error (device ide0(3,9)) in start_transaction: Journal has aborted
> EXT3-fs error (device ide0(3,9)) in start_transaction: Journal has aborted
> ...
> EXT3-fs error (device ide0(3,9)) in start_transaction: Journal has aborted
> EXT3-fs error (device ide0(3,9)) in start_transaction: Journal has aborted
> EXT3-fs error (device ide0(3,9)) in start_transaction: Journal has aborted
> 
> And again, on reboot into single user mode and a full fsck bad inode
> count errors were present. There were no errors detected whilst testing
> the disk with -c.

There was a problem in 2.5.46 which mucked up these counters.  On disk.

2.5.47 fixed that bug, and now you have fixed the on-disk mess which 2.5.46
created, all should be well.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/