From: Roman Mamedov <rm@romanrm.net>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: "Nikolay Borisov" <nborisov@suse.com>,
"José Luis" <parajoseluis@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: kernel 5.2 read time tree block corruption
Date: Wed, 16 Oct 2019 13:12:26 +0500 [thread overview]
Message-ID: <20191016131226.465eb506@natsu> (raw)
In-Reply-To: <375ce380-7b7d-03e5-212a-197d8cc2d5fc@gmx.com>
On Wed, 16 Oct 2019 15:45:54 +0800
Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
> dirty fixes (a special branch for the user
> to do, never intended to upstream).
Still it would be nice to get a btrfs check mode which would include trying
destructive actions, as in accepting the loss of some part of user data
(outright delete corrupt blocks, etc), just to restore the filesystem itself to
a fully correct and mountable state.
Sometimes there are cases when it is inconvenient to recreate the entire FS
(remember seeing 40TB mentioned recently), just to fix a few "parent transid
failed", not even many transactions apart. And the data itself is often backed
up, so restoring only the missing part from the backup would be much easier.
--
With respect,
Roman
next prev parent reply other threads:[~2019-10-16 8:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 10:15 kernel 5.2 read time tree block corruption José Luis
2019-10-15 12:24 ` Qu Wenruo
2019-10-15 12:38 ` Qu Wenruo
2019-10-15 15:03 ` José Luis
2019-10-15 13:25 ` Qu Wenruo
2019-10-15 17:55 ` José Luis
2019-10-16 0:43 ` Qu Wenruo
2019-10-16 7:42 ` Nikolay Borisov
2019-10-16 7:45 ` Qu Wenruo
2019-10-16 8:12 ` Roman Mamedov [this message]
2019-10-16 8:36 ` 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=20191016131226.465eb506@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=parajoseluis@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox