From: Fields James <bfields@fieldses.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
Morton Andrew <akpm@linux-foundation.org>,
Harrosh Boaz <bharrosh@panasas.com>,
"<linux-nfs@vger.kernel.org>" <linux-nfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Namjae Jeon <namjae.jeon@samsung.com>,
Vivek Trivedi <t.vivek@samsung.com>,
Amit Sahrawat <a.sahrawat@samsung.com>
Subject: Re: [RFC PATCH] nfs: Add NFS3PROC_UMOUNT procedure.
Date: Sat, 23 Jun 2012 12:09:23 -0400 [thread overview]
Message-ID: <20120623160923.GB10787@fieldses.org> (raw)
In-Reply-To: <20120623155710.GA10787@fieldses.org>
On Sat, Jun 23, 2012 at 11:57:10AM -0400, Fields James wrote:
> On Sat, Jun 23, 2012 at 03:52:20PM +0000, Myklebust, Trond wrote:
> > The other objection is that NFSv3 already has a way to do this via the MOUNT protocol. We already call MOUNTPROC3_UMNT/MOUNTPROC_UMNT on unmount of a filesystem.
> >
> > The problem with this approach is that if the NFS client crashes before it can call this function, then the server never gets notified. That is a problem that your patch has too...
>
> Yes. Could you instead work on describing *exactly* what the original
> problem was that prompted this?
("You" here meaning Namjae Jeon, of course).
And note here we've all read the changelog, that's not what I'm asking
for.
I want to know the details of *your* specific case. "I have X clients
that I use for Y, periodically I want to unmount the exported filesystem
to do Z, I tried doing W but it didn't work...".
--b.
next prev parent reply other threads:[~2012-06-23 16:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 10:46 Namjae Jeon
2012-06-23 15:07 ` Myklebust, Trond
2012-06-23 15:52 ` Myklebust, Trond
2012-06-23 15:57 ` Fields James
2012-06-23 16:09 ` Fields James [this message]
2012-06-24 5:12 ` Namjae Jeon
2012-06-25 11:30 ` Fields James
2012-06-26 5:51 ` Namjae Jeon
2012-06-26 11:10 ` Fields James
2012-06-26 11:57 ` Namjae Jeon
2012-06-23 15:59 ` Chuck Lever
2012-06-24 4:49 ` Namjae Jeon
2012-06-24 4:44 ` Namjae Jeon
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=20120623160923.GB10787@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=a.sahrawat@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=linkinjeon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=t.vivek@samsung.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
all inboxes | Powered by JetHome®