October 27, 20241 yr Hi everyone, Getting this error randomly after running the server 24-48 hours then only a reboot can fix this, as it kills all my dockers. This has now been happening for the last two weeks. shfs: shfs: ../lib/fuse.c:1450: unlink_node: Assertion `node->nlookup > 1' failed. I did a some research but nothing I tried seems to fix this - Changed RAM - disable NFS Sharing - re-installed all the dockers - re-installed all the plugins - disabled support for Hard Links - disabled disk shares I am only running this on a mini PC for the dockers (for 7 years no issues before this), storage is on the network via Unassigned Devices (re-installed that and added all the shares again) Could it be the bootable memory stick or the SSD? Any suggestions would be appreciated.
October 27, 20241 yr Community Expert This is usually caused my containers manipulating the users shares with stale files, try using disk shares (or exclusive shares) whenever possible.
October 27, 20241 yr Author 7 minutes ago, JorgeB said: This is usually caused my containers manipulating the users shares with stale files, try using disk shares (or exclusive shares) whenever possible. Many thanks Jorge, I have been mounting shares on remotes for years now, with pretty much the same dockers, why would it change now? Apologies but what do you mean by exclusive shares?
October 27, 20241 yr Community Expert https://docs.unraid.net/unraid-os/release-notes/6.12.0/#exclusive-shares Also see below for some more info on that error: https://forums.unraid.net/bug-reports/stable-releases/683-shfs-error-results-in-lost-mntuser-r939/
October 29, 20241 yr Author Moved it all to a new box I had spare, and still happening! Running out of ideas.
October 30, 20241 yr Author 2 hours ago, JorgeB said: That's not a hardware issue. Reading the links you send me, doesn't seem to be a clear indication on how to reolve this error.
October 30, 20241 yr Community Expert There are some workarounds discussed there, also mentioned one in the first reply, but very unlikely that changing the hardware will help.
November 2, 20241 yr Author In the end rebuilt my dockers and haven't had the error since Tuesday! so fingers crossed.
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.