From: Tom Haynes <thomas.haynes@primarydata.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: panic on 4.20 server exporting xfs filesystem
Date: Sun, 8 Mar 2015 06:08:57 -0700 [thread overview]
Message-ID: <07736642-EBA0-4F6B-B6BD-C7C5725A2DC6@primarydata.com> (raw)
In-Reply-To: <20150305131901.GB16235@lst.de>
> On Mar 5, 2015, at 5:19 AM, Christoph Hellwig <hch@lst.de> wrote:
>
>> 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
Let's be sure to talk about this at LSF...
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Tom Haynes <thomas.haynes@primarydata.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Dave Chinner <david@fromorbit.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: panic on 4.20 server exporting xfs filesystem
Date: Sun, 8 Mar 2015 06:08:57 -0700 [thread overview]
Message-ID: <07736642-EBA0-4F6B-B6BD-C7C5725A2DC6@primarydata.com> (raw)
In-Reply-To: <20150305131901.GB16235@lst.de>
> On Mar 5, 2015, at 5:19 AM, Christoph Hellwig <hch@lst.de> wrote:
>
>> 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
Let's be sure to talk about this at LSF...
next prev parent reply other threads:[~2015-03-08 13:09 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 22:10 panic on 4.20 server exporting xfs filesystem J. Bruce Fields
2015-03-03 22:10 ` J. Bruce Fields
2015-03-03 22:44 ` Dave Chinner
2015-03-03 22:44 ` Dave Chinner
2015-03-04 2:08 ` J. Bruce Fields
2015-03-04 2:08 ` J. Bruce Fields
2015-03-04 4:41 ` Dave Chinner
2015-03-04 4:41 ` Dave Chinner
2015-03-05 13:19 ` Christoph Hellwig
2015-03-05 13:19 ` Christoph Hellwig
2015-03-05 15:21 ` J. Bruce Fields
2015-03-05 15:21 ` J. Bruce Fields
2015-03-08 13:08 ` Tom Haynes [this message]
2015-03-08 13:08 ` Tom Haynes
2015-03-04 15:54 ` J. Bruce Fields
2015-03-04 15:54 ` J. Bruce Fields
2015-03-04 22:09 ` Dave Chinner
2015-03-04 22:09 ` Dave Chinner
2015-03-04 22:27 ` J. Bruce Fields
2015-03-04 22:27 ` J. Bruce Fields
2015-03-04 22:45 ` Dave Chinner
2015-03-04 22:45 ` Dave Chinner
2015-03-04 22:49 ` Eric Sandeen
2015-03-04 22:49 ` Eric Sandeen
2015-03-04 22:56 ` Dave Chinner
2015-03-04 22:56 ` Dave Chinner
2015-03-05 4:08 ` J. Bruce Fields
2015-03-05 4:08 ` J. Bruce Fields
2015-03-05 13:17 ` Christoph Hellwig
2015-03-05 13:17 ` Christoph Hellwig
2015-03-05 15:01 ` J. Bruce Fields
2015-03-05 15:01 ` J. Bruce Fields
2015-03-05 17:02 ` J. Bruce Fields
2015-03-05 17:02 ` J. Bruce Fields
2015-03-05 20:47 ` J. Bruce Fields
2015-03-05 20:47 ` J. Bruce Fields
2015-03-05 20:59 ` Dave Chinner
2015-03-05 20:59 ` Dave Chinner
2015-03-06 20:47 ` J. Bruce Fields
2015-03-06 20:47 ` J. Bruce Fields
2015-03-19 17:27 ` Christoph Hellwig
2015-03-19 17:27 ` Christoph Hellwig
2015-03-19 18:47 ` J. Bruce Fields
2015-03-19 18:47 ` J. Bruce Fields
2015-03-20 6:49 ` Christoph Hellwig
2015-03-20 6:49 ` Christoph Hellwig
2015-03-08 15:30 ` Christoph Hellwig
2015-03-08 15:30 ` Christoph Hellwig
2015-03-09 19:45 ` J. Bruce Fields
2015-03-09 19:45 ` J. Bruce Fields
2015-03-20 4:06 ` Kinglong Mee
2015-03-20 4:06 ` Kinglong Mee
2015-03-20 6:50 ` Christoph Hellwig
2015-03-20 6:50 ` Christoph Hellwig
2015-03-20 7:56 ` [PATCH] NFSD: Fix infinite loop in nfsd4_cb_layout_fail() Kinglong Mee
2015-03-20 7:56 ` Kinglong Mee
2015-03-15 12:58 ` panic on 4.20 server exporting xfs filesystem Christoph Hellwig
2015-03-15 12:58 ` Christoph Hellwig
2015-03-16 14:27 ` J. Bruce Fields
2015-03-16 14:27 ` J. Bruce Fields
2015-03-17 10:30 ` Christoph Hellwig
2015-03-17 10:30 ` Christoph Hellwig
2015-03-18 10:50 ` Christoph Hellwig
2015-03-18 10:50 ` Christoph Hellwig
2015-03-27 10:41 ` Christoph Hellwig
2015-03-27 14:50 ` Jeff Layton
2015-03-30 16:44 ` Christoph Hellwig
2015-03-27 15:13 ` J. Bruce Fields
2015-04-26 16:19 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07736642-EBA0-4F6B-B6BD-C7C5725A2DC6@primarydata.com \
--to=thomas.haynes@primarydata.com \
--cc=bfields@fieldses.org \
--cc=hch@lst.de \
--cc=linux-nfs@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.