From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Cerem Cem ASLAN <ceremcem@ceremcem.net>, linux-btrfs@vger.kernel.org
Subject: Re: Why isnt NOCOW attributes propogated on snapshot transfers?
Date: Mon, 16 Oct 2017 08:51:04 +0800 [thread overview]
Message-ID: <f7d452b4-8607-bef4-6e3c-c96bde726541@gmx.com> (raw)
In-Reply-To: <CAN4oSBcZmqh+iK7Qyd4VBcOhQDfZVAu2B7_1pL60UKCb_oX3zg@mail.gmail.com>
On 2017年10月15日 09:19, Cerem Cem ASLAN wrote:
> `btrfs send | btrfs receive` removes NOCOW attributes. Is it a bug or
> a feature? If it's a feature, how can we keep these attributes if we
> need to?
It seems that, current send doesn't have support for extra inode flags.
Send can only send out c/m/atime, uid/gid and xattr.
Since NODATACOW is stored in inode item flags, not xattr, so it's not
supported yet.
Thanks,
Qu
> --
> 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
>
next prev parent reply other threads:[~2017-10-16 0:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 1:19 Why isnt NOCOW attributes propogated on snapshot transfers? Cerem Cem ASLAN
2017-10-16 0:51 ` Qu Wenruo [this message]
2017-10-16 13:28 ` David Sterba
2017-10-16 15:59 ` Graham Cobb
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=f7d452b4-8607-bef4-6e3c-c96bde726541@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=ceremcem@ceremcem.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).