From: Roman Mamedov <rm@romanrm.net>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: "marcel.cochem" <marcel.cochem@googlemail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: BTRFS error: bad tree block start 0 623771648
Date: Tue, 1 Aug 2017 11:04:10 +0500 [thread overview]
Message-ID: <20170801110410.0813a03a@natsu> (raw)
In-Reply-To: <20170731181200.GA3459@lim.localdomain>
On Mon, 31 Jul 2017 11:12:01 -0700
Liu Bo <bo.li.liu@oracle.com> wrote:
> Superblock and chunk tree root is OK, looks like the header part of
> the tree root is now all-zero, but I'm unable to think of a btrfs bug
> which can lead to that (if there is, it is a serious enough one)
I see that the FS is being mounted with "discard". So maybe it was a TRIM gone
bad (wrong location or in a wrong sequence).
Generally it appears to be not recommended to use "discard" by now (because of
its performance impact, and maybe possible issues like this), instead schedule
to call "fstrim <mountpoint>" once a day or so, and/or on boot-up.
> on ssd like disks, by default there is only one copy for metadata.
Time and time again, the default of "single" metadata for SSD is a terrible
idea. Most likely DUP metadata would save the FS in this case.
--
With respect,
Roman
next prev parent reply other threads:[~2017-08-01 6:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 16:14 BTRFS error: bad tree block start 0 623771648 marcel.cochem
2017-07-31 18:12 ` Liu Bo
2017-08-01 6:04 ` Roman Mamedov [this message]
2017-08-01 21:45 ` Liu Bo
2017-08-02 8:30 ` marcel.cochem
2017-08-01 6:08 ` Roman Mamedov
2017-08-02 3:22 ` Duncan
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=20170801110410.0813a03a@natsu \
--to=rm@romanrm.net \
--cc=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcel.cochem@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.