From: Roman Mamedov <rm@romanrm.net>
To: Brian Hansen <dulanic@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: reflink copy now works with nocow?
Date: Sat, 2 Nov 2019 20:24:33 +0500 [thread overview]
Message-ID: <20191102202433.1ca92ea5@natsu> (raw)
In-Reply-To: <CAMiuOHWtjJdeKmkEV-kx+GRk_VskXEKMZoJWD5z7acapqeDE-A@mail.gmail.com>
On Sat, 2 Nov 2019 10:09:27 -0500
Brian Hansen <dulanic@gmail.com> wrote:
> So I'll need to setup a script to remove C when moving
> directories.
The only way to un-nocow a +C file is to physically rewrite it into a new
copy. The +C attribute can be removed on existing files only if they are 0
bytes in size.
> Unless there is a easier way to deal with this?
Try a different/newer kernel version, as noted in my message all of this
doesn't seem to matter anymore, and nocow files can now be reflinked (or +C is
not working anymore and they aren't actually nocow).
--
With respect,
Roman
next prev parent reply other threads:[~2019-11-02 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 13:49 cp --reflink invalid argument error Brian Hansen
2019-11-02 14:36 ` reflink copy now works with nocow? Roman Mamedov
2019-11-02 15:09 ` Brian Hansen
2019-11-02 15:24 ` Roman Mamedov [this message]
2019-11-02 20:15 ` Brian Hansen
2019-11-14 5:21 ` Zygo Blaxell
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=20191102202433.1ca92ea5@natsu \
--to=rm@romanrm.net \
--cc=dulanic@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.