NFS share is no longer accessible after deleting several files in this share

[Peter Pünjer]

Hello,
When I delete several files from an NFS share, I get the error message that I do not have the rights to delete the files. After that, all NFS shares are no longer accessible. It seems that the NFS service has completely failed. I now have to restart the Unraid server, after which NFS will be available again.

I have had this error in earlier versions, but very rarely. With version 6.11 the error always occurs, e.g. when I delete single files sometimes, when I delete 5 files at once currently always.

I use Fedora 36 Workstation as my operating system. I mount the drives via automount, no fstab! For testing, I have also configured it with NFS V3 in automount.

I only have the problem when using my client, Docker containers that use the same share do not cause the problem.

 

Log & diagnostics as attachmant....
 

Any idea?

 

Regards

Peter

 

Oct  3 14:27:42 Tower kernel: CPU: 2 PID: 4107 Comm: nfsd Tainted: G          I       5.19.9-Unraid #1
Oct  3 14:27:42 Tower kernel: Hardware name: HPE ML10Gen9/ML10Gen9, BIOS 1.004 09/13/2016
Oct  3 14:27:42 Tower kernel: RIP: 0010:nfserrno+0x45/0x51 [nfsd]
Oct  3 14:27:42 Tower kernel: Code: c3 cc cc cc cc 48 ff c0 48 83 f8 26 75 e0 80 3d cc 47 05 00 00 75 15 48 c7 c7 0f 44 8d a0 c6 05 bc 47 05 00 01 e8 06 89 f2 e0 <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 48 83 ec 18 31 c9 ba ff 07 00
Oct  3 14:27:42 Tower kernel: RSP: 0018:ffffc9000061fdc8 EFLAGS: 00010282
Oct  3 14:27:42 Tower kernel: RAX: 0000000000000000 RBX: ffff8881024a8030 RCX: 0000000000000027
Oct  3 14:27:42 Tower kernel: RDX: 0000000000000001 RSI: ffffffff81ec827f RDI: 00000000ffffffff
Oct  3 14:27:42 Tower kernel: RBP: ffff8881025ad0a4 R08: 0000000000000000 R09: ffffffff82044990
Oct  3 14:27:42 Tower kernel: R10: 00007fffffffffff R11: ffffffff82653436 R12: ffff8881024a8030
Oct  3 14:27:42 Tower kernel: R13: ffff888105eb4000 R14: 000000000000000b R15: ffff888105eb6bf8
Oct  3 14:27:42 Tower kernel: FS:  0000000000000000(0000) GS:ffff88826ad00000(0000) knlGS:0000000000000000
Oct  3 14:27:42 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct  3 14:27:42 Tower kernel: CR2: 0000149387c4950c CR3: 000000000200a005 CR4: 00000000003706e0
Oct  3 14:27:42 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct  3 14:27:42 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct  3 14:27:42 Tower kernel: Call Trace:
Oct  3 14:27:42 Tower kernel: <TASK>
Oct  3 14:27:42 Tower kernel: nfsd_lookup+0x5e/0xdb [nfsd]
Oct  3 14:27:42 Tower kernel: nfsd4_proc_compound+0x417/0x557 [nfsd]
Oct  3 14:27:42 Tower kernel: nfsd_dispatch+0x191/0x24d [nfsd]
Oct  3 14:27:42 Tower kernel: svc_process+0x3ee/0x5d6 [sunrpc]
Oct  3 14:27:42 Tower kernel: ? nfsd_svc+0x2b6/0x2b6 [nfsd]
Oct  3 14:27:42 Tower kernel: ? nfsd_shutdown_threads+0x5b/0x5b [nfsd]
Oct  3 14:27:42 Tower kernel: nfsd+0xd5/0x155 [nfsd]
Oct  3 14:27:42 Tower kernel: kthread+0xe4/0xef
Oct  3 14:27:42 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b
Oct  3 14:27:42 Tower kernel: ret_from_fork+0x1f/0x30
Oct  3 14:27:42 Tower kernel: </TASK>
Oct  3 14:27:42 Tower kernel: ---[ end trace 0000000000000000 ]---
 

tower-diagnostics-20221003-1429.zip

[JorgeB]

shfs crashed, rebooting should bring the shares back.

[Peter Pünjer]

Hello,
hmm, yes, that is exactly my problem, only a restart fixes the error....
In the meantime, I have also had the file system checked and fixed.
The error remains the same.

I need a better idea...

Peter

[JorgeB]

Sorry, I didn't read the complete post, no idea about why it's crashing, I've never used NFS, someone else might be able to help.

[dlandon]

I'm not sure this is an issue, but you only have 8GB of memory.

 

What I would try is to reboot in safe mode and see if you can reproduce the problem.  If not, then install CA manually, and start adding back plugins and see if one of them is causing the error.

 

If the issue still happens in safe mode, post your diagnostics file.