NFS folder empty

[Gooberpatrol66]

Hey, when I mount my freenas volume in Manjaro the folder shows up empty.

Results of ls:

ls: reading directory /home/user/Desktop/NFS-share/: Input/output error
total 0

Results of dmesg on the server:

nfsd: can't register svc name

Using version FreeNAS-9.3-STABLE-201501090144

Any help would be appreciated.

 

[DrKK]

Could this be related to #8876?

 

[Gooberpatrol66]

Doesn't look like it. Dig -x works both ways, unlike that guy.

 

[Gooberpatrol66]

Also, I'm not using vSphere or any virtualization

 

[Gooberpatrol66]

Is there a way to look into why nfsd is spewing that error?

 

[Gooberpatrol66]

Looks like I fixed it by resetting to factory defaults, switching to LDAP, and deleting my lagg.

 

[Gooberpatrol66]

Nope, nevermind. I reset it to factory defaults now and turn on NFS and the very first thing it does is spew that error again.

 

[cyberjock]

Why not run a newer version than Jan 2015? There's literally been hundreds of bug fixes since that build...

 

[Gooberpatrol66]

I thought I was running the most recent version from the webui...
Do the factory defaults reset the version?

 

[cyberjock]

Uhh.. I don't even understand your question. It is nonsensical to me.

Upgrading does NOT reset your settings or anything..... if that's what you are asking.

 

[Gooberpatrol66]

Sorry, I'm stupid.

I can confirm that I'm running FreeNAS-9.3-STABLE-201509022158 right now and I'm still getting the error.

 

[cyberjock]

What does 'showmount -e' show on the FreeNAS server?

 

[Gooberpatrol66]

What does 'showmount -e' show on the FreeNAS server?

Code:

Exports list on localhost:
/mnt/Vol1/Share1                                              Everyone

 

[cyberjock]

I get that error, and I've ignored it because my NFS works. I tend to think that something on your client has changed, it isn't being mounted on your client for some reason, etc.

You could try mounting the NFS share locally on your FreeNAS in a /tmp/test and see if that works:

# mkdir /tmp/test
# mount -t nfs servernameorIP:/mnt/Vol1/Share1 /tmp/test
# cd /tmp/test
# ls

If the ls output shows you your directory then it's safe to say the server is working fine and the issue is client side. Note that you shouldn't use 127.0.0.1 or localhost in place of "servernameorIP". Preferably you'd want to use the same convention that you use on your client machine(s).

 

[Gooberpatrol66]

Oh geez, I restarted the nfs service on the client and it started working. It must not be starting correctly on bootup.

Strange, it always seemed to output an error before if something was wrong.