From: Robin Kreis <r.kreis@uni-bremen.de>
To: linux-btrfs@vger.kernel.org
Subject: Recovering from btrfsck --init-csum-tree
Date: Tue, 4 Jun 2013 22:58:02 +0200 [thread overview]
Message-ID: <20130604225802.0feb0367@quip> (raw)
Hello,
how can I recover from running btrfsck --init-csum-tree on my 2TB
btrfs? Every attempt to read a file results in no checksum being
found, followed by a checksum mismatch which leads to the data block
being zeroed out (see label zeroit in inode.c). My current fix is
simply skipping the whole checksum validation, which enables me to
read my files again. I still think at least one of the following
should happen:
1. Add a warning that --init-csum-tree is pretty desctructive.
2. Make --init-csum-tree mark all inodes with INODE_NODATASUM.
3. Have some global flag or mount option to disable CRC checks.
What do you think?
reply other threads:[~2013-06-04 21:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130604225802.0feb0367@quip \
--to=r.kreis@uni-bremen.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).