| To: | "J. Bruce Fields" <bfields@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: panic on 4.20 server exporting xfs filesystem |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Wed, 4 Mar 2015 15:41:41 +1100 |
| Cc: | Christoph Hellwig <hch@xxxxxx>, linux-nfs@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20150304020826.GD19439@xxxxxxxxxxxx> |
| References: | <20150303221033.GB19439@xxxxxxxxxxxx> <20150303224456.GV4251@dastard> <20150304020826.GD19439@xxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Tue, Mar 03, 2015 at 09:08:26PM -0500, J. Bruce Fields wrote: > By the way, Christoph, an unrelated question: how are the devices found, > and what are the chances of a client writing to the wrong block device? > > (E.g., if they're addressed based on a uuid that doesn't change on > cloning the block device, and if the client had access to another device > with an identical copy of the filesystem, could it end up writing to > that instead?) 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. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: panic on 4.20 server exporting xfs filesystem, J. Bruce Fields |
|---|---|
| Next by Date: | Re: How to handle TIF_MEMDIE stalls?, Dave Chinner |
| Previous by Thread: | Re: panic on 4.20 server exporting xfs filesystem, J. Bruce Fields |
| Next by Thread: | Re: panic on 4.20 server exporting xfs filesystem, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |