From: "J. Bruce Fields" <bfields@fieldses.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
"Trond.Myklebust@netapp.com" <Trond.Myklebust@netapp.com>,
Amit Sahrawat <a.sahrawat@samsung.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: [Problem]NFS Server – Umount results in Device Busy.
Date: Mon, 11 Jun 2012 08:28:00 -0400 [thread overview]
Message-ID: <20120611122800.GE7654@fieldses.org> (raw)
In-Reply-To: <4FD1242E.1010909@panasas.com>
On Fri, Jun 08, 2012 at 12:59:10AM +0300, Boaz Harrosh wrote:
> On 06/07/2012 02:33 PM, J. Bruce Fields wrote:
>
> > On Thu, Jun 07, 2012 at 11:13:04AM +0300, Boaz Harrosh wrote:
>
>
> >
> > I'm not sure how adding an "unmount" rpc to the protocol would really
> > help here, if that's what you're asking for.
> >
>
>
> Please elaborate a bit. I'm not familiar with the details of this
> discussion.
The mount protocol used with NFSv2/v3, for example, has mount/unmount
calls, and I seem to recall problems with keeping the list of mounted
clients accurate in the face of unreliable clients and networks.
I guess you could add the same but make them subject to the lease, so a
client would be assumed "unmounted" if it lost its lease. I don't know.
But the reported problems here sound like just simple bugs, so I'm not
interested in such discussion till the bugs are investigated and fixed
and someone explains what problem then remains to be solved.
--b.
next prev parent reply other threads:[~2012-06-11 12:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 7:47 Re: Re: [Problem]NFS Server – Umount results in Device Busy Namjae Jeon
2012-06-07 8:13 ` Boaz Harrosh
2012-06-07 9:43 ` Namjae Jeon
2012-06-07 10:16 ` Boaz Harrosh
2012-06-07 10:36 ` Namjae Jeon
2012-06-07 11:33 ` J. Bruce Fields
2012-06-07 21:59 ` Boaz Harrosh
2012-06-07 22:05 ` Boaz Harrosh
2012-06-08 7:23 ` Namjae Jeon
2012-06-11 12:28 ` J. Bruce Fields [this message]
2012-06-07 23:41 ` Namjae Jeon
-- strict thread matches above, loose matches on Subject: below --
2012-05-10 6:59 AMIT SAHRAWAT
2012-05-10 6:59 ` AMIT SAHRAWAT
2012-05-10 10:38 ` J. Bruce Fields
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=20120611122800.GE7654@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=a.sahrawat@samsung.com \
--cc=bharrosh@panasas.com \
--cc=linkinjeon@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=namjae.jeon@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 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.