From: Brendan Hide <brendan@swiftspirit.co.za>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs check segfaults after flipping 2 Bytes
Date: Thu, 02 Oct 2014 20:38:49 +0200 [thread overview]
Message-ID: <542D9BB9.40507@swiftspirit.co.za> (raw)
In-Reply-To: <542CE7CC.4020904@swiftspirit.co.za>
On 2014/10/02 07:51, Brendan Hide wrote:
> On 2014/10/02 01:31, Duncan wrote:
> [snip]
>
> I'm not sure if there is a mount option for this use case however. The
> option descriptions for "nodatasum" and "nodatacow" imply that *new*
> checksums are not generated. In this case the checksums already exist.
>
Looks like btrfsck has a relevant option, albeit likely more destructive
than absolutely necessary:
--init-csum-tree
create a new CRC tree.
^ Also, mail was sent as HTML 12 hours ago thus was never delivered.
Thunderbird has been disciplined.
--
__________
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
next prev parent reply other threads:[~2014-10-02 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 20:29 btrfs check segfaults after flipping 2 Bytes Niklas Fischer
2014-10-01 20:34 ` Niklas Fischer
2014-10-01 23:31 ` Duncan
2014-10-02 5:51 ` Brendan Hide
2014-10-02 10:58 ` Duncan
2014-10-02 18:38 ` Brendan Hide [this message]
2014-10-06 2:29 ` Qu Wenruo
2014-10-06 4:10 ` Duncan
2014-10-06 4:13 ` Qu Wenruo
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=542D9BB9.40507@swiftspirit.co.za \
--to=brendan@swiftspirit.co.za \
--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