I'm having trouble with 2.6.0-test2's NFS support. The problem has
existed for a few releases (not sure how far back.)
I'm using NFSv3 over UDP. Every time a client makes an NFS mount, the
previous mount is silently dropped. The client assumes that both mounts
are current, but only the more recent mount is functional.
Is this behaviour intentional? Has anybody else experienced it? 2.4.x
is not affected.
- M
http://yallara.cs.rmit.edu.au/~malsmith/
On Monday August 11, [email protected] wrote:
> I'm having trouble with 2.6.0-test2's NFS support. The problem has
> existed for a few releases (not sure how far back.)
>
> I'm using NFSv3 over UDP. Every time a client makes an NFS mount, the
> previous mount is silently dropped. The client assumes that both mounts
> are current, but only the more recent mount is functional.
>
> Is this behaviour intentional? Has anybody else experienced it? 2.4.x
> is not affected.
I'm afraid I don't quite understand your problem.
Could you be a bit more specific, and give examples?
Thanks,
NeilBrown