From: Bob Marley <bobmarley@shiftmail.org>
To: Hugo Mills <hugo@carfax.org.uk>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: High-sensitivity fs checker (not repairer) for btrfs
Date: Sat, 10 Nov 2012 23:32:15 +0100 [thread overview]
Message-ID: <509ED5EF.6090506@shiftmail.org> (raw)
In-Reply-To: <20121110212317.GE29581@carfax.org.uk>
On 11/10/12 22:23, Hugo Mills wrote:
> The closest thing is btrfsck. That's about as picky as we've got to
> date.
>
> What exactly is your use-case for this requirement?
We need a decently-available system. We can rollback filesystem to
last-known-good if the "test" detects an inconsistency on current btrfs
filesystem, but we need a very good test for that (i.e. if
last-known-good is actually bad we get into serious troubles).
So do you think btrfsck can return a false "OK" result? can it "not-see"
an inconsistency?
Thank you
next prev parent reply other threads:[~2012-11-10 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 21:18 High-sensitivity fs checker (not repairer) for btrfs Bob Marley
2012-11-10 21:23 ` Hugo Mills
2012-11-10 22:32 ` Bob Marley [this message]
2012-11-11 4:15 ` cwillu
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=509ED5EF.6090506@shiftmail.org \
--to=bobmarley@shiftmail.org \
--cc=hugo@carfax.org.uk \
--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