I've been having my User shares disappear and become inaccessible at times over the past few months with no luck in troubleshooting the issue.  Usually it locks up the entire server and I have to reboot it to gain back access at which point I don't have any relevant logs.  Today they disappeared, I lost access to the shares but the WebUI is still responsive.  I caught these messages in the log:

 

Apr 20 12:32:50 SPE-UNRAID01 kernel: WARNING: CPU: 0 PID: 2947 at fs/nfsd/nfsproc.c:800 nfserrno+0x5a/0x5f
Apr 20 12:32:50 SPE-UNRAID01 kernel: nfsd: non-standard errno: -103
Apr 20 12:32:50 SPE-UNRAID01 kernel: Modules linked in: md_mod coretemp kvm_intel kvm mpt3sas ata_piix raid_class scsi_transport_sas i2c_piix4 i2c_core intel_agp intel_gtt agpgart acpi_cpufreq
Apr 20 12:32:50 SPE-UNRAID01 kernel: CPU: 0 PID: 2947 Comm: nfsd Not tainted 4.9.19-unRAID #1
Apr 20 12:32:50 SPE-UNRAID01 kernel: ffffc90002cb7cb8 ffffffff813a3bf2 ffffc90002cb7d08 ffffffff81951bbe
Apr 20 12:32:50 SPE-UNRAID01 kernel: ffffc90002cb7cf8 ffffffff8104d04c 0000032002cb7d70 0000000005000000
Apr 20 12:32:50 SPE-UNRAID01 kernel: ffff8802356abd48 ffff88011aec1000 ffff8801002e8cc0 ffff880101ac6090
Apr 20 12:32:50 SPE-UNRAID01 kernel: Call Trace:
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff813a3bf2>] dump_stack+0x61/0x7e
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff8104d04c>] __warn+0xb8/0xd3
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff8104d0ad>] warn_slowpath_fmt+0x46/0x4e
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff810e660e>] ? list_lru_add+0xf1/0x106
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff8112b216>] ? vfs_rename+0x55f/0x668
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff8120dac3>] nfserrno+0x5a/0x5f
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff81210771>] nfsd_rename+0x2d7/0x34a
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff812157a1>] nfsd3_proc_rename+0xb8/0xc9
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff8120c78c>] nfsd_dispatch+0x8d/0x145
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff81659344>] svc_process+0x3f6/0x64b
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff8120c333>] nfsd+0x102/0x154
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff8120c231>] ? nfsd_destroy+0x69/0x69
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff81063893>] kthread+0xce/0xd6
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff810637c5>] ? kthread_park+0x52/0x52
Apr 20 12:32:50 SPE-UNRAID01 kernel: [<ffffffff8167e205>] ret_from_fork+0x25/0x30
Apr 20 12:32:50 SPE-UNRAID01 kernel: ---[ end trace c2a77c7a6b974e91 ]---

 

**NOTE** I only use my UnRAID server for serving up NFS shares, nothing else.

spe-unraid01-diagnostics-20170420-1235.zip

Edited April 20, 20179 yr by IamSpartacus

You should post the full diagnostics.  You get this either from the GUI via Tools->Diagnostics or by using the 'diagnostics' command from the command line.  You will find that normally anyone giving advice wants to see what lead up to the log messages you posted, or to look at other files included in the diagnostics.

Added.