ext3: i_blocks is xx, should be yy

From: Jan Niehusmann (jan@gondor.com)
Date: Sun Apr 21 2002 - 11:29:15 EST


On an (otherwise clean, and cleanly unmounted) ext3 partition, I got
some ext2fs errors like the following:

Inode 295208, i_blocks is 112, should be 8. Fix<y>?
Inode 295342, i_blocks is 8, should be 0. Fix<y>?
Inode 295343, i_blocks is 8, should be 0. Fix<y>?
Inode 295344, i_blocks is 8, should be 0. Fix<y>?
[...]

I looked up the inodes with debug2fs and noticed that all of them belong
to files which probably had failed write attemps because the fs was
full.

This happened with 2.4.18-rc2-ac1, neither the latest one nor a
'release' version, but I don't remember reading about such a problem on
linux-kernel.

Jan

-
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 : Tue Apr 23 2002 - 22:00:29 EST