| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: panic on 4.20 server exporting xfs filesystem |
| From: | Christoph Hellwig <hch@xxxxxx> |
| Date: | Thu, 5 Mar 2015 14:19:01 +0100 |
| Cc: | "J. Bruce Fields" <bfields@xxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, linux-nfs@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20150304044141.GQ18360@dastard> |
| References: | <20150303221033.GB19439@xxxxxxxxxxxx> <20150303224456.GV4251@dastard> <20150304020826.GD19439@xxxxxxxxxxxx> <20150304044141.GQ18360@dastard> |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
On Wed, Mar 04, 2015 at 03:41:41PM +1100, Dave Chinner wrote: > As I understand it, nothing will prevent this - if you don't change > the UUID on the filesystem when you clone it, then the UUID will > still match and writes can be directed to any block deice with a > matching offset/UUID pair. Unfortunately that's the case indeed. The whole discovery part of the block layout protocol is fundamentally flawed, as is the recall part. This is my attempt to fix it, but I have no idea how to proceed from posting my draft to the IETF to actually making it a standard: http://tools.ietf.org/html/draft-hellwig-nfsv4-scsi-layout-00 |
| Previous by Date: | Re: panic on 4.20 server exporting xfs filesystem, Christoph Hellwig |
|---|---|
| Next by Date: | 成功做外贸 抢先主动联系客户, ken |
| Previous by Thread: | Re: panic on 4.20 server exporting xfs filesystem, Dave Chinner |
| Next by Thread: | Re: panic on 4.20 server exporting xfs filesystem, J. Bruce Fields |
| Indexes: | [Date] [Thread] [Top] [All Lists] |