Bug#1076372: Observations, Logs, and Testing
- To: Stefan <debian@simg.de>, 1076372@bugs.debian.org
- Cc: tj.iam.tj@proton.me
- Subject: Bug#1076372: Observations, Logs, and Testing
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Tue, 10 Dec 2024 21:12:59 +0100
- Message-id: <[🔎] Z1igy8PwGyZ2zrvB@eldamar.lan>
- Reply-to: Salvatore Bonaccorso <carnil@debian.org>, 1076372@bugs.debian.org
- In-reply-to: <6d1cf56c-a8ac-4a8e-a354-aaddd739d4eb@simg.de>
- References: <172104075060.7102.3621600478475051128.reportbug@ws7> <173050557877.2947277.14281153347574216764.reportbug@sunny> <172104075060.7102.3621600478475051128.reportbug@ws7> <65e0eac0-b7e3-4586-a163-935592a3ed0e@simg.de> <172104075060.7102.3621600478475051128.reportbug@ws7> <3329850f-e92b-4c5b-b3a0-4c4be49d44f7@simg.de> <172104075060.7102.3621600478475051128.reportbug@ws7> <6d1cf56c-a8ac-4a8e-a354-aaddd739d4eb@simg.de> <172104075060.7102.3621600478475051128.reportbug@ws7>
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?
Regards,
Salvatore
Reply to: