From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Will "btrfs scrub" clear corrupt filesystem trees?
Date: Thu, 10 Oct 2013 19:27:28 +0100 [thread overview]
Message-ID: <l36ri7$uvg$1@ger.gmane.org> (raw)
I have 1.5TB of data on a single disk formatted with defaults. There
appears to be only two directory trees of a few MBytes that have
suffered corruption (due to in the past too high a sata speed causing
corruption).
The filesystem mounts fine. But how to clear out the corrupt trees?
At the moment, I have running:
btrfsck --repair --init-extent-tree /dev/sdc
parent transid verify failed on 911904604160 wanted 17448 found 17449
parent transid verify failed on 911904604160 wanted 17448 found 17449
parent transid verify failed on 911904604160 wanted 17448 found 17449
parent transid verify failed on 911904604160 wanted 17448 found 17449
Ignoring transid failure
... And it is still running after over two days now. Looped?
Would a:
btrfs scrub start
clear out the corrupt trees?
Must I wait for the btrfsck to complete if it is recreating an extents
tree?...
Suggestions welcomed...
Martin
next reply other threads:[~2013-10-10 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 18:27 Martin [this message]
2013-10-10 19:11 ` Will "btrfs scrub" clear corrupt filesystem trees? Chris Murphy
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='l36ri7$uvg$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--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.