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/
This archive was generated by hypermail 2b29 : Fri Nov 15 2002 - 22:00:23 EST