linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Unexpected behavior involving file attributes and snapshots.
Date: Tue, 14 Feb 2017 11:46:10 -0500	[thread overview]
Message-ID: <03288d87-0689-2cf5-0ab5-e625c97880dd@gmail.com> (raw)
In-Reply-To: <CAJCQCtQi56sVYccDPsVi8Av+FW=4SQjPpDskL0kJ-qY=P6rU1A@mail.gmail.com>

On 2017-02-14 11:07, Chris Murphy wrote:
> On Tue, Feb 14, 2017 at 8:30 AM, Austin S. Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>> 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).
>
> Huh, I can't reproduce this with 4.9.8 or 4.10rc7. systemd sets
> journal files with chattr +C, and I do manual snapshots of rootfs
> periodically, and those snapshots have journal files that have +C
> still set.
>
Just tested on a different filesystem, and I'm not seeing it there 
either, I'll take a closer look at the FS I saw this on and see if I can 
figure out what's up.


  reply	other threads:[~2017-02-14 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 15:30 Unexpected behavior involving file attributes and snapshots Austin S. Hemmelgarn
2017-02-14 15:55 ` Roman Mamedov
2017-02-14 16:07 ` Chris Murphy
2017-02-14 16:46   ` Austin S. Hemmelgarn [this message]
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=03288d87-0689-2cf5-0ab5-e625c97880dd@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).