From: Benny Halevy <bhalevy@panasas.com>
To: Jim Rees <rees@umich.edu>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
"Brian J. Murrell"
<brian-SquOHqY54CVWr29BmMi2cA@public.gmane.org>,
linux-nfs@vger.kernel.org
Subject: Re: stuck/hung nfsv4 mounts
Date: Mon, 03 Nov 2008 19:38:31 +0200 [thread overview]
Message-ID: <490F3717.1030407@panasas.com> (raw)
In-Reply-To: <20081103172529.GA9008@citi.umich.edu>
On Nov. 03, 2008, 19:25 +0200, Jim Rees <rees@umich.edu> wrote:
> Trond Myklebust wrote:
>
> BTW: NFSv4 + soft == BAD BAD BAD!
>
> Maybe this combination should be prohibited. Does it make any sense given
> the stateful nature of v4?
>From the usage perspective it allows the application to fail rather
than stall. If it would have been implemented similar to "intr"
and return an error to the app as if the system call had received
an interrupt but under the covers the RPC will be processed to
completion (or graceful cleanup) I think it might still make sense for nfs4.
Until then this combination should at least be warned about.
Benny
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-03 17:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 15:05 stuck/hung nfsv4 mounts Brian J. Murrell
2008-11-03 16:59 ` Trond Myklebust
[not found] ` <1225731544.6958.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-11-03 17:25 ` Jim Rees
2008-11-03 17:37 ` Trond Myklebust
[not found] ` <1225733834.6958.12.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-11-03 21:40 ` Chuck Lever
2008-11-03 22:20 ` Peter Staubach
2008-11-03 22:47 ` Chuck Lever
2008-11-04 16:03 ` Peter Staubach
2008-11-03 17:38 ` Benny Halevy [this message]
2008-11-03 17:50 ` Brian J. Murrell
2008-11-03 19:58 ` Kevin Coffman
[not found] ` <4d569c330811031158r26963e0w5bcf8331e0fb14b7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-03 20:09 ` Brian J. Murrell
2008-11-03 20:28 ` Kevin Coffman
[not found] ` <4d569c330811031228r5bb9aefs7a970303910810e2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-03 21:12 ` Brian J. Murrell
2008-11-03 22:33 ` Kevin Coffman
[not found] ` <4d569c330811031433k7ae18d4enfbda349e8f90a951-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-03 23:45 ` Brian J. Murrell
2008-11-04 1:24 ` Brian J. Murrell
2008-11-04 15:14 ` Brian J. Murrell
2008-11-04 17:22 ` Kevin Coffman
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=490F3717.1030407@panasas.com \
--to=bhalevy@panasas.com \
--cc=brian-SquOHqY54CVWr29BmMi2cA@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
--cc=trond.myklebust@fys.uio.no \
/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.