From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Unexpected behavior involving file attributes and snapshots.
Date: Tue, 14 Feb 2017 10:30:43 -0500 [thread overview]
Message-ID: <ea92c7c6-4b98-d683-eb66-593836bcc82a@gmail.com> (raw)
I was just experimenting with snapshots on 4.9.0, and came across some
unexpected behavior.
The simple explanation is that if you snapshot a subvolume, any files in
the subvolume that have the NOCOW attribute will not have that attribute
in the snapshot. Some further testing indicates that this is the only
file attribute that isn't preserved (I checked all the chattr flags that
BTRFS supports).
I'm kind of curious whether:
1. This is actually documented somewhere, as it's somewhat unexpected
given that everything else is preserved when snapshotting.
2. This is intended behavior, or just happens to be a side effect of the
implementation.
next reply other threads:[~2017-02-14 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 15:30 Austin S. Hemmelgarn [this message]
2017-02-14 15:55 ` Unexpected behavior involving file attributes and snapshots Roman Mamedov
2017-02-14 16:07 ` Chris Murphy
2017-02-14 16:46 ` Austin S. Hemmelgarn
2017-02-14 17:52 ` Austin S. Hemmelgarn
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=ea92c7c6-4b98-d683-eb66-593836bcc82a@gmail.com \
--to=ahferroin7@gmail.com \
--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).