xfs
[Top] [All Lists]

Re: [RFCv3 00/12] xfstests: test the btrfs/xfs reflink/dedupe ioctls

To: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Subject: Re: [RFCv3 00/12] xfstests: test the btrfs/xfs reflink/dedupe ioctls
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Sun, 8 Nov 2015 23:59:26 -0800
Cc: david@xxxxxxxxxxxxx, fstests@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, Anna.Schumaker@xxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20151007051257.3260.73072.stgit@xxxxxxxxxxxxxxxx>
References: <20151007051257.3260.73072.stgit@xxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.23 (2014-03-12)
On Tue, Oct 06, 2015 at 10:12:57PM -0700, Darrick J. Wong wrote:
>  * I don't have any interesting NFS/CIFS setups for test. :(

I have a banrch with client and server support for NFSv4.2 CLONE
support:

http://git.infradead.org/users/hch/pnfs.git/shortlog/refs/heads/reflink+clone

For now you want to use btrfs on the server, as using reflinks on XFS
seems to be a little unstable over NFS.

> If you're going to start using this mess, you probably ought to just
> pull from my github trees for kernel[1], xfsprogs[2], and xfstests[3].
> They should just work with the btrfs that's in 4.3.
> 
> Comments and questions are, as always, welcome.

Any reason the groups are called clone?  I don't really have an opinion
on clone vs reflink but given that the xfs_io command is reflink I'd
rather be consistent.

Otherwise I'd say get it merged ASAP, we can still fix up various
details later.

<Prev in Thread] Current Thread [Next in Thread>