From: Juan Orti Alcaine <juan.orti@miceliux.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs send/receive does not preserve +C (nocow) attribute
Date: Wed, 06 Aug 2014 18:22:52 +0200 [thread overview]
Message-ID: <1651217.HJVXSU4rSp@xenon.miceliux.com> (raw)
In-Reply-To: <20140806155652.GA569@asusntb.lan>
El Miércoles, 6 de agosto de 2014 17:56:52 Jakub Klinkovský escribió:
> I've been testing btrfs send/receive, and to my surprise, the +C (nocow)
> attribute I have set on directory for virtual machines images is not
> preserved. Is this expected? Having found no information about this issue,
> I'm asking here.
>
> Info:
> $ uname -a
> Linux asusntb 3.15.8-1-ARCH #1 SMP PREEMPT Fri Aug 1 08:51:42 CEST 2014
> x86_64 GNU/Linux $ btrfs --version
> Btrfs v3.14.2-dirty
>
> Both source and target btrfs filesystems are mounted with the same mount
> options:
> rw,nosuid,nodev,noatime,compress=lzo,space_cache,autodefrag,commit=60
>
> $ lsattr ~/virtual_machines/
> ---------------C virtual_machines/archlinux-btrfs.raw
> ---------------C virtual_machines/archlinux.raw
> ---------------C virtual_machines/winxp.raw
>
> $ lsattr /media/backup/virtual_machines/2014-08-06/
> ----------------
> /media/backup/virtual_machines/2014-08-06/archlinux-btrfs.raw
> ---------------- /media/backup/virtual_machines/2014-08-06/archlinux.raw
> ---------------- /media/backup/virtual_machines/2014-08-06/winxp.raw
>
> Regards,
>
> --
> jlk
Nor do file capabilities get preserved:
https://bugzilla.kernel.org/show_bug.cgi?id=68891
prev parent reply other threads:[~2014-08-06 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 15:56 btrfs send/receive does not preserve +C (nocow) attribute Jakub Klinkovský
2014-08-06 16:22 ` Juan Orti Alcaine [this message]
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=1651217.HJVXSU4rSp@xenon.miceliux.com \
--to=juan.orti@miceliux.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).