https://bugzilla.kernel.org/show_bug.cgi?id=195561 Andreas Dilger (adilger.kernelbugzilla@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adilger.kernelbugzilla@dilg | |er.ca --- Comment #7 from Andreas Dilger (adilger.kernelbugzilla@xxxxxxxxx) --- Given that the same corruption is happening across different block devices, it points to something other than the block device going bad. It might be a bug in the ext4 code, or some other kernel code that is corrupting the memory (unlikely), or a userspace process that is clobbering this block. It would be worthwhile to save a copy of the corrupted bitmap block for further analysis. It may be possible to identify what is overwriting that block by looking at the content. Collect "dumpe2fs -h" output for the filesystem, so we can see what features are enabled. Collect "dd if=/dev/sda1 of=/tmp/block.dat bs=4k count=1 skip=557056" and then dump it via "od -Ax4 -tx4 -a /tmp/block.dat". You could also potentially add a tracepoint or run blktrace to see which processes are writing to this block. It should only be the jbd2 thread. -- You are receiving this mail because: You are watching the assignee of the bug.
