https://bugzilla.kernel.org/show_bug.cgi?id=23772 --- Comment #17 from Eric Sandeen <sandeen@xxxxxxxxxx> 2010-11-30 18:07:08 --- Something is scribbling on / has scribbled on the front of your filesystem, it seems. hexdumping the first 2 blocks you sent: 00000580 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 000005e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0f 00 |................| 000005f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000600 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00000660 ff ff ff ff ff ff ff 01 00 00 00 00 00 00 00 00 |................| 00000670 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000680 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 000006e0 ff ff ff ff ff ff ff ff 0f 00 00 00 00 00 00 00 |................| 00000580 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 000005e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0f 00 |................| 000005f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000600 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00000660 ff ff ff ff ff ff ff 01 00 00 00 00 00 00 00 00 |................| 00000670 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000680 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 000006e0 ff ff ff ff ff ff ff ff 0f 00 00 00 00 00 00 00 |................| 000006f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000700 ff ff ff ff 7f 00 00 00 00 00 00 00 00 00 00 00 |................| 00000710 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| superblock starts at 0x400; so here we are at offset 0x180 to 0x310 in the sb. There's a lot of "-1" (0xff) in there with a few other values. This translates into the "4294967295" values you see above. The various error tracking bits are in this part of the superblock so you're seeing the -1/4294967295 pop out in the error reporting code: __le32 s_error_count; /* number of fs errors */ __le32 s_first_error_time; /* first time an error happened */ __le32 s_first_error_ino; /* inode involved in first error */ /*1a0*/ __le64 s_first_error_block; /* block involved of first error */ /*1a8*/ __u8 s_first_error_func[32]; /* function where the error happened */ /*1c8*/ __le32 s_first_error_line; /* line number where error happened */ __le32 s_last_error_time; /* most recent time of an error */ /*1d0*/ __le32 s_last_error_ino; /* inode involved in last error */ __le32 s_last_error_line; /* line number where error happened */ __le64 s_last_error_block; /* block involved of last error */ /*1e0*/ __u8 s_last_error_func[32]; /* function where the error happened */ Your dd above should have zeroed this out, though, which makes me wonder how you got 1's back in here. It could be anything, though I wonder if it's possible that it's a stray bitmap.... What kind of storage is this? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
