From: Hugo Mills <hugo@carfax.org.uk>
To: Bob Marley <bobmarley@shiftmail.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: High-sensitivity fs checker (not repairer) for btrfs
Date: Sat, 10 Nov 2012 21:23:17 +0000 [thread overview]
Message-ID: <20121110212317.GE29581@carfax.org.uk> (raw)
In-Reply-To: <509EC4B2.6090706@shiftmail.org>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
On Sat, Nov 10, 2012 at 10:18:42PM +0100, Bob Marley wrote:
> Hello all
> I would like to know if there exists a tool to check the btrfs
> filesystem very thoroughly.
> It's ok if it needs the FS unmounted to operate. Also mounted is OK.
> It does not need repair capability
> It needs very good checking capability: it has to return Good / Bad
> status with the "Bad" meaning that there is at least ONE
> inconsistency. Good means that it is really really 100% consistent.
>
> Does something like this exists?
>
> We need to detect as much ahead of time as possible if the btrfs
> filesystem has become even just a little bit inconsistent
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?
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- 2 + 2 = 5, for sufficiently large values of 2. ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-11-10 21:23 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 [this message]
2012-11-10 22:32 ` Bob Marley
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=20121110212317.GE29581@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=bobmarley@shiftmail.org \
--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