From: Charles Cazabon <charlesc-lists-btrfs@pyropus.ca>
To: btrfs list <linux-btrfs@vger.kernel.org>
Subject: Re: Is `btrfsck --repair` supposed to actually repair problems?
Date: Wed, 2 Oct 2013 13:56:55 -0600 [thread overview]
Message-ID: <20131002195655.GA23426@pyropus.ca> (raw)
In-Reply-To: <DBA8B3F5-F070-48AC-8EF7-20CCCAD9C732@colorremedies.com>
Chris Murphy <lists@colorremedies.com> wrote:
> On Oct 2, 2013, at 10:53 AM, Charles Cazabon wrote:
>
> >> I'd wait until the raid is finished syncing.
> >
> > Strictly speaking, this shouldn't be necessary.
>
> I know but it's a 16TB array, do you really want to start over from scratch?
> No. And neither do most people. So this isn't a use case that's probably
> getting a ton of testing.
Fair enough. The sync should be done late today or early tomorrow, and I am
waiting for it to complete before continuing to debug this. I'll start with
the scrub you mentioned.
> Also the write-intent bitmap isn't configured by default, and you didn't
> previous say that it was. Is this an internal or external bitmap?
Internal.
Thanks for your assistance to date.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon
GPL'ed software available at: http://pyropus.ca/software/
-----------------------------------------------------------------------
prev parent reply other threads:[~2013-10-02 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 21:12 Is `btrfsck --repair` supposed to actually repair problems? Charles Cazabon
2013-10-01 22:01 ` Chris Murphy
2013-10-01 23:46 ` Charles Cazabon
2013-10-02 0:42 ` Chris Murphy
2013-10-02 3:13 ` Charles Cazabon
2013-10-02 3:50 ` Chris Murphy
2013-10-02 16:53 ` Charles Cazabon
2013-10-02 19:13 ` Chris Murphy
2013-10-02 19:56 ` Charles Cazabon [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=20131002195655.GA23426@pyropus.ca \
--to=charlesc-lists-btrfs@pyropus.ca \
--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.