FYI -- examining nfs versions I found I was using a user-side nfs-client. Am
trying "switching" to server-side...but keep getting side-tracked on other
problems.
So far haven't gotten kernel-based nfs server to work remotely -- works
"locally" (using autofs & /net/"server"/filesys), but on client -- if I
restart "nfsserver" & try /net/server on client, client will create
mount points (and showmount -e from client works).
But after the mount points are created, if I try to access any, the
mount-points get dynamically removed as I access each one, and
showmount -e <server> returns:
rpc mount export: RPC: Unable to receive; errno = Connection refused;
The problem seems party on server -- since if I /etc/rc.d/nfsserver restart,
showmount will start working "again", and I can get an automount from a
client to remount all of the server-exported filesystems.
I keep trying different options, but so far, no luck. Haven't
responded, since I keep thinking I should be able to fix this -- it's just
a "config" problem. Sigh...
Joseph Loo wrote:
I routinely move files 3 to 4 Gbytes from xfs to jfs system with no
problems. I am running the 2.6.22 kernel thugh and using open suse 10.3
Could you list the /etc/exports file and the rpms associated with the
nfs server and the nfs client.
----
/etc/exports:
/backups astara(async,rw,no_root_squash,no_subtree_check)
/Share astara(async,rw,no_root_squash,no_subtree_check)
/Share 192.168.3.0/255.255.255.0(async,ro,no_subtree_check)
/home astara(async,rw,no_root_squash,no_subtree_check)
====
client & server running rpms:
nfs-kerenel-server-1.1.0-8
nfsidmap-0.20-21
nfs-client-1.1.0-8;
Another thing you could do is to enable automount and uncomment
the /net. There you can try to copy a large file say your machine is
"hello" via "cp /net/hello/big.file /net/hello/big,file.copy" This will
help to determine if your nfs server is properly configured.
---
As mentioned in passing above -- I have enabled this --
it works on the server, but not from the client -- on client,
will mount the exported filesystems, but I it acts like it is
the remote mountd (RPC:Unable to receive") on server that seems
to be failing.
I'm trying to see why mountd appears to be
dying. Haven't used nfs4 enough to know "normal", but I see
4*[nfsd] but only 1 [nfsd4]. Not sure if that is right or
not...
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
