From: Remi Gauvin <remi@georgianit.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS corruption, mounts but comes read-only
Date: Mon, 30 Sep 2019 21:41:53 -0400 [thread overview]
Message-ID: <fe22fa62-7b13-f417-1af8-3ed12bf082f8@georgianit.com> (raw)
In-Reply-To: <6022d6c9-3022-01fd-3b97-67bd08ce36f1@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 976 bytes --]
On 2019-09-30 9:30 p.m., Qu Wenruo wrote:
>
>
> On 2019/10/1 上午5:08, Remi Gauvin wrote:
>> Mounting the FS after that btrfs check, kernel 5.3.1, here is the dmesg log:
>
> As that btrfs check shows, your extent tree is corrupted.
> Quite some backref is lost, thus no wonder some write opeartion would
> cause problem.
>
> In that case, it looks like only extent tree is corrupted, and no
> transid error.
>
> If you have data backed up, you would like to btrfs check --repair to
> see if it can repair them.
>
> Thanks,
> Qu
This is itself a back-up system, but not wishing to tempt fate, I'm
going to have to create a working substitute before I do anything risky
with it. It would take me several days and lots of travel to re-aquire
them.
Any idea what could have happened? The data and meta data should be
raid1, and none of the drives have any io errors of any kinds in their
SMART log.
Thank you for your guidance.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2019-10-01 1:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 19:57 BTRFS corruption, mounts but comes read-only Remi Gauvin
2019-09-30 21:08 ` Remi Gauvin
2019-10-01 1:30 ` Qu Wenruo
2019-10-01 1:41 ` Remi Gauvin [this message]
2019-10-01 1:53 ` Qu Wenruo
2019-10-05 17:14 ` Remi Gauvin
2019-10-05 23:18 ` Qu Wenruo
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=fe22fa62-7b13-f417-1af8-3ed12bf082f8@georgianit.com \
--to=remi@georgianit.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).