I have a NFS share mounted on my desktop. Several times a day I it stops responding and see the following in dmesg on my desktop.
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).
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.