Lately my NFS server stops responding with the following errors in dmesg. I have to umount the share and remount it. It's then fine for a random amount of time and then it starts to act up again.

 

newnfs: server '192.168.1.10' error: fileid changed. fsid 0:0: expected fileid 0x9010000000000a0, got 0x2500000055ea0a. (BROKEN NFS SERVER OR MIDDLEWARE) 
newnfs: server '192.168.1.10' error: fileid changed. fsid 0:0: expected fileid 0x9010000000000a0, got 0x2500000055ea0a. (BROKEN NFS SERVER OR MIDDLEWARE) 
newnfs: server '192.168.1.10' error: fileid changed. fsid 0:0: expected fileid 0x9010000000000a0, got 0x2500000055ea0a. (BROKEN NFS SERVER OR MIDDLEWARE) 
newnfs: server '192.168.1.10' error: fileid changed. fsid 0:0: expected fileid 0x9010000000000a0, got 0x2500000055ea0a. (BROKEN NFS SERVER OR MIDDLEWARE) 
newnfs: server '192.168.1.10' error: fileid changed. fsid 0:0: expected fileid 0x9010000000000a0, got 0x2500000055ea0a. (BROKEN NFS SERVER OR MIDDLEWARE) 
newnfs: server '192.168.1.10' error: fileid changed. fsid 0:0: expected fileid 0x9010000000000a0, got 0x2500000055ea0a. (BROKEN NFS SERVER OR MIDDLEWARE) 
newnfs: server '192.168.1.10' error: fileid changed. fsid 0:0: expected fileid 0x9010000000000a0, got 0x2500000055ea0a. (BROKEN NFS SERVER OR MIDDLEWARE) 
newnfs: server '192.168.1.10' error: fileid changed. fsid 0:0: expected fileid 0x9010000000000a0, got 0x2500000055ea0a. (BROKEN NFS SERVER OR MIDDLEWARE) 
newnfs: server '192.168.1.10' error: fileid changed. fsid 0:0: expected fileid 0x9010000000000a0, got 0x2500000055ea0a. (BROKEN NFS SERVER OR MIDDLEWARE) 
newnfs: server '192.168.1.10' error: fileid changed. fsid 0:0: expected fileid 0x9010000000000a0, got 0x2500000055ea0a. (BROKEN NFS SERVER OR MIDDLEWARE) 
newnfs: Logged 10 times about fileid corruption; going quiet to avoid spamming logs excessively. (Limit is: 10).

 

Edited November 22, 20196 yr by gregfitz
formatting

It appears there was a file on disk1 and then possibly it got moved maybe to cache or unassigned device?

You can probably get rid of the messages: go to: Settings/Global Share Settings, change Tunable (support hard links) to No.  But hard links in user shares will not be supported, but you may not need that anyway.

Please report back with findings.

I am also having this issue when using fstab and also autofs (which I moved to trying to solve the fstab issue). I am wondering if there is a good solution.

 

I am sharing via nfs movies, tv and some other videos locations from my unraid machine to another computer on my network. 

 

I get the following:

 

plex@dionysus:/mnt/media$ ls
ls: cannot access 'TvShows': Stale file handle
Home-Movies  Movies  TvShows
 

and then when enabling logging in autofs. I see the following in the logs:

 

Apr 9 12:49:51 dionysus kernel: [684639.585302] fsid 0:73: expected fileid 0x901000025857ba7, got 0x27000011a31bce
Apr 9 12:49:51 dionysus kernel: [684639.585797] NFS: server 192.168.86.2 error: fileid changed
Apr 9 12:49:51 dionysus kernel: [684639.585797] fsid 0:73: expected fileid 0x901000025857ba7, got 0x27000011a31bce

 

I am wondering if this is an issue with using a cache device for these locations? Could it be that this is caused by the files initially being on cache and then getting moved to the array?

Edited April 9, 20206 yr by WexfordStyle