On Nov 3, 2008, at Nov 3, 2008, 5:20 PM, Peter Staubach wrote:
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.
As opposed to the support "call" we got today? ;-)
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.
I think our petard is hoist either way. Better to avoid data
corruption, by whatever means.
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?
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
