All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl-Philipp Richter <richter@richtercloud.de>
To: linux-btrfs@vger.kernel.org
Subject: btrfs check --init-csum-tree removes csums again
Date: Sun, 15 Feb 2015 09:50:21 +0100	[thread overview]
Message-ID: <54E05DCD.3050508@richtercloud.de> (raw)

Hi,
After running `btrfs check --init-csum-tree` 3.18.2 and 3.19-rc2 on a
btrfs all checksums are gone (thousands of line in the form of `no csum
found for inode X start Y` in `/var/log/kern.log`). I know that this
behavior (to delete all csums) was a stub in a dev version and remember
that it was fixed and that I even fixed a csum tree at one point. Could
someone please confirm and maybe even point me to a working version?

Any help or pointers are appreciated.

Best regards,
Kalle

             reply	other threads:[~2015-02-15  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15  8:50 Karl-Philipp Richter [this message]
2015-02-16  5:59 ` btrfs check --init-csum-tree removes csums again Chris Murphy
2015-02-16  8:42   ` Qu Wenruo
2015-02-16 10:21     ` Tim DeNike
2015-02-16 11:19       ` Karl-Philipp Richter
2015-02-17  4:18         ` Karl-Philipp Richter
2015-02-17  5:19           ` Qu Wenruo
2015-02-17  7:12           ` 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=54E05DCD.3050508@richtercloud.de \
    --to=richter@richtercloud.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 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.