* Recovering from btrfsck --init-csum-tree
@ 2013-06-04 20:58 Robin Kreis
0 siblings, 0 replies; only message in thread
From: Robin Kreis @ 2013-06-04 20:58 UTC (permalink / raw)
To: linux-btrfs
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?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-06-04 21:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-06-04 20:58 Recovering from btrfsck --init-csum-tree Robin Kreis
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).