[back to XFS after a few weeks' distractions] On Wed, Mar 02, 2016 at 05:34:45PM +0100, Christoph Hellwig wrote: > Although the protocol allows for it, the Linux NFS server code doesn't > support reflink-like functionality yet. It's been added to by TODO > list.. > > Signed-off-by: Christoph Hellwig <hch@xxxxxx> > --- > fs/xfs/xfs_pnfs.c | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/fs/xfs/xfs_pnfs.c b/fs/xfs/xfs_pnfs.c > index ade236e..9708fef 100644 > --- a/fs/xfs/xfs_pnfs.c > +++ b/fs/xfs/xfs_pnfs.c > @@ -139,6 +139,13 @@ xfs_fs_map_blocks( > return -ENXIO; > > /* > + * The pNFS block layout spec actually supports reflink like > + * functionality, but the Linux pNFS server doesn't implement it yet. > + */ > + if (!xfs_is_reflink_inode(ip)) > + return -ENXIO; /me isn't familiar with pNFS, but doesn't this make it so that xfs_fs_map_blocks /only/ works on reflinked files? Maybe I'm misreading the comment, but it sounds to me like Linux doesn't support reflinked files over pNFS and therefore we want to disable this iomapping functionality any time we find a reflinked file. But maybe there's a subtlety here that I'm missing? --D > + > + /* > * Lock out any other I/O before we flush and invalidate the pagecache, > * and then hand out a layout to the remote system. This is very > * similar to direct I/O, except that the synchronization is much more > -- > 2.1.4 > _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
