From: Russell Coker <russell@coker.com.au>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: multiple btrfsck runs
Date: Wed, 27 Mar 2013 19:27:11 +1100 [thread overview]
Message-ID: <201303271927.12379.russell@coker.com.au> (raw)
In-Reply-To: <CAE5mzvgqkeB2qox4hi7JZ0cOQkwNA0WrMC2+k4bXDDGWuD+5OA@mail.gmail.com>
On Sun, 17 Mar 2013, cwillu <cwillu@cwillu.com> wrote:
> On Sat, Mar 16, 2013 at 6:46 AM, Russell Coker <russell@coker.com.au> wrote:
> > On Sat, 16 Mar 2013, cwillu <cwillu@cwillu.com> 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.
> >
> > The man page for the version in Debian doesn't document any options.
> >
> > The source indicates that --repair might be the one that's desired, is
> > that correct?
>
> Yes. However, unless something is actually broken, or you've been
> advised by a developer, I'd stick with btrfs scrub.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
I've got a filesystem that causes a kernel panic and can't even get to the
scrub stage, so btrfsck is necessary.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703211
While this is an upstream bug, I've filed the above Debian bug report about it.
Sometimes in such situations the DD will fix the bug and send the patch
upstream.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
prev parent reply other threads:[~2013-03-27 8:27 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
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 [this message]
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=201303271927.12379.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=cwillu@cwillu.com \
--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.