Hi,
On Wed, Nov 06, 2002 at 01:43:45AM -0800, Christopher Li wrote:
> Can you put the e2image of that device to some URL I can
> download?
It's unlikely to be useful. A journal abort will cause existing
transactions to be suspended midstream, so any errors afterwards may
be due to updates which were in progress at the time and which didn't
complete. And since a fsck has been done, we've lost those errors
anyway.
Is the problem reproducible? The basic
> EXT3-fs error (device ide1(22,1)): ext3_new_inode: Free inodes count
> corrupted in group 688 Aborting journal on device ide1(22,1).
error is just ext3's normal reaction to a fatal error detected in the
filesystem, so that in itself isn't a worry. The cause of the problem
it spotted is the worry; is this reproducible?
Cheers,
Stephen
-
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 : Thu Nov 07 2002 - 22:00:42 EST