| To: | "Darrick J. Wong" <darrick.wong@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] xfs: don't hand out pNFS layouts for reflink inodes |
| From: | Christoph Hellwig <hch@xxxxxx> |
| Date: | Tue, 29 Mar 2016 09:21:28 +0200 |
| Cc: | Christoph Hellwig <hch@xxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20160328195140.GB5360@xxxxxxxxxxxxxxxx> |
| References: | <1456936485-21940-1-git-send-email-hch@xxxxxx> <20160328195140.GB5360@xxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
On Mon, Mar 28, 2016 at 12:51:40PM -0700, Darrick J. Wong wrote: > > /* > > + * 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? You jsut missed me fat fingering the check :) Btw, we'll need something similar to prevent swapfiles which just use ->bmap, but unfortunately swap just checks for the existences of method, so I'll probably have to do some VFS changes to properly support that. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Build regressions/improvements in v4.6-rc1, Geert Uytterhoeven |
|---|---|
| Next by Date: | Re: [PATCH 1/8] block: move bvec iterator into include/linux/bvec_iter.h, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH] xfs: don't hand out pNFS layouts for reflink inodes, Darrick J. Wong |
| Next by Thread: | Re: [PATCH] xfs: don't hand out pNFS layouts for reflink inodes, Darrick J. Wong |
| Indexes: | [Date] [Thread] [Top] [All Lists] |