Quote:
Originally Posted by onebuck
Hi,
Try 'exportfs -ra' to update the table.
|
pipeline is 192.168.1.1: server.
superman is 192.168.1.3: client.
Just to verify everything is ok:
[pipeline:jp/]$ /etc/rc.d/rc.nfsd stop
[pipeline:jp/]$ killall rpc.statd
[pipeline:jp/]$ killall rpc.rquotad
rpc.rquotad: no process killed
[pipeline:jp/]$ killall rpc.mountd
rpc.mountd: no process killed
[pipeline:jp/]$ killall rpc.portmap
rpc.portmap: no process killed
I begin to start nfs.:
[pipeline:jp/]$ /etc/rc.d/rc.nfsd start
Starting RPC portmapper: /sbin/rpc.portmap
Starting RPC NSM (Network Status Monitor): /sbin/rpc.statd
Starting NFS server daemons:
/usr/sbin/exportfs -r
/usr/sbin/rpc.rquotad
/usr/sbin/rpc.nfsd 8
/usr/sbin/rpc.mountd
[pipeline:jp/]$ /usr/sbin/exportfs
/mnt/commun/tmp
192.168.1.3
[pipeline:jp/]$
All seem ok on the server. Now from the client:
[superman:jp/]$ /usr/sbin/showmount -e 192.168.1.1
Export list for 192.168.1.1:
/mnt/commun/tmp 192.168.1.3
[superman:jp/]$
So the client sees the partition to mount. Try to mount the partition:
[superman:jp/]$ mount -v -t nfs 192.168.1.1:/mnt/commun/tmp /mnt/pipeline
mount.nfs: timeout set for Wed Aug 6 19:09:22 2008
mount.nfs: text-based options: 'addr=192.168.1.1'
mount.nfs: internal error
[superman:jp/]$
And then:
[superman:jp/]$ /usr/sbin/showmount -e 192.168.1.1
[superman:jp/]$
The client does not see anymore the server. But the server continues to
export:
[pipeline:jp/]$ /usr/sbin/exportfs
/mnt/commun/tmp
192.168.1.3
[pipeline:jp/]$
There is really something I don't understand here...