If you do, please add your comments. It was a problem on the server. After another reboot of the client, I found that the volumes were again not mounted. So I mounted them by hand. But I found one volume which could not be mounted. I had forgotten that this client mounted NFS volumes from two different servers.
I went to the other NFS server, I killed mountd and nfsd and then restarted them. Then the volumes mounted properly on the client. I was compiling a kernel on my fast box and while I was waiting I set up the slow box.
Here is what I did on the box which contained most of my distfiles. The following copied the distfiles from the client to the server mybox. On the client box, I did this:. The above retains the existing distfiles in case of a problem.
It then mounts the remote directory where it normally resides. To make this mount permanent, see Mounting the remote volume. All exports from a single file system must be on the same export entry. You must be logged in to post a comment. NFS — sharing file systems across a network This article was originally written in November , but has only just been completed.
Join Date: Dec On NFS client, what is the output of: Code :. Join Date: Mar Solaris 10 NFS client cannot mount a share from a Windows server. I have a Solaris 10 server, I'm trying to mount a share from a Windows nfs server. Shell Programming and Scripting. I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people.
Fails to mount the server The server came up fine but most Not able to mount NFS share on client side. When i tried to mount the nfs i see this error message mount -t nfs Even the other Linux SuSE clients in the same room are mounting successfully with defaults without NFS client Mount script after boot.
I'd like to check that nfs is up, then do the client mount all from a startup See my first post. FreeBSD 4. Results of rpcinfo -p: quote: program vers proto port 2 tcp portmapper 2 udp portmapper 3 udp mountd 3 tcp mountd 1 udp mountd 1 tcp mountd nfsd doesn't appear to be registered, strangly in the past when I execute nfsd -r to re-register nfs with portmap i always get the same errors - but this is the results of rpcinfo -p after re-registering nfsd: quote: program vers proto port 2 tcp portmapper 2 udp portmapper 3 udp mountd 3 tcp mountd 1 udp mountd 1 tcp mountd 2 udp nfs 3 udp nfs Quite strange.
Anyways, I just fixed the permission problem for sure by adding the system's IP to the allowed listing , and still received the same connection refused message. Any ideas from anyone?
0コメント