Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: runtime btrfsck
Date: Wed, 10 May 2017 13:52:55 +0500	[thread overview]
Message-ID: <20170510135255.790fbe39@natsu> (raw)
In-Reply-To: <1801706.Ls22q1bWhG@merkaba>

On Wed, 10 May 2017 09:48:07 +0200
Martin Steigerwald <martin@lichtvoll.de> wrote:

> Yet, when it comes to btrfs check? Its still quite rudimentary if you ask me.  

Indeed it is. It may or may not be possible to build a perfect Fsck, but IMO
for the time being, what's most sorely missing, is some sort of a knowingly
destructive repair mode, as in "I don't care about partial user data loss,
just whack the FS metadata into full logical consistency at any means
necessary".

Also feels like it doesn't currently deal with the majority of actual
in-real-world corruptions, notably the "parent transid failure" (even by a few
dozens increments) which it can only helpfully "Ignore" during repair.

So even with a minor corruption (something wonky in just ONE block of a
multi-terabyte FS) the answer is way too often "nuke the entire thing and
restore from backups".

-- 
With respect,
Roman

  parent reply	other threads:[~2017-05-10  8:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  6:29 runtime btrfsck Stefan Priebe - Profihost AG
2017-05-06  5:56 ` Stefan Priebe - Profihost AG
2017-05-10  7:02   ` Stefan Priebe - Profihost AG
2017-05-10  7:18     ` Roman Mamedov
2017-05-10  7:36       ` Stefan Priebe - Profihost AG
2017-05-10  7:40         ` Hugo Mills
2017-05-10  8:40           ` Stefan Priebe - Profihost AG
2017-05-10  9:08             ` Hugo Mills
2017-05-10  9:20               ` Stefan Priebe - Profihost AG
2017-05-10  9:54                 ` Hugo Mills
2017-05-10 11:23                   ` Stefan Priebe - Profihost AG
2017-05-10  7:24     ` Marat Khalili
2017-05-10  7:48     ` Martin Steigerwald
2017-05-10  8:42       ` Stefan Priebe - Profihost AG
2017-05-10  8:52       ` Roman Mamedov [this message]
2017-05-11 14:03         ` 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=20170510135255.790fbe39@natsu \
    --to=rm@romanrm.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=martin@lichtvoll.de \
    --cc=s.priebe@profihost.ag \
    /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