Control: clone -1 -2 Control: retitle -1 Control: retitle -1 Corruption of Longsys/Kingston NVMe drive Control: retitle -2 Corruption of Lexar NM790 NVMe drive with Linux 6.5+ Control: found -2 6.11.5-1
Hi Stefan, On Tue, Dec 10, 2024 at 09:12:59PM +0100, Salvatore Bonaccorso wrote: > Hi Stefan, > > On Tue, Nov 26, 2024 at 12:58:24PM +0100, Stefan wrote: > > > > Hi, > > > > here are more test results. > > > > Configuration 1: Kingston read error in 1st M.2 socket: > > > > * I ran f3 tests in a loop for several days. The read errors with > > 6.1.112 kernel could only be reproduced one time. (f3 reported 5120 > > corrupted 512 byte sectors in one 1GB file, which is not very > > informative) > > > > Configuration 2: Lexar write errors in 1st M2 slot: > > > > * Occur with Debian 6.11.5 kernel and with unmodified (self-compiled) > > 6.11.5 kernel, but does not occur with 6.1. kernels. > > * f3 reports overwritten sectors. > > * I always tested with 500 files (= 500 GB). The last 150 or so files > > were never corrupted (overwritten). This could also explain why there > > are no file system errors, if these data are written at last (journal > > ?). > > At least for this second issue, which you can reproduce with an > upstream version reliably, can you please report it to upstream? trying to distangle both. As you can reproduce the second with Lexar NM790 NVMe reliably and with upstream versions, we would like to ask you really to report it already to upstream (keeping us in the loop so we can keep track). Regards, Salvatore
