https://bugzilla.kernel.org/show_bug.cgi?id=32182 Eric Sandeen <sandeen@xxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sandeen@xxxxxxxxxx --- Comment #3 from Eric Sandeen <sandeen@xxxxxxxxxx> 2011-04-01 15:29:37 --- If most recent fsck doesn't find anything, but runtime finds errors, perhaps you can provide a bzip2'd e2image -r of the fileystem in question? If filenames are sensitive/private, there is an option to scramble them. That way we can see what it's finding, why it's complaining, and why fsck doesn't seem to care. It's interesting that the "bad" data is all 0s though. 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
