All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: cwillu <cwillu@cwillu.com>
Cc: russell@coker.com.au, linux-btrfs@vger.kernel.org
Subject: Re: multiple btrfsck runs
Date: Sat, 16 Mar 2013 05:44:15 -0700	[thread overview]
Message-ID: <20130316124415.GL24591@merlins.org> (raw)
In-Reply-To: <CAE5mzvj4DF98MmzW7M29WZtKiW3p_f7=GzZ54q3+jo6CWgPvxw@mail.gmail.com>

On Sat, Mar 16, 2013 at 06:24:47AM -0600, cwillu wrote:
> On Sat, Mar 16, 2013 at 6:02 AM, Russell Coker <russell@coker.com.au> wrote:
> > Is it expected that running btrfsck more than once will keep reporting errors?
> 
> Without options, btrfsck does not write to the disk.

Aaaaah, that explains why I never got it to work the day I wanted to try
it.
I should note that waht you're saying is neither documented in the man
page, nor in https://btrfs.wiki.kernel.org/index.php/Btrfsck

For that matter, the wiki actually states there are no options.

Is that mostly intentional so that whoever isn't reading the source
doesn't really run the tool because it's not ready?

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/

  reply	other threads:[~2013-03-16 12:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16 12:02 multiple btrfsck runs Russell Coker
2013-03-16 12:24 ` cwillu
2013-03-16 12:44   ` Marc MERLIN [this message]
2013-03-16 13:13     ` cwillu
2013-03-16 12:46   ` Russell Coker
2013-03-16 13:08     ` cwillu
2013-03-27  8:27       ` Russell Coker

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=20130316124415.GL24591@merlins.org \
    --to=marc@merlins.org \
    --cc=cwillu@cwillu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=russell@coker.com.au \
    /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.