From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: dsterba@suse.cz, Jorge Bastos <jorge.mrbastos@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Zygo Blaxell <ce3g8jdj@umail.furryterror.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: Thu, 22 Jul 2021 15:54:55 +0200 [thread overview]
Message-ID: <20210722135455.GU19710@twin.jikos.cz> (raw)
In-Reply-To: <8b830dc8-11d4-9b21-abe4-5f44e6baa013@gmx.com>
On Thu, Jul 22, 2021 at 08:18:21AM +0800, Qu Wenruo wrote:
>
>
> On 2021/7/22 上午1:44, David Sterba wrote:
> > On Fri, Jul 16, 2021 at 11:44:21PM +0100, Jorge Bastos wrote:
> >> Hi,
> >>
> >> This was a single disk filesystem, DUP metadata, and this week it stop
> >> mounting out of the blue, the data is not a concern since I have a
> >> full fs snapshot in another server, just curious why this happened, I
> >> remember reading that some WD disks have firmware with write caches
> >> issues, and I believe this disk is affected:
> >>
> >> Model family:Western Digital Green
> >> Device model:WDC WD20EZRX-00D8PB0
> >> Firmware version:80.00A80
> >
> > For the record summing up the discussion from IRC with Zygo, this
> > particular firmware 80.00A80 on WD Green is known to have problematic
> > firmware and would explain the observed errors.
> >
> > Recommendation is not to use WD Green or periodically disable the write
> > cache by 'hdparm -W0'.
>
> Zygo is always the god to expose bad hardware.
>
> Can we maintain a list of known bad hardware inside btrfs-wiki?
> And maybe escalate it to other fses too?
Yeah a list on wiki would be great, though I'm a bit skeptical about
keeping it up up to date, there are very few active wiki editors, the
knowledge is still mostly stored in the IRC logs. But without a landing
page on wiki we can't even start, so I'll create it.
next prev parent reply other threads:[~2021-07-22 13:57 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 [this message]
2021-07-24 23:15 ` Zygo Blaxell
2021-07-25 3:34 ` Chris Murphy
2021-07-27 9:02 ` David Sterba
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=20210722135455.GU19710@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=jorge.mrbastos@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--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).