| From | Nix <> | Subject | Re: Apparent serious progressive ext4 data corruption bug in 3.6 (when rebooting during umount) | Date | Thu, 25 Oct 2012 12:06:42 +0100 |
| |
On 25 Oct 2012, Theodore Ts'o stated: > Also, can you reproduce the problem with the nobarrier and > journal_async_commit options *removed*? Yes, I know you have battery > backup, but it would be interesting to see if the problem shows up in > the default configuration with none of the more specialist options. > (So it would probably be good to test with journal_checksum removed as > well.)
I'm going to spend some time after work today trying to reproduce this in a virtual machine. If rebooting while umounting is truly all it takes, as it seems, this should eliminate a bunch of variables and make it a lot easier to reproduce. (Assuming Eric hasn't already done just that, that is.)
-- NULL && (void)
|