You are not logged in.
Pages: 1
Topic closed
Hi,
I used to use nfs3 sucessfully but now I upgraded to nfsv4
I followed http://wiki.archlinux.org/index.php/NFSv4 to the letter.
/etc/exports on server:
/home 192.168.1.213(fsid=0,sync,no_subtree_check,no_root_squash,ro)
/home/dieter 192.168.1.213(sync,no_subtree_check,no_root_squash,rw) ws(sync,no_subtree_check,no_root_squash,rw)
/home/www 192.168.1.213(sync,no_subtree_check,no_root_squash,rw) ws(sync,no_subtree_check,no_root_squash,rw)
/home/backup 192.168.1.213(sync,no_subtree_check,no_root_squash,rw) ws(sync,no_subtree_check,no_root_squash,rw)
/home/hilde 192.168.1.65(sync,no_subtree_check,no_root_squash,rw,nohide)
Now I try to mount /home/hilde on 192.168.1.65:
[root@hilde-compaq-arch ~]# mount /home/hilde/server/
mount.nfs4: mounting 192.168.1.2:/hilde failed, reason given by server:
No such file or directory
Oddly enough, there is also this:
[root@hilde-compaq-arch ~]# /etc/rc.d/nfs-common stop
:: Stopping rpc.idmapd daemon [FAIL]
[root@hilde-compaq-arch ~]# /etc/rc.d/nfs-common start
:: Starting rpc.statd daemon [FAIL]
[root@hilde-compaq-arch ~]# ps aux | grep statd
nobody 2978 0.0 0.0 10160 804 ? Ss Jul30 0:00 /usr/sbin/rpc.statd
root 6369 0.0 0.0 7784 964 pts/0 S+ 22:55 0:00 grep statd
Any help appreciated...
Dieter
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
Not to sure but did you run exportfs again on the server?
Offline
Not to sure but did you run exportfs again on the server?
yeah. I ran exportfs -r -v. (hell I even tried restarting all related daemons and rebooting the server ;-))
I do wonder why I can't start nfs-common on the client though..
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
I was seeing this problem and found that doing "modprobe nfs" on the client before trying to mount solved it.
EDIT: wait, perhaps that was the solution to a different error I was seeing. Another fix I found, perhaps it's the fix to this problem, was to adjust the /etc/hosts.allow file on the server. Mine now looks like this:
#
# /etc/hosts.allow
#
nfsd: 192.168.1.0/255.255.255.0
rpcbind: 192.168.1.0/255.255.255.0
mountd: 192.168.1.0/255.255.255.0
# End of file
Last edited by Profjim (2009-08-04 20:53:18)
Offline
I was seeing this problem and found that doing "modprobe nfs" on the client before trying to mount solved it.
[root@hilde-compaq-arch ~]# mount /home/hilde/server/
mount.nfs4: mounting 192.168.1.2:/hilde failed, reason given by server:
No such file or directory
[root@hilde-compaq-arch ~]# modprobe nfs
[root@hilde-compaq-arch ~]# mount /home/hilde/server/
mount.nfs4: mounting 192.168.1.2:/hilde failed, reason given by server:
No such file or directory
[root@hilde-compaq-arch ~]# /etc/rc.d/nfs-common start
:: Starting rpc.statd daemon FAIL
EDIT: wait, perhaps that was the solution to a different error I was seeing. Another fix I found, perhaps it's the fix to this problem, was to adjust the /etc/hosts.allow file on the server. Mine now looks like this:
# # /etc/hosts.allow # nfsd: 192.168.1.0/255.255.255.0 rpcbind: 192.168.1.0/255.255.255.0 mountd: 192.168.1.0/255.255.255.0 # End of file
Ah yes, I had a mistake here. But still this doesn't change anything client side
thanks for the help
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
I just noticed, when I reboot the pc and it mounts the filesystems it says "unknown filesystem:rpc_pipefs" (or something like that), but oddly enough, it did have the filesystem mounted after booting.
So I removed the line from the filesystem and rebooted, and some process seems to automagically mount it, so I guess you don't need to do it explicitly like http://wiki.archlinux.org/index.php/NFSv4 said.
however, the rest of my problem remains
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
Aha i'm now a step further. Apparantly nfs-common is what does the mounting of the rpc_pipefs. If I umount it manually and then start nfs-common on the client, then it wants to start. hooray.
But still..
on server (ip 192.168.1.2)
[root@dieter-p4sci-arch ~]# exportfs -r -v
exporting ws:/home/backup
exporting ws:/home/www
exporting ws:/home/dieter
exporting 192.168.1.213:/home/media
exporting 192.168.1.64:/home/media
exporting 192.168.1.213:/home/media/1tbdisk
exporting 192.168.1.65:/home/hilde
exporting 192.168.1.213:/home/backup
exporting 192.168.1.213:/home/www
exporting 192.168.1.213:/home/dieter
exporting 192.168.1.213:/home
exporting 192.168.1.65:/home
on client ( ip 192.168.1.65)
[root@hilde-compaq-arch ~]# mount 192.168.1.2:hilde /home/hilde/server/ -t nfs4
mount.nfs4: mounting 192.168.1.2:hilde failed, reason given by server:
No such file or directory
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
FYI my /etc/exports listed the 'root' fs ('/home') only for another host. I changed it so it also includes the client in question. However, no change (after restarting all daemons)
/home 192.168.1.213(fsid=0,sync,no_subtree_check,no_root_squash,ro) 192.168.1.65(fsid=0,sync,no_subtree_check,no_root_squash,rw,nohide)
/home/dieter 192.168.1.213(sync,no_subtree_check,no_root_squash,rw) ws(sync,no_subtree_check,no_root_squash,rw)
/home/www 192.168.1.213(sync,no_subtree_check,no_root_squash,rw) ws(sync,no_subtree_check,no_root_squash,rw)
/home/backup 192.168.1.213(sync,no_subtree_check,no_root_squash,rw) ws(sync,no_subtree_check,no_root_squash,rw)
/home/hilde 192.168.1.65(sync,no_subtree_check,no_root_squash,rw,nohide)
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
[root@hilde-compaq-arch ~]# mount 192.168.1.2:hilde /home/hilde/server/ -t nfs4
mount.nfs4: mounting 192.168.1.2:hilde failed, reason given by server:
No such file or directory
Just grasping at straws...
1. You've verified /home/hilde/server/ exists on client machine? (though error report doesn't seem to indicate any problem with that)
2. Does "mount 192.168.1.2:/hilde /home/hilde/server/ -t nfs4" work?
3. Does "mount 192.168.1.2:/home/hilde /home/hilde/server/ -t nfs4" work?
Though I agree with you that what you're already trying should work. (Though I'm a NFS newbie myself, so my agreement isn't worth much here.)
Also, I've never tried putting the "-t fstype" options at the end of the mount statement like you do. Are you sure that's OK? I've always done, for example:
mount -t nfs4 192.168.1.2:/hilde /home/hilde/server/
Last edited by Profjim (2009-08-09 19:59:06)
Offline
Dieter@be wrote:[root@hilde-compaq-arch ~]# mount 192.168.1.2:hilde /home/hilde/server/ -t nfs4
mount.nfs4: mounting 192.168.1.2:hilde failed, reason given by server:
No such file or directoryJust grasping at straws...
1. You've verified /home/hilde/server/ exists on client machine? (though error report doesn't seem to indicate any problem with that)
2. Does "mount 192.168.1.2:/hilde /home/hilde/server/ -t nfs4" work?
3. Does "mount 192.168.1.2:/home/hilde /home/hilde/server/ -t nfs4" work?Though I agree with you that what you're already trying should work. (Though I'm a NFS newbie myself, so my agreement isn't worth much here.)
1) exists
2) what the f****. This works fine. now I'm totally confused. All of a sudden my earlier mount command started working, and so is the fstab entry. weird.
thanks btw
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
Well, 2 does differ from what you were using by using "host:/path" instead of "host:path"
Offline
Well, 2 does differ from what you were using by using "host:/path" instead of "host:path"
Yeah but now both variants work Maybe it was my fsid fix that took a lot of time (even after re-exporting to be in effect :s )
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
you need allow 192.168.1.65 on the root(fsid=0) for /home/hidle
# /etc/exports
/home 192.168.1.213(fsid=0,...) 192.168.1.65(fsid=0,...)
/home/dieter 192.168.1.213(...)
...
/home/hilde 192.168.1.65(...)
Last edited by GutenYe (2014-01-04 10:18:37)
Linux, Vim, Ruby, Javascript and Go.
Offline
Welcome to our forums GutenYe - please take a minute to have a read of our Forum Etiquette. Specifically we like to leave the dead to rest in peace: https://wiki.archlinux.org/index.php/Fo … Bumping.22
Closing.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Pages: 1
Topic closed