https://bugzilla.kernel.org/show_bug.cgi?id=23772 --- Comment #18 from Andreas Dilger <adilger.kernelbugzilla@xxxxxxxxx> 2010-11-30 20:54:18 --- (In reply to comment #17) > Something is scribbling on / has scribbled on the front of your filesystem, it > seems. I think/hope this is all old garbage that e2fsck has never cared about fixing. > 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: Right, and while it will be annoying to get this printed every day, it doesn't actually hurt any operation of the filesystem. > 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.... No, my "dd" command only zeroed out the second half of the superblock (starting at 0x600, the s_mount_opts field. It didn't touch the "error" parts of the superblock, for simplicity/safety. It should be possible to zero out these fields, even from userspace on a mounted filesystem, since the superblock is direct-mapped to the buffer. Whether you do this depends on whether the annoyance of the error message is higher than the risk that the following command might clobber your filesystem (which of course I hope it doesn't): dd if=/dev/zero of=/dev/dsk/by-label/MyBook bs=1 seek=0x17c skip=0x17c count=0x84 -- 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
