https://bugzilla.kernel.org/show_bug.cgi?id=201685 James Courtier-Dutton (James@xxxxxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |James@xxxxxxxxxxxxxx --- Comment #118 from James Courtier-Dutton (James@xxxxxxxxxxxxxx) --- I have not observed the problem, but I have been thinking of maybe a more reliable way to detect a problem. btrfs has a "scrub" command that essentially verifies the checksum of every file on the disk. Now, ext4 does not have such a feature (as far as I know). How about people who are seeing this problem, do a recursive sha1sum -b of every file on the disk while in a known good state, and then do a sha1sum -c of every file on the disk to see which ones got corrupted. This might help when doing git bisect and checking that we are back to a known good file system, and in cases like comment #116, item 2. Also, I think there is a way to force a reboot to a particular kernel, using grub, so one could script and git bisect, reboot to old working kernel, fsck, then reboot to problem kernel and start next git bisect all using automated scripts. Anyway, just ideas. -- You are receiving this mail because: You are watching the assignee of the bug.
