linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jorge Bastos <jorge.mrbastos@gmail.com>
To: dsterba@suse.cz, Jorge Bastos <jorge.mrbastos@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
	Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Subject: Re: "bad tree block start, want 419774464 have 0" after a clean shutdown, could it be a disk firmware issue?
Date: Mon, 22 Nov 2021 13:49:18 +0000	[thread overview]
Message-ID: <CAHzMYBSE6jeEcOfOerc-99M9_j-4XDLcEw_w=hGLxAzr9bmWwA@mail.gmail.com> (raw)
In-Reply-To: <CAHzMYBQnP=rqa_mf9TXAEK3Yrpjezff0cE=pBsunbBT63wHeSQ@mail.gmail.com>

Hello all,

Small update on this issue, it happened again to the same disk:

Nov 22 13:32:15 TV1 emhttpd: shcmd (126): mount -t btrfs -o
noatime,space_cache=v2 /dev/md20 /mnt/disk20
Nov 22 13:32:15 TV1 kernel: BTRFS info (device md20): enabling free space tree
Nov 22 13:32:15 TV1 kernel: BTRFS info (device md20): using free space tree
Nov 22 13:32:15 TV1 kernel: BTRFS info (device md20): has skinny extents
Nov 22 13:32:16 TV1 kernel: BTRFS error (device md20): bad tree block
start, want 1589201485824 have 620757024
Nov 22 13:32:16 TV1 kernel: BTRFS error (device md20): bad tree block
start, want 1589201485824 have 620757024
Nov 22 13:32:16 TV1 kernel: BTRFS error (device md20): failed to read
block groups: -5

This is a new filesystem, previous one was unrecoverable, again it
happened on boot after a clean shutdown, I have over a 100 similar
btrfs filesystems, more than 10 using this same disk model with no
other issues for years, so the same thing happening to the same disk
in a space of a few months suggests to me it's not just a firmware
issue, something else must be going one, maybe something in the disk
is going bad, controller is an LSI 9207 HBA with 17 more disks
connected, for now I'm going to restore the data to a different disk
and see if it doesn't happen again, might also use this disk in a
small zfs pool I have to see if it also gives issues there.

Regards,
Jorge Bastos

On Wed, Jul 21, 2021 at 7:14 PM Jorge Bastos <jorge.mrbastos@gmail.com> wrote:
>
> On Wed, Jul 21, 2021 at 6:47 PM David Sterba <dsterba@suse.cz> wrote:
> >
> > 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'.
> >
>
> Thank you for the reply, yes, from now on I intend to disable write
> cache on those disks, since I still have a lot of them in use.
>
> Jorge

  reply	other threads:[~2021-11-22 13:49 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 [this message]
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
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='CAHzMYBSE6jeEcOfOerc-99M9_j-4XDLcEw_w=hGLxAzr9bmWwA@mail.gmail.com' \
    --to=jorge.mrbastos@gmail.com \
    --cc=ce3g8jdj@umail.furryterror.org \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    /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).