From: "Alex Xu (Hello71)" <firstname.lastname@example.org> To: email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Subject: regression: data corruption with ext4 on LUKS on nvme with torvalds master Date: Sat, 08 May 2021 13:54:39 -0400 [thread overview] Message-ID: <1620493841.bxdq8r5haw.none@localhost> (raw) In-Reply-To: <1620493841.bxdq8r5haw.none.ref@localhost> Hi all, Using torvalds master, I recently encountered data corruption on my ext4 volume on LUKS on NVMe. Specifically, during heavy writes, the system partially hangs; SysRq-W shows that processes are blocked in the kernel on I/O. After forcibly rebooting, chunks of files are replaced with other, unrelated data. I'm not sure exactly what the data is; some of it is unknown binary data, but in at least one case, a list of file paths was inserted into a file, indicating that the data is misdirected after encryption. This issue appears to affect files receiving writes in the temporal vicinity of the hang, but affects both new and old data: for example, my shell history file was corrupted up to many months before. The drive reports no SMART issues. I believe this is a regression in the kernel related to something merged in the last few days, as it consistently occurs with my most recent kernel versions, but disappears when reverting to an older kernel. I haven't investigated further, such as by bisecting. I hope this is sufficient information to give someone a lead on the issue, and if it is a bug, nail it down before anybody else loses data. Regards, Alex.
next parent reply other threads:[~2021-05-08 17:54 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <1620493841.bxdq8r5haw.none.ref@localhost> 2021-05-08 17:54 ` Alex Xu (Hello71) [this message] 2021-05-09 2:29 ` Alex Xu (Hello71) 2021-05-09 3:51 ` Jens Axboe 2021-05-09 14:47 ` Alex Xu (Hello71) [not found] <CGME20210513100034epcas1p4b23892cd77bde73c777eea6dc51c16a4@epcas1p4.samsung.com> 2021-05-13 9:42 ` Changheun Lee 2021-05-13 14:15 ` Theodore Ts'o 2021-05-13 15:59 ` Bart Van Assche [not found] ` <firstname.lastname@example.org> 2021-05-13 19:22 ` Mikulas Patocka 2021-05-13 21:18 ` Bart Van Assche 2021-05-14 9:43 ` Mikulas Patocka 2021-05-14 9:50 ` Mikulas Patocka [not found] ` <CGME20210514104426epcas1p3ee2f22f8e18c961118795c356e6a14ae@epcas1p3.samsung.com> 2021-05-14 10:26 ` Changheun Lee 2021-07-09 20:45 ` Samuel Mendoza-Jonas
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1620493841.bxdq8r5haw.none@localhost \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: regression: data corruption with ext4 on LUKS on nvme with torvalds master' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).