:
:Firstly, I have no intention of committing this patch anytime soon,
:but I think you are mistaken in what it does. Unless I messed up,
:it will never allow "uninterruptible" mounts to be interrupted by
Oops, sorry about that. Today is not one of my better days.
>
> No, I haven't gone mad and decided to make all NFS mounts soft
> to "fix" all NFS problems :-)
>
I once asked Bob Lyon (who is still at Legato) about what he thought needed to
happen to 'fix' NFS (after all, it was he and Rusty Sandberg who did the
initial work on all this).
His response was
In message <[EMAIL PROTECTED]>, Matt Dillon writes:
> Ian, please don't do this. The whole point of having an uninterruptable
> mount is so the client can survive a server reboot or network failure.
> Doing this destroys uninterruptable semantics.
Firstly, I have no intention of committing
Ian, please don't do this. The whole point of having an uninterruptable
mount is so the client can survive a server reboot or network failure.
Doing this destroys uninterruptable semantics.
If you want to flag uninterruptable mounts in a special way when someone
tries to umount th
In message <[EMAIL PROTECTED]>, Maxim Sobolev writes:
>I found that after introduction of the new RPC NFS client is no longer
>able to recover from server crash (both cluent and server are 5-CURRENT
>systems). After a well known `nfs server not responding' message, client
>hangs and even though se
Hi,
I found that after introduction of the new RPC NFS client is no longer
able to recover from server crash (both cluent and server are 5-CURRENT
systems). After a well known `nfs server not responding' message, client
hangs and even though server comes back in a minute or two it doesn't
recover
