Re: Severe data corruption with ext4
From: Richard Höchenberger
Date: Mon Mar 23 2009 - 10:20:32 EST
Hi Ted, I just compiled and installed 2.6.29-rc8 vanilla. Before
running it, I booted from a live CD and fsck'd all my file systems to
get them into a consistent, clean state.
Now, after booting 2.6.29-rc8 and writing stuff to dm-14 (/usr), I again get:
----------
Mar 23 15:01:02 bakunin kernel: __find_get_block_slow() failed.
block=135274289954816, b_blocknr=0
Mar 23 15:01:02 bakunin kernel: b_state=0x00310021, b_size=4096
Mar 23 15:01:02 bakunin kernel: device blocksize: 4096
Mar 23 15:01:02 bakunin kernel: __find_get_block_slow() failed.
block=135274289954816, b_blocknr=0
Mar 23 15:01:02 bakunin kernel: b_state=0x00310021, b_size=4096
Mar 23 15:01:02 bakunin kernel: device blocksize: 4096
Mar 23 15:01:02 bakunin kernel: grow_buffers: requested out-of-range
block 135274289954816 for device dm-14
Mar 23 15:01:02 bakunin kernel: EXT4-fs error (device dm-14):
ext4_xattr_delete_inode: inode 4501: block 135274289954816 read error
----------
(the same for other inodes as well)
I've again attached the output of dumpe2fs (maybe something has
changed in the meantime..?) and an image of inode 4501.
Richard
Attachment:
itable_dm-14_usr-1.img
Description: Binary data
Attachment:
dumpe2fs_dm-14_usr-1.txt.gz
Description: GNU Zip compressed data