From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Does data checksumming remain for files with No_COW file attribute?
Date: Sat, 24 Sep 2016 20:11:31 +0200 [thread overview]
Message-ID: <1474740691.7196.6.camel@scientia.net> (raw)
In-Reply-To: <20160924124323.GS7138@carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
On Sat, 2016-09-24 at 12:43 +0000, Hugo Mills wrote:
> It's because you can't update the data and the checksum atomically
> -- at some point in the writing process, they must be inconsistent.
> This is considered a Bad Thing.
It's not worse at all than simply not cheksuming... in both cases you
have no guarantee whether the data is bogus or not, but in with csums,
you can at least tell - only at the little cost, of false positives
when the data was fully and correctly written, but the csums not.
Cheers.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5930 bytes --]
next prev parent reply other threads:[~2016-09-24 18:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 12:26 Does data checksumming remain for files with No_COW file attribute? Alexander Tomokhov
2016-09-24 12:37 ` Hugo Mills
2016-09-24 23:25 ` Alexander Tomokhov
2016-09-24 23:50 ` Adam Borowski
2016-09-25 5:44 ` Duncan
2016-09-26 20:41 ` Adam Borowski
2016-09-24 12:40 ` Roman Mamedov
2016-09-24 12:43 ` Hugo Mills
2016-09-24 18:11 ` Christoph Anton Mitterer [this message]
2016-09-25 13:49 ` Goffredo Baroncelli
2016-09-25 19:53 ` Christoph Anton Mitterer
2016-09-26 11:11 ` Austin S. Hemmelgarn
2016-09-24 18:09 ` Christoph Anton Mitterer
2016-09-24 21:44 ` Adam Borowski
2016-09-24 22:52 ` Christoph Anton Mitterer
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=1474740691.7196.6.camel@scientia.net \
--to=calestyo@scientia.net \
--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).