From: "Darrick J. Wong" <firstname.lastname@example.org>
To: email@example.com, Andreas Dilger <firstname.lastname@example.org>,
Eric Sandeen <email@example.com>,
Qu Wenruo <firstname.lastname@example.org>, Joshi <email@example.com>,
Subject: Re: cross-fs copy support
Date: Tue, 2 Oct 2018 08:19:26 -0700 [thread overview]
Message-ID: <20181002151926.GC6706@magnolia> (raw)
On Tue, Oct 02, 2018 at 10:15:44AM +0200, David Sterba wrote:
> On Mon, Oct 01, 2018 at 01:51:09PM -0600, Andreas Dilger wrote:
> > > Yes, I would expect there to be problems with his modified kernel
> > > for a filesystem that supports clone_file_range, because
> > > vfs_copy_file_range() will clone if possible, and this should fail across
> > > filesystems.
> > >
> > > In general, though, I don't know for sure why we don't fall back to
> > > do_splice_direct() across filesystems, although the filesystems that
> > > implement their own ->copy_file_range ops may have their own,
> > > further restrictions within their implementations.
> > >
> > > This call /is/ documented in the manpage as only being valid for
> > > files on the same filesystem, though:
> > > http://man7.org/linux/man-pages/man2/copy_file_range.2.html
> > There was a patch to allow cross-mount copy for NFS, but it hasn't landed
> > yet.
> I found https://marc.info/?l=linux-nfs&m=144138779721907&w=2 that lifts
> the VFS check (part of a series that can't be easily linked to).
> The lack of cross-mount reflink (based on the copy_file_ragne) is often
> confusing users, there are common setups that mount subvolumes
> separately and reflinking between them would require mount of the
> toplevel subvolume.
> If there are 2 in-kernel users of the relaxed cross-mount copy, I think
> this would help to push the series forward.
I don't have any objection to cross-mountpoint same-filesystem clones,
though obviously we need to all agree that from now on the vfs /does/
support certain IO operations across mountpoints.
(I haven't any opinion on cross-filesystem copies, as XFS is incapable
of such things.)
next prev parent reply other threads:[~2018-10-02 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 14:32 cross-fs copy support Joshi
2018-10-01 14:48 ` Qu Wenruo
2018-10-01 15:15 ` Joshi
2018-10-01 15:49 ` Eric Sandeen
2018-10-01 19:51 ` Andreas Dilger
2018-10-02 8:15 ` David Sterba
2018-10-02 15:19 ` Darrick J. Wong [this message]
2018-10-02 18:28 ` J. Bruce Fields
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).