On Thu, Jan 18, 2001 at 08:12:15PM -0800, Nate Amsden wrote:
Ethan Benson wrote:
you might try explicity mounting with -o vers=2 to make sure your not
getting stuff from the nfsv3 servers. upgrading to 2.2.18 and NFSv3
would be better though ;-)
so you have the NFS3 option on? i left
because ethan bensen said it was good (hi ethan! :) ) i decided
to try out the kernel mode nfsd in 2.2.18(on all my other boxes
i use user mode nfs). but i get this on my client(running
2.2.17):
Jan 18 07:44:38 aphro kernel: RPC: garbage, retrying 19574
Jan 18 07:44:38 aphro kernel: RPC: garbage,
On Thu, Jan 18, 2001 at 08:35:10AM -0800, Nate Amsden wrote:
because ethan bensen said it was good (hi ethan! :) ) i decided
to try out the kernel mode nfsd in 2.2.18(on all my other boxes
i use user mode nfs). but i get this on my client(running
2.2.17):
Jan 18 07:44:38 aphro kernel: RPC:
On Thu, Jan 18, 2001 at 08:35:10AM -0800, Nate Amsden wrote:
because ethan bensen said it was good (hi ethan! :) ) i decided
to try out the kernel mode nfsd in 2.2.18(on all my other boxes
i use user mode nfs). but i get this on my client(running
2.2.17):
Jan 18 07:44:38 aphro kernel: RPC:
Ethan Benson wrote:
you might try explicity mounting with -o vers=2 to make sure your not
getting stuff from the nfsv3 servers. upgrading to 2.2.18 and NFSv3
would be better though ;-)
so you have the NFS3 option on? i left it off since it was marked
EXPERIMENTAL ..is that where most of the
I have just upgraded my Debian 1.2 to the latest bleeding edge stuff
using HAMM, and have found that my nfsd appears to occasionally go
into oblivion for no apparent reason. I have to stop and restart
(using /etc/init.d/netstd_nfs) periodically as things just hang on the
client machines.
Has
6 matches
Mail list logo