From: "Johannes Löthberg" <johannes@kyriasis.com>
To: linux-btrfs@vger.kernel.org
Subject: Bug when trying to clone with cp --reflink=always
Date: Tue, 8 Apr 2014 18:06:26 +0200 [thread overview]
Message-ID: <20140408160626.GA23154@leeloo> (raw)
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
Hello,
I have a bunch of files that can't be cloned with `cp --reflink=always`
for no apparent reason. However, if I copy the file before doign the
clone it works.
Staces of a --reflink copy of the original file[1] and of the copied
file[2]:
[1]: http://sprunge.us/UXOO
[2]: http://sprunge.us/TUVa
lsattr says that no interesting attribute is set on any of the files and
I'm not sure what else to check.
--
Sincerely,
Johannes Löthberg
PGP Key ID: 3A9D0BB5
[-- Attachment #2: Type: application/pgp-signature, Size: 1600 bytes --]
reply other threads:[~2014-04-08 16:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140408160626.GA23154@leeloo \
--to=johannes@kyriasis.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