NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
codermotor
Oct 28, 2012Aspirant
X6 Cannot Access Remote NFSv4 Share
I have been using a ReadyNAS X6 for years as a backup server for my LAN's file server. That file server originally ran NFSv2 and then NFSv3 on Redhat/Fedora distros.
Recently I moved the file server to Scientific Linux 6.0 (RHEL) which also upgraded NFS to NFSv4. Since then, my FrontView backup jobs no longer work. They fail with the error
Oddly, if I SSH into the X6, I can manually mount the NFSv4 directory with
So it seems the problem is with whatever code FrontView uses to mount the share. The file server exports the share from /etc/exports as
Is there a known solution to this problem?
Recently I moved the file server to Scientific Linux 6.0 (RHEL) which also upgraded NFS to NFSv4. Since then, my FrontView backup jobs no longer work. They fail with the error
Unable to access remote path 192.168.7.200:/home
Oddly, if I SSH into the X6, I can manually mount the NFSv4 directory with
mount -t nfs4 /192.168.7.200/home /mnt
So it seems the problem is with whatever code FrontView uses to mount the share. The file server exports the share from /etc/exports as
/var/nfs4exports/home eight(rw,no_root_squash,sync)(where "eight" is the ReadyNAS).
Is there a known solution to this problem?
1 Reply
- codermotorAspirantSolved:
I've found that while the ReadyNAS X6 does indeed support NFSv4, apparently FrontView has some separate problems with it. At least as far as the X6 being an NFS client.
My solution applies to the server side of the remote NFSv4 server:
Exporting the share/dir using the version 4 file system in /etc/exports(e.g.)/var/nfs4exports/exported_directory readynas(rw,no_root_squash,sync)
(where /var/nfs4exports is the root of the exported NFSv4 file system) does not work for the ReadyNAS client.
Instead, I had use the NFSv3/2 style just for the X6 (e.g.)/exported_directory readynas(rw,no_root_squash,sync)
in a separate export line.
Normally, I would export exported_directory to the X6's entire subnet like this:/var/nfs4exports/exported_directory 192.168.7.0(rw,sync)
But now I have to export that directory to each box on the subnet explicitly, since if one exports the NFSv4 file system to the whole subnet, and then exports the same directory to a specific NFSv3 box on that same subnet, NFS uses the first export (i.e. the v4 one) and ignores the other one.
So, this works (where 192.168.7.201 is the X6):### For NFSv4 clients
/var/nfs4exports/exported_directory 192.168.4.0/24(rw,sync)\
192.168.5.0/24(rw,sync)\
192.168.7.202(rw,sync)\
192.168.7.203(rw,sync)\
192.168.8.0/24(rw,sync)\
192.168.10.0/24(rw,sync)\
192.168.7.207(rw,sync,insecure)\
### Export to an NFSv3 client
/exported_directory 192.168.7.201(rw,sync,no_root_squash)
This does not work:/var/nfs4exports/home 192.168.7.0/24(rw,sync)
as NFS sees that both exports are in the same subnet, and so uses only the first entry.
/home 192.168.7.201(rw,sync,no_root_squash)
I'm wondering if FrontView does not properly see the NFS remote host as a version 4 server. If the NFS version can't be automatically detected by FrontView, then there should probably be an option to the Backup dialogs to specify the NFS version explicitly. Because I only use my X6 as a backup server, I suppose I could just add an entry in /etc/fstab to mount my remote server at boot time, but I don't know if that change will persist on reboot of the NAS.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!