-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Which test checks for 201685 (ext4 corruption) ? #58
Comments
Last I remember, I wasn't able to get the reproducer to trigger in blktests. I was going to merge it anyways, but there was some other issue with it that I don't recall. @axboe do you remember? |
Thanks @osandov - I ask because I have a situation where I have a hard-to-reproduce problem on arm64 that smells a lot like the 201685 problem but isn't & am looking for better repro tools. |
Here is the last thing I could find if you want to try pulling out the fio job and running that: a1c4b5b |
Thanks @osandov - appreciated |
@osandov that last link has all I know, what's what I wrote when I finally managed to reproduce that issue. |
There is a comment by @axboe at
https://bugzilla.kernel.org/show_bug.cgi?id=201685#c288
to the effect that a test has been added to
blktests
to check for the ext4 file corruption issue described. Is that test in this test suite, and if so where is it?The text was updated successfully, but these errors were encountered: