NFS mount problem SOLVED!!!!!

[wilsonal2]

For everyone that had problems mounting the Valkyrie NAS via NFS I have the solution. The problem was that every time you tried to mount the NAS you got a error message of “mount.nfs: access denied by server while mounting 10.25.70.90:/mnt/data/public” (my Valkyrie NAS ip is 10.25.70.90) and no matter what you tried you could not get it to work. Even though using “showmount -e 10.25.70.90” replied with the NAS export list (/mnt/data/public 10.25.70.*) and “rpcinfo -p 10.25.70.90” showed that the NAS was listening to the correct ports and ready to accept a nfs mount request for nfs versions 2, 3, 4. Well like so many things that we have learned about the Valkyrie what is says and what is does is not the same thing. The Valkyrie does support NFS mounts with version 3, 4 or the firmware (I'm using ver. 4) BUT ONLY USING NFS3 NOT NFS4. If you use “mount -v -t nfs -o vers=3 10.25.70.90:/mnt/data/public /mnt/NAS” (I'm running Fedora 16) the Valkyrie will mount via NFS just fine, every time. Since most modern linux OS default to NFSv4 and the Valkyrie rpcinfo says it will accept NFSv4 your system does not try NFSv3 or NFSv2 to mount. By forcing your system to use NFSv3 you can now mount the NAS export just fine.

Also mounting via NFS the I/O speed to the device improves dramatically. I have not done benchmark test yet but transferring 735M using a 1gig network took only 40 sec. For me this was better then I ever had in the past using cifs to mount

[heymanj]

For everyone that had problems mounting the Valkyrie NAS via NFS I have the solution. The problem was that every time you tried to mount the NAS you got a error message of “mount.nfs: access denied by server while mounting 10.25.70.90:/mnt/data/public” (my Valkyrie NAS ip is 10.25.70.90) and no matter what you tried you could not get it to work. Even though using “showmount -e 10.25.70.90” replied with the NAS export list (/mnt/data/public 10.25.70.*) and “rpcinfo -p 10.25.70.90” showed that the NAS was listening to the correct ports and ready to accept a nfs mount request for nfs versions 2, 3, 4. Well like so many things that we have learned about the Valkyrie what is says and what is does is not the same thing. The Valkyrie does support NFS mounts with version 3, 4 or the firmware (I'm using ver. 4) BUT ONLY USING NFS3 NOT NFS4. If you use “mount -v -t nfs -o vers=3 10.25.70.90:/mnt/data/public /mnt/NAS” (I'm running Fedora 16) the Valkyrie will mount via NFS just fine, every time. Since most modern linux OS default to NFSv4 and the Valkyrie rpcinfo says it will accept NFSv4 your system does not try NFSv3 or NFSv2 to mount. By forcing your system to use NFSv3 you can now mount the NAS export just fine.

Also mounting via NFS the I/O speed to the device improves dramatically. I have not done benchmark test yet but transferring 735M using a 1gig network took only 40 sec. For me this was better then I ever had in the past using cifs to mount

I'm happy to hear that things are working for you - I wish I could say that the solution was a universal fix :-(

[jerry@unix Download]$ sudo mount -v -t nfs -o vers=3 diskspace:/mnt/data/public /mnt/diskspace
mount.nfs: timeout set for Fri Mar 16 21:38:24 2012
mount.nfs: trying text-based options 'vers=3,addr=192.168.1.30'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.30 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.30 prog 100005 vers 3 prot UDP port 2520
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting diskspace:/mnt/data/public
[jerry@unix Download]$ showmount -e diskspace
bash: showmount: command not found
You have new mail in /var/spool/mail/jerry
[jerry@unix Download]$ sudo showmount -e diskspace
Export list for diskspace:
/mnt/data/public 192.168.1.*

I'll gladly entertain other thoughts/ideas

[wilsonal2]

what does the output of "rpcinfo -p 192.168.1.30" look like? Just wondering if everything is running and has a open port. Also use the root telnet login to the NAS and confirm that /mnt/data/public has Full Permissions (777) also make sure that your mount point (/mnt/diskspace) has the same Full Permissions. since the uid's between the two systems do not match, both need to be open. Also try mounting as root (su -) and use the numerical IP address for the NAS

[heymanj]

what does the output of "rpcinfo -p 192.168.1.30" look like? Just wondering if everything is running and has a open port. Also use the root telnet login to the NAS and confirm that /mnt/data/public has Full Permissions (777) also make sure that your mount point (/mnt/diskspace) has the same Full Permissions. since the uid's between the two systems do not match, both need to be open. Also try mounting as root (su -) and use the numerical IP address for the NAS

To me it looks like an incompatibility introduced somewhere in nfs-utils-clients. I just installed Mandriva 2006 (yes, a 6 yr old distro I happened to have on cd) and was able to successfully mount the Valkyrie without any issues.

# showmount -e 192.17.1.30
Export list for 192.168.1.30:
/mnt/data/public 192.168.1.*
# mount 192.169.1.30:/mnt/data/public /mnt/disk
# cd /mnt/disk
# ls
jerry/ jerry.tgz mageia-dvd-1-x86_64/ usrlocal.tgz
# df
Filesystem Size Used Avail Use% Mounted on
/dev//sdb7 9.5G 1.6G 7.5G 18% /
/dev/sda1 20G 14G 6.2G 69% /mnt/windows
192.168.1.30:/mnt/data/public
915G 95G 775G 11% /mnt/disk
# rpm -aq | grep -i nfs
nfs-utils-clients-1.0.7-6mdk

On my permission denied system (Mageia 1 x86_64)

# rpm -aq | grep -i nfs
nfs-utils-clients-1.2.3-2.3.mga1

for giggles, I just tried the mount command again, and now it works on the x86_64 machine! I have no clue why...

jerry

[heymanj]

To me it looks like an incompatibility introduced somewhere in nfs-utils-clients. I just installed Mandriva 2006 (yes, a 6 yr old distro I happened to have on cd) and was able to successfully mount the Valkyrie without any issues.

# showmount -e 192.17.1.30
Export list for 192.168.1.30:
/mnt/data/public 192.168.1.*
# mount 192.169.1.30:/mnt/data/public /mnt/disk
# cd /mnt/disk
# ls
jerry/ jerry.tgz mageia-dvd-1-x86_64/ usrlocal.tgz
# df
Filesystem Size Used Avail Use% Mounted on
/dev//sdb7 9.5G 1.6G 7.5G 18% /
/dev/sda1 20G 14G 6.2G 69% /mnt/windows
192.168.1.30:/mnt/data/public
915G 95G 775G 11% /mnt/disk
# rpm -aq | grep -i nfs
nfs-utils-clients-1.0.7-6mdk

On my permission denied system (Mageia 1 x86_64)

# rpm -aq | grep -i nfs
nfs-utils-clients-1.2.3-2.3.mga1

for giggles, I just tried the mount command again, and now it works on the x86_64 machine! I have no clue why...

jerry

Power outage. First time I get to try the above since the problem was 'solved' in September. Amazingly, now the
Mandriva 2006.1 system is getting the

mount: diskspace:/mnt/data/public failed, reason given by server: Permission denied

so the above steps no longer work. I've rebooted the Mandriva system, I've rebooted the Valkyrie...

The adventure continues :-(