From: Sebastian Roller <sebastian.roller@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: All files are damaged after btrfs restore
Date: Wed, 17 Mar 2021 10:01:47 +0100 [thread overview]
Message-ID: <CALS+qHNq1YJr-sYfeGUpr=zjTJjUe3cC6PTwUuWKhEMni3pmbA@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtQ7o1_Kkxf3Gh8bM+r4-e3tXuZsFM1mHUQakRvJUA9mqA@mail.gmail.com>
Am Mi., 17. März 2021 um 03:59 Uhr schrieb Chris Murphy
<lists@colorremedies.com>:
>
> On Tue, Mar 16, 2021 at 7:39 PM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
> > > Using that restore I was able to restore approx. 7 TB of the
> > > originally stored 22 TB under that directory.
> > > Unfortunately nearly all the files are damaged. Small text files are
> > > still OK. But every larger binary file is useless.
> > > Is there any possibility to fix the filesystem in a way, that I get
> > > the data less damaged?
> >
> > From the result, it looks like the on-disk data get (partially) wiped out.
> > I doubt if it's just simple controller failure, but more likely
> > something not really reaching disk or something more weird.
>
> Hey Qu, thanks for the reply.
>
> So it's not clear until further downthread that it's bcache in
> writeback mode with an SSD that failed. And I've probably
> underestimated the significance of how much data (in this case both
> Btrfs metadata and user data) and for how long it can stay *only* on
> the SSD with this policy.
Sorry Chris. I might have expressed this wrongly. But the
btrfs-filesystem was never on bcache. On bcache was a xfs-filesystem
that I backed up (rsynced) to the btrfs-filesystem when everything
went wrong. And I quickly gave up hope for that xfs afterwards, due to
the (lost) cached data of the directory-structure. That's why I'm
focusing on getting the backup on the btrfs-filesystem back.
But the possibility that some data is really wiped out or as Qu said,
that something is not reaching the disk gives me a direction to
investigate further. Maybe the raid-enclosure or the FC got damaged (I
ruled that out in the beginning). Eventually a failed raid-rebuild or
so. That would explain why so much data is missing.
Thank you.
Sebastian
next prev parent reply other threads:[~2021-03-17 9:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 15:45 All files are damaged after btrfs restore Sebastian Roller
2021-02-25 5:40 ` Chris Murphy
2021-02-25 5:52 ` Chris Murphy
2021-02-26 16:01 ` Sebastian Roller
2021-02-27 1:04 ` Chris Murphy
2021-03-04 15:34 ` Sebastian Roller
2021-03-05 3:01 ` Chris Murphy
2021-03-07 13:58 ` Sebastian Roller
2021-03-08 0:56 ` Chris Murphy
2021-03-09 17:02 ` Sebastian Roller
2021-03-09 20:34 ` Chris Murphy
2021-03-16 9:35 ` Sebastian Roller
2021-03-16 19:34 ` Chris Murphy
2021-03-17 1:38 ` Qu Wenruo
2021-03-17 2:59 ` Chris Murphy
2021-03-17 9:01 ` Sebastian Roller [this message]
2021-03-17 1:54 ` Dāvis Mosāns
2021-03-17 10:50 ` Sebastian Roller
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='CALS+qHNq1YJr-sYfeGUpr=zjTJjUe3cC6PTwUuWKhEMni3pmbA@mail.gmail.com' \
--to=sebastian.roller@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--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 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.