From: David Sterba <dsterba@suse.cz>
To: Chris Murphy <lists@colorremedies.com>
Cc: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
David Sterba <dsterba@suse.cz>,
Qu Wenruo <quwenruo.btrfs@gmx.com>,
Jorge Bastos <jorge.mrbastos@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Maybe we want to maintain a bad driver list? (Was 'Re: "bad tree block start, want 419774464 have 0" after a clean shutdown, could it be a disk firmware issue?')
Date: Tue, 27 Jul 2021 11:02:56 +0200 [thread overview]
Message-ID: <20210727090256.GL5047@twin.jikos.cz> (raw)
In-Reply-To: <CAJCQCtSc8x3xLKb2yyBchgvMn-0ecGi56CEDtQcFD74WyEOzUw@mail.gmail.com>
On Sat, Jul 24, 2021 at 09:34:23PM -0600, Chris Murphy wrote:
> On Sat, Jul 24, 2021 at 5:16 PM Zygo Blaxell
> <ce3g8jdj@umail.furryterror.org> wrote:
> >
> > SSDs are a different story: there are so many models, firmware revisions
> > are far more diverse, and vendors are still rapidly updating their
> > designs, so we never see exactly the same firmware in any two incident
> > reports. A firmware list would be obsolete in days. There is nothing
> > in SSD firmware like the decade-long stability there is in HDD firmware.
>
> It might still be worth having reports act as a counter. 0-3 might be
> "not enough info", 4-7 might be "suspicious", 8+ might be "consider
> yourself warned".
>
> But the scale could be a problem due to the small sample size.
That's a good idea, I've started something on
https://btrfs.wiki.kernel.org/index.php/Hardware_bugs
using the mentioned WD and firmware as first exapmle.
next prev parent reply other threads:[~2021-07-27 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 22:44 "bad tree block start, want 419774464 have 0" after a clean shutdown, could it be a disk firmware issue? Jorge Bastos
2021-07-21 17:44 ` David Sterba
2021-07-21 18:14 ` Jorge Bastos
2021-11-22 13:49 ` Jorge Bastos
2021-07-22 0:18 ` Maybe we want to maintain a bad driver list? (Was 'Re: "bad tree block start, want 419774464 have 0" after a clean shutdown, could it be a disk firmware issue?') Qu Wenruo
2021-07-22 13:54 ` David Sterba
2021-07-24 23:15 ` Zygo Blaxell
2021-07-25 3:34 ` Chris Murphy
2021-07-27 9:02 ` David Sterba [this message]
2021-07-25 5:27 ` Qu Wenruo
2021-07-26 2:53 ` Zygo Blaxell
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=20210727090256.GL5047@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=jorge.mrbastos@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo.btrfs@gmx.com \
/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).