All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Jim Rees <rees@umich.edu>,
	"Brian J. Murrell"
	<brian-SquOHqY54CVWr29BmMi2cA@public.gmane.org>,
	linux-nfs@vger.kernel.org
Subject: Re: stuck/hung nfsv4 mounts
Date: Mon, 03 Nov 2008 17:20:29 -0500	[thread overview]
Message-ID: <490F792D.6010208@redhat.com> (raw)
In-Reply-To: <2C93A491-1277-42B6-9CED-FC06A85174D5@oracle.com>

Chuck Lever wrote:
> On Nov 3, 2008, at Nov 3, 2008, 12:37 PM, Trond Myklebust wrote:
>> On Mon, 2008-11-03 at 12:25 -0500, Jim Rees 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?
>>
>> It might make sense if we were to fix up the granularity of the recovery
>> routines so that we are able to recover all the state associated with
>> just a single open owner or lock owner. Currently we'd have to recover
>> all the state associated with that server.
>>
>> IOW: we might be able to fix things up in the future, but right now,
>> NFSv4+soft is not a good idea.
>
> Two cents worth:  Until NFSv4+soft works reasonably well, I wouldn't 
> have any problem with making "soft" a no-op for nfs4 mounts. 

It may be the right thing to do in the short term, but it will
generate calls to support organizations.  Anyone trying it will
wonder why it doesn't work "as it used to".  That sort of thing.
When that happens, we will be forced to do something and not at
our choice of time.

Perhaps we should deny such mount attempts because at least that
would be obvious what was happening?  Perhaps we should also
deny NFSv4 mounting over UDP?

       ps

  reply	other threads:[~2008-11-03 22:20 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 [this message]
2008-11-03 22:47               ` Chuck Lever
2008-11-04 16:03                 ` Peter Staubach
2008-11-03 17:38       ` Benny Halevy
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=490F792D.6010208@redhat.com \
    --to=staubach@redhat.com \
    --cc=brian-SquOHqY54CVWr29BmMi2cA@public.gmane.org \
    --cc=chuck.lever@oracle.com \
    --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.