Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

SHFS crash "shfs: ../lib/fuse.c:836: unref_node: Assertion `node->refctr > 0' failed"

Featured Replies

Running Version: 6.10.3  i had SHFS crash on me for the frist time, the system is very stable, runtime was over half a year and previously before that the same, never had this happen before and would like to try to investigate why it suddenly happened.

 

Log isn't very helpful, no issues until suddenly:

Sep 27 10:33:40 NAS shfs: shfs: ../lib/fuse.c:836: unref_node: Assertion `node->refctr > 0' failed.
Sep 27 10:33:41 NAS emhttpd: error: get_filesystem_status, 6258: Transport endpoint is not connected (107): scandir Transport endpoint is not connected

 

All i know is that rsync was running at the time it happened, my guess this is the culprit? Is it that it ran out of memory or something else, like i said i am not getting much help from the logs.

 

For future reference, is there anyway to start SHFS if this occurs or do i have to unmount the array and then remount it again in order to get it back up running? I had all my docker containers mapped directly instead of via shfs so the only thing that happened when shfs crashed was that i couldnt access any data via the smb shares.

  • Author

Darn, scary read, but i have NFS disable as well as hardlink support, but i found someone who was doing stuff over SMB via a WM that was hosted on the same unraid machine, this is actually something i was also doing when this error occured, at first i though it was due to rsync running but looking closer the rsync script finished sucessfully just seconds before this error occured so its more likely i managed to trigger the error doing stuff via SMB from the WM. Makes me wonder if you can craft a bad smb packet and just crash shfs on demand?

 

Ill monitor the situation and hope for the best, thanks for the information @JorgeB

Edited by je82

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.