All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Marley <bobmarley@shiftmail.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: High-sensitivity fs checker (not repairer) for btrfs
Date: Sat, 10 Nov 2012 22:18:42 +0100	[thread overview]
Message-ID: <509EC4B2.6090706@shiftmail.org> (raw)

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

Thank you

             reply	other threads:[~2012-11-10 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-10 21:18 Bob Marley [this message]
2012-11-10 21:23 ` High-sensitivity fs checker (not repairer) for btrfs Hugo Mills
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=509EC4B2.6090706@shiftmail.org \
    --to=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 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.