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.

abl030

Members
  • Joined

  • Last visited

  1. Edit, it happened again today and I got the syslog this time, the TL:DR is its this: https://github.com/libfuse/libfuse/issues/589 So yeah. It's known and old and still open. May 13 12:00:30 Tower shfs: shfs: ../lib/fuse.c:1402: unlink_node: Assertion `node->nlookup > 1' failed. This fires at line 1402 of fuse.c (libfuse 3.16.2 still — same version as Feb), which is the unlink_node cleanup path. The assertion guards against a refcount underflow — shfs has tried to decrement an inode's lookup count below 1 when there are no more outstanding lookups. Once tripped, libfuse aborts the FUSE session and the /mnt/user mount is permanently severed. Identical kernel symptoms as before — nfsd returns ENOTCONN to clients: May 13 12:00:30 Tower kernel: nfsd: non-standard errno: -107 May 13 12:00:30 Tower kernel: WARNING: CPU: 0 PID: 15275 at fs/nfsd/vfs.c:111 nfserrno+0x45/0x60 [nfsd] May 13 12:00:30 Tower kernel: RIP: 0010:nfserrno+0x45/0x60 [nfsd] May 13 12:00:30 Tower kernel: nfsd_splice_read+0xe2/0x110 [nfsd] May 13 12:00:30 Tower kernel: nfsd4_encode_splice_read+0x55/0xf0 [nfsd] May 13 12:00:30 Tower kernel: nfsd4_encode_read_plus+0x10e/0x190 [nfsd] May 13 12:00:30 Tower kernel: nfsd4_encode_operation+0x9e/0x230 [nfsd] May 13 12:00:30 Tower kernel: nfsd4_proc_compound+0x24a/0x5f0 [nfsd] May 13 12:00:30 Tower kernel: nfsd_dispatch+0x110/0x200 [nfsd] May 13 12:00:30 Tower kernel: nfsd+0xbb/0xe0 [nfsd]
  2. Hey mate, Did you ever get this sorted? I too am encountering this error. I tried disabling noatime but that didn't help. I am wondering I am running with NFS set to private. Are you as well? My NFS options: "x-systemd.automount" "noauto" "x-systemd.idle-timeout=300" "noatime" "nfsvers=4.2"

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.