From: David Sterba <dsterba@suse.cz>
To: Cerem Cem ASLAN <ceremcem@ceremcem.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Why isnt NOCOW attributes propogated on snapshot transfers?
Date: Mon, 16 Oct 2017 15:28:27 +0200 [thread overview]
Message-ID: <20171016132826.GH3521@twin.jikos.cz> (raw)
In-Reply-To: <CAN4oSBcZmqh+iK7Qyd4VBcOhQDfZVAu2B7_1pL60UKCb_oX3zg@mail.gmail.com>
On Sun, Oct 15, 2017 at 04:19:23AM +0300, 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?
This is a known defficiency of send protocol v1. And there are more,
listed on
https://btrfs.wiki.kernel.org/index.php/Design_notes_on_Send/Receive#Send_stream_v2_draft
next prev parent reply other threads:[~2017-10-16 13:30 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
2017-10-16 13:28 ` David Sterba [this message]
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=20171016132826.GH3521@twin.jikos.cz \
--to=dsterba@suse.cz \
--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).