From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>, telsch <telsch@gmx.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Random csum errors
Date: Wed, 4 Aug 2021 09:07:30 +0300 [thread overview]
Message-ID: <3f14ef82-cf1b-db1e-adc5-8faa6a29698e@gmail.com> (raw)
In-Reply-To: <20210803211649.GP10170@hungrycats.org>
On 04.08.2021 00:16, Zygo Blaxell wrote:
>>
>> 1 SanDisk SDSSDA120G/Firmware Version: Z22000RL
>
> I have some of those! I can confirm they silently corrupt data as they
> approach the end of their very short lives. I've seen no evidence that
> the firmware is able to detect or report any errors before the drive dies,
> despite providing drives many opportunities to do so as they died.
>
What about adding them to
https://btrfs.wiki.kernel.org/index.php/Hardware_bugs?
prev parent reply other threads:[~2021-08-04 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 14:20 Random csum errors telsch
2021-08-02 23:38 ` Zygo Blaxell
2021-08-03 18:55 ` Aw: " telsch
2021-08-03 21:16 ` Zygo Blaxell
2021-08-04 6:07 ` Andrei Borzenkov [this message]
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=3f14ef82-cf1b-db1e-adc5-8faa6a29698e@gmail.com \
--to=arvidjaar@gmail.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=telsch@gmx.de \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).