NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NFS broken on NV+ with Raidiator v4.1.10
Hi, I tried upgrading to RAIDiator version 4.1.10 a couple weeks ago and noticed that NFS started behaving badly. On my clients, I couldn't always mount drives, I'd get access denied errors, "no locks available", etc. I found out that rpc.mountd was crashing with a segmentation fault on the NV+. After many digressions where I tried to fix things, I gave up and rolled back to 4.1.9. (I got a "checksum mismatch" error so I had to apply the firmware using the trick at http://www.readynas.com/forum/viewtopic.php?f=65&t=28048&p=155032#p155032 .) Things are working OK now so far. Has anyone else seen this?
Ethan
Ethan
3 Replies
Replies have been turned off for this discussion
- Can you provide syslogs of the rpc.mountd segfaults?
- Here's a typical section of log from syslog. Note that mountd doesn't signal that it crashed. I ran it "by hand" using /usr/sbin/rpc.mountd -f -D all, and again, no messages about why it was crashing, just similar messages about receiving requests. (It always crashed after handling just one.)
Oct 9 18:45:44 tularosa mountd[4014]: authenticated unmount request from 192.168.1.124:834
for /c/media (/c/media)
Oct 9 18:54:02 tularosa mountd[4062]: authenticated mount request from 192.168.1.124:852 fo
r /c/media (/c/media)
Oct 9 18:57:20 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 18:57:20 tularosa kernel: lockd: cannot unmonitor 192.168.1.124
Oct 9 18:57:55 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 18:57:55 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 18:58:30 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 18:58:30 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 18:59:05 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 18:59:05 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 18:59:40 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 18:59:40 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 19:00:15 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 19:00:15 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 19:00:50 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 19:00:50 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 19:01:25 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 19:01:25 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 19:02:00 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 19:02:00 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 19:02:35 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 19:02:35 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 19:03:10 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 19:03:10 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 19:03:45 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 19:03:45 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 19:04:20 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 19:04:20 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 19:04:55 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 19:04:55 tularosa kernel: lockd: cannot monitor 192.168.1.124
Oct 9 19:05:30 tularosa kernel: statd: server localhost not responding, timed out
Oct 9 19:05:30 tularosa kernel: lockd: cannot monitor 192.168.1.124 - Hopefully someone from NTGR will come along to try and reproduce it.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
