From: "J. Bruce Fields" <bfields@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Trond Myklebust <trondmy@primarydata.com>,
Steve Dickson <SteveD@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: EXCHANGE_ID with same network address but different server owner
Date: Tue, 16 May 2017 09:36:03 -0400 [thread overview]
Message-ID: <20170516133603.GA21704@parsley.fieldses.org> (raw)
In-Reply-To: <20170516133338.GD8498@stefanha-x1.localdomain>
On Tue, May 16, 2017 at 02:33:38PM +0100, Stefan Hajnoczi wrote:
> I suspect many guests will have a dedicated/private export. The guest
> will be the only client accessing its export. This could simplify the
> locking issues.
So why not migrate filesystem images instead of using NFS?
--b.
next prev parent reply other threads:[~2017-05-16 13:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 13:27 EXCHANGE_ID with same network address but different server owner Stefan Hajnoczi
2017-05-12 14:34 ` J. Bruce Fields
2017-05-12 15:01 ` Trond Myklebust
2017-05-12 17:00 ` Chuck Lever
2017-05-15 14:43 ` Stefan Hajnoczi
2017-05-15 16:02 ` J. Bruce Fields
2017-05-16 13:11 ` J. Bruce Fields
2017-05-18 13:34 ` Stefan Hajnoczi
2017-05-18 14:28 ` Chuck Lever
2017-05-18 15:04 ` Trond Myklebust
2017-05-18 15:08 ` J. Bruce Fields
2017-05-18 15:15 ` Chuck Lever
2017-05-18 15:17 ` Trond Myklebust
2017-05-18 15:17 ` Trond Myklebust
2017-05-18 15:28 ` bfields
2017-05-18 16:09 ` Trond Myklebust
2017-05-18 16:32 ` J. Bruce Fields
2017-05-18 17:13 ` Trond Myklebust
2017-05-22 12:45 ` Stefan Hajnoczi
2017-05-22 14:25 ` Jeff Layton
2017-05-16 13:33 ` Stefan Hajnoczi
2017-05-16 13:36 ` J. Bruce Fields [this message]
2017-05-17 14:33 ` Stefan Hajnoczi
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=20170516133603.GA21704@parsley.fieldses.org \
--to=bfields@redhat.com \
--cc=SteveD@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=trondmy@primarydata.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).