From: Hugo Mills <hugo@carfax.org.uk>
To: Alexander Tomokhov <alexoundos@ya.ru>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Does data checksumming remain for files with No_COW file attribute?
Date: Sat, 24 Sep 2016 12:37:49 +0000 [thread overview]
Message-ID: <20160924123749.GR7138@carfax.org.uk> (raw)
In-Reply-To: <767591474719974@web21o.yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
On Sat, Sep 24, 2016 at 03:26:14PM +0300, Alexander Tomokhov wrote:
> There is an unanswered question at stackexchange:
> http://unix.stackexchange.com/q/303130/41572
>
> Assume that we don't invoke mount options like nodatacow and nodatasum - operate only at file attributes level, which are controlled with lsattr/chattr. So does setting No_COW on a file (chattr +C) imply disabling data checksumming on it? The same way as mount options behave (nodatacow implies nodatasum)? Moreover may it disable checksumming only for newly written extents and keep for reading existing ones?
Yes, it does imply disabling checksums.
If you have extents in the file when +C is set, then the flag is
ignored (even for new extents, as far as I know): you can only
usefully set +C on a file with no extents.
So, to use +C, you either need to touch the file first, then set +C
on it, then open the file and write to it, or you need to have +C set
on the parent directory.
Hugo.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Hugo Mills | Comic Sans goes into a bar, and the barman says, "We
hugo@... carfax.org.uk | don't serve your type here."
http://carfax.org.uk/ |
PGP: E2AB1DE4 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-09-24 12:37 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 [this message]
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
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=20160924123749.GR7138@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=alexoundos@ya.ru \
--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.