From: Jean-Denis Girard <jd.girard@sysnux.pf>
To: linux-btrfs@vger.kernel.org
Subject: Re: ERROR: could not setup extent tree
Date: Thu, 12 Nov 2020 13:08:25 -1000 [thread overview]
Message-ID: <rokf9a$sb0$1@ciao.gmane.io> (raw)
In-Reply-To: <CAJCQCtS81a96whvBXzkWY3wv9qLbTWiyjP_=3pQTVMi1uAnJrw@mail.gmail.com>
Le 12/11/2020 à 12:55, Chris Murphy a écrit :
> Hypothesis: The NVMe drive has had some kind of failure, and since
> this single NVMe is used as cache for both HDDs, in effect this
> thwarts the raid1 protection of Btrfs. i.e. you don't have complete
> hardware isolation by having dedicated SSD's to use as cache for each
> HDD. Something went wrong, and it's adversely affected the writes to
> both drives. Btrfs is reporting write errors for both bcache0 and
> bcache1 at the same time.
ok, it makes sense, so I made a mistake with this setup...
> I don't know for sure what the next step is, so my strong advice is to
> make no changes until the problem and path forward is well understood.
> The more things are changed at this point, the greater the likelihood
> of non-recovery. Importantly, I'd say whatever you do should be
> reversible, until you get superior advice.
I restored from backups on a different HDD, so the original setup has
not been touched.
> You might consider reposting or cross-posting on the bcache list and
> see if they have some advice for recovery, or maybe it's safer to just
> decouple bcache, and once the HDDs are freed to see if Btrfs can
> recover on its own.
Good idea, I'll also post on bcache list.
Thanks for your reply Chris!
Best regards,
--
Jean-Denis Girard
SysNux Systèmes Linux en Polynésie française
https://www.sysnux.pf/ Tél: +689 40.50.10.40 / GSM: +689 87.797.527
prev parent reply other threads:[~2020-11-12 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 3:53 ERROR: could not setup extent tree Jean-Denis Girard
2020-11-12 22:55 ` Chris Murphy
2020-11-12 23:08 ` Jean-Denis Girard [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='rokf9a$sb0$1@ciao.gmane.io' \
--to=jd.girard@sysnux.pf \
--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).