March 7, 20233 yr This has happened to me 4 times in the past year, and 2 times it happened last night around 3AM so I wasn't exactly on top of my game, but I did remember to get diagnostics both times. I was watching plex struggle with a music folder of bad .wav files, and determined the rip was bad so I went to delete the folder via NFS and Linux Mint 21 reported "Can not delete folder, not empty." I went to look at the folder and all the contents were deleted, it was empty so I deleted the folder that's when it was reported "input/output error." Then Unraid loses all of it's shares and docker throws a fit. Under the "shares" tab, there are no shares. I tried stopping the array and restarting it, but still no shares. I was required to reboot the server to get everything back, thankfully. After reboot, I started a parity check and decided to try to delete a totally different folder (one that wasn't possibly in use by plex). Same result happened, all shares disappeared and I had to reboot again. Same error, "folder not empty, can't delete." Try to delete the (actually empty) folder and "input/output error" and all shares go down. I had completed a parity check just a few days prior, so I'm pretty certain there are no issues there. Also the parity check I've been running now for the past 8 hours since this happened is reporting no errors. Out of curiosity, is there a command I can run to get shares back instead of rebooting? 1st time: Mar 7 02:27:39 Delmar kernel: ------------[ cut here ]------------ Mar 7 02:27:39 Delmar kernel: nfsd: non-standard errno: -107 Mar 7 02:27:39 Delmar kernel: WARNING: CPU: 0 PID: 7623 at fs/nfsd/nfsproc.c:889 nfserrno+0x45/0x51 [nfsd] Mar 7 02:27:39 Delmar kernel: Modules linked in: ext4 mbcache jbd2 ccp rpcsec_gss_krb5 macvlan xt_nat veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net tun vhost vhost_iotlb tap xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls i915 iosf_mbi drm_buddy x86_pkg_temp_thermal intel_powerclamp coretemp i2c_algo_bit mpt3sas gigabyte_wmi raid_class wmi_bmof kvm_intel nvme i2c_i801 intel_wmi_thunderbolt kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore nvme_core i2c_smbus scsi_transport_sas ttm drm_display_helper r8169 realtek drm_kms_helper ahci libahci drm input_leds led_class intel_gtt agpgart i2c_core syscopyarea Mar 7 02:27:39 Delmar kernel: sysfillrect sysimgblt intel_pch_thermal fb_sys_fops fan thermal wmi tpm_crb tpm_tis video tpm_tis_core backlight tpm acpi_pad button unix Mar 7 02:27:39 Delmar kernel: CPU: 0 PID: 7623 Comm: nfsd Not tainted 5.19.17-Unraid #2 Mar 7 02:27:39 Delmar kernel: Hardware name: Gigabyte Technology Co., Ltd. Z390 UD/Z390 UD, BIOS F10 11/05/2021 Mar 7 02:27:39 Delmar kernel: RIP: 0010:nfserrno+0x45/0x51 [nfsd] Mar 7 02:27:39 Delmar kernel: Code: c3 cc cc cc cc 48 ff c0 48 83 f8 26 75 e0 80 3d bb 47 05 00 00 75 15 48 c7 c7 17 54 6a a0 c6 05 ab 47 05 00 01 e8 42 57 1a e1 <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 48 83 ec 18 31 c9 ba ff 07 00 Mar 7 02:27:39 Delmar kernel: RSP: 0018:ffffc90000767d78 EFLAGS: 00010286 Mar 7 02:27:39 Delmar kernel: RAX: 0000000000000000 RBX: ffff8881589d0030 RCX: 0000000000000027 Mar 7 02:27:39 Delmar kernel: RDX: 0000000000000001 RSI: ffffffff820d7be1 RDI: 00000000ffffffff Mar 7 02:27:39 Delmar kernel: RBP: ffff888158308000 R08: 0000000000000000 R09: ffffffff82244bd0 Mar 7 02:27:39 Delmar kernel: R10: 00007fffffffffff R11: ffffffff82882d66 R12: ffff888179c090c0 Mar 7 02:27:39 Delmar kernel: R13: ffff8887bfbd2600 R14: 000000000000000b R15: 0000000000000000 Mar 7 02:27:39 Delmar kernel: FS: 0000000000000000(0000) GS:ffff88907e200000(0000) knlGS:0000000000000000 Mar 7 02:27:39 Delmar kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 7 02:27:39 Delmar kernel: CR2: 0000000000000010 CR3: 000000018ab02004 CR4: 00000000003726f0 Mar 7 02:27:39 Delmar kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 7 02:27:39 Delmar kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 7 02:27:39 Delmar kernel: Call Trace: Mar 7 02:27:39 Delmar kernel: <TASK> Mar 7 02:27:39 Delmar kernel: fh_verify+0x4e7/0x58d [nfsd] Mar 7 02:27:39 Delmar kernel: nfsd_lookup+0x3f/0xdb [nfsd] Mar 7 02:27:39 Delmar kernel: nfsd4_proc_compound+0x434/0x56c [nfsd] Mar 7 02:27:39 Delmar kernel: nfsd_dispatch+0x1a6/0x262 [nfsd] Mar 7 02:27:39 Delmar kernel: svc_process+0x3ee/0x5d6 [sunrpc] Mar 7 02:27:39 Delmar kernel: ? nfsd_svc+0x2b6/0x2b6 [nfsd] Mar 7 02:27:39 Delmar kernel: ? nfsd_shutdown_threads+0x5b/0x5b [nfsd] Mar 7 02:27:39 Delmar kernel: nfsd+0xd5/0x155 [nfsd] Mar 7 02:27:39 Delmar kernel: kthread+0xe4/0xef Mar 7 02:27:39 Delmar kernel: ? kthread_complete_and_exit+0x1b/0x1b Mar 7 02:27:39 Delmar kernel: ret_from_fork+0x1f/0x30 Mar 7 02:27:39 Delmar kernel: </TASK> Mar 7 02:27:39 Delmar kernel: ---[ end trace 0000000000000000 ]--- Second time: Mar 7 03:07:06 Delmar kernel: ------------[ cut here ]------------ Mar 7 03:07:06 Delmar kernel: nfsd: non-standard errno: -103 Mar 7 03:07:06 Delmar kernel: WARNING: CPU: 0 PID: 7829 at fs/nfsd/nfsproc.c:889 nfserrno+0x45/0x51 [nfsd] Mar 7 03:07:06 Delmar kernel: Modules linked in: macvlan xt_nat veth nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net tun vhost vhost_iotlb tap xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls i915 gigabyte_wmi x86_pkg_temp_thermal intel_powerclamp wmi_bmof intel_wmi_thunderbolt coretemp mpt3sas iosf_mbi drm_buddy kvm_intel i2c_algo_bit ttm drm_display_helper i2c_i801 nvme raid_class kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore nvme_core i2c_smbus scsi_transport_sas drm_kms_helper r8169 realtek ahci libahci drm intel_gtt agpgart input_leds led_class i2c_core intel_pch_thermal syscopyarea sysfillrect sysimgblt Mar 7 03:07:06 Delmar kernel: fb_sys_fops fan thermal wmi tpm_crb video tpm_tis backlight tpm_tis_core tpm acpi_pad button unix Mar 7 03:07:06 Delmar kernel: CPU: 0 PID: 7829 Comm: nfsd Not tainted 5.19.17-Unraid #2 Mar 7 03:07:06 Delmar kernel: Hardware name: Gigabyte Technology Co., Ltd. Z390 UD/Z390 UD, BIOS F10 11/05/2021 Mar 7 03:07:06 Delmar kernel: RIP: 0010:nfserrno+0x45/0x51 [nfsd] Mar 7 03:07:06 Delmar kernel: Code: c3 cc cc cc cc 48 ff c0 48 83 f8 26 75 e0 80 3d bb 47 05 00 00 75 15 48 c7 c7 17 d4 91 a0 c6 05 ab 47 05 00 01 e8 42 d7 f2 e0 <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 48 83 ec 18 31 c9 ba ff 07 00 Mar 7 03:07:06 Delmar kernel: RSP: 0018:ffffc9000073fb58 EFLAGS: 00010282 Mar 7 03:07:06 Delmar kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027 Mar 7 03:07:06 Delmar kernel: RDX: 0000000000000001 RSI: ffffffff820d7be1 RDI: 00000000ffffffff Mar 7 03:07:06 Delmar kernel: RBP: ffffc9000073fdb0 R08: 0000000000000000 R09: ffffffff82244bd0 Mar 7 03:07:06 Delmar kernel: R10: 00007fffffffffff R11: ffffffff8287946e R12: 000000000000000c Mar 7 03:07:06 Delmar kernel: R13: 000000000010011a R14: ffff8881049111a0 R15: ffffffff82909480 Mar 7 03:07:06 Delmar kernel: FS: 0000000000000000(0000) GS:ffff88907e200000(0000) knlGS:0000000000000000 Mar 7 03:07:06 Delmar kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 7 03:07:06 Delmar kernel: CR2: 000014b224d7d000 CR3: 00000004df3e8004 CR4: 00000000003726f0 Mar 7 03:07:06 Delmar kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 7 03:07:06 Delmar kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 7 03:07:06 Delmar kernel: Call Trace: Mar 7 03:07:06 Delmar kernel: <TASK> Mar 7 03:07:06 Delmar kernel: nfsd4_encode_fattr+0x1372/0x13d9 [nfsd] Mar 7 03:07:06 Delmar kernel: ? getboottime64+0x20/0x2e Mar 7 03:07:06 Delmar kernel: ? kvmalloc_node+0x44/0xbc Mar 7 03:07:06 Delmar kernel: ? __kmalloc_node+0x1b4/0x1df Mar 7 03:07:06 Delmar kernel: ? kvmalloc_node+0x44/0xbc Mar 7 03:07:06 Delmar kernel: ? override_creds+0x21/0x34 Mar 7 03:07:06 Delmar kernel: ? nfsd_setuser+0x185/0x1a5 [nfsd] Mar 7 03:07:06 Delmar kernel: ? nfsd_setuser_and_check_port+0x76/0xb4 [nfsd] ### [PREVIOUS LINE REPEATED 1 TIMES] ### Mar 7 03:07:06 Delmar kernel: nfsd4_encode_getattr+0x28/0x2e [nfsd] Mar 7 03:07:06 Delmar kernel: nfsd4_encode_operation+0xad/0x201 [nfsd] Mar 7 03:07:06 Delmar kernel: nfsd4_proc_compound+0x2a7/0x56c [nfsd] Mar 7 03:07:06 Delmar kernel: nfsd_dispatch+0x1a6/0x262 [nfsd] Mar 7 03:07:06 Delmar kernel: svc_process+0x3ee/0x5d6 [sunrpc] Mar 7 03:07:06 Delmar kernel: ? nfsd_svc+0x2b6/0x2b6 [nfsd] Mar 7 03:07:06 Delmar kernel: ? nfsd_shutdown_threads+0x5b/0x5b [nfsd] Mar 7 03:07:06 Delmar kernel: nfsd+0xd5/0x155 [nfsd] Mar 7 03:07:06 Delmar kernel: kthread+0xe4/0xef Mar 7 03:07:06 Delmar kernel: ? kthread_complete_and_exit+0x1b/0x1b Mar 7 03:07:06 Delmar kernel: ret_from_fork+0x1f/0x30 Mar 7 03:07:06 Delmar kernel: </TASK> Mar 7 03:07:06 Delmar kernel: ---[ end trace 0000000000000000 ]--- delmar-diag-second-crash.zip delmar-diag.zip
March 25, 20233 yr Did you figure this out? I think I'm seeing the same thing as of this morning. I don't think this has ever happened to me until today (twice already).
March 25, 20233 yr Author 3 hours ago, Howboys said: Did you figure this out? I think I'm seeing the same thing as of this morning. I don't think this has ever happened to me until today (twice already). My "solution" was to quit NFS and use SMB solely. Haven't had a problem since. It's pretty scary when it happens because literally all your data just POOF vanishes and I don't like it one bit. I haven't figured out the cause or a real solution.
March 25, 20233 yr 24 minutes ago, grants169 said: My "solution" was to quit NFS and use SMB solely. Haven't had a problem since. It's pretty scary when it happens because literally all your data just POOF vanishes and I don't like it one bit. I haven't figured out the cause or a real solution. Ugh.. even samba has issues for me (performance and locking related). That's why I switched to nfs.
March 26, 20233 yr Author 3 hours ago, Howboys said: Ugh.. even samba has issues for me (performance and locking related). That's why I switched to nfs. Assuming you're on linux, this is what I use in my /etc/fstab for samba, maybe it'll help you out... //[unraid server IP]/media /mnt/media cifs cred=/etc/cred.cifs,uid=[your local username],gid=[your local group],perm,iocharset=utf8 0 0 make a file /etc/cred.cifs, chown it root:root and chmod it 600 and put in it: username=[unraid username] password=[unraid password] and of course create the directory /mnt/media or where ever you want to mount the share. mount it with sudo mount -a -t cifs I know there are a few tweaks you can do to that, but I keep it simple and it works flawlessly for me.....
December 3, 20232 yr Same issue here on 6.12.4. Run into this 3 times in the past 5 months. Deleting files via NFS seems to be the trigger for me.
March 3, 20242 yr Just happened to me as well. Mar 3 12:21:32 Tower kernel: docker0: port 9(veth6a244cc) entered blocking state Mar 3 12:21:32 Tower kernel: docker0: port 9(veth6a244cc) entered forwarding state Mar 3 12:27:13 Tower kernel: shfs[9157]: segfault at 10 ip 000014bd8c39a5c2 sp 000014bd8bc8ec20 error 4 in libfuse3.so.3.12.0[14bd8c396000+19000] likely on CPU 12 (core 24, socket 0) Mar 3 12:27:13 Tower kernel: Code: f4 c8 ff ff 8b b3 08 01 00 00 85 f6 0f 85 46 01 00 00 4c 89 ee 48 89 df 45 31 ff e8 18 dc ff ff 4c 89 e7 45 31 e4 48 8b 40 20 <4c> 8b 68 10 e8 15 c2 ff ff 48 8d 4c 24 18 45 31 c0 31 d2 4c 89 ee Mar 3 12:27:13 Tower kernel: ------------[ cut here ]------------ Mar 3 12:27:13 Tower kernel: nfsd: non-standard errno: -107 Mar 3 12:27:13 Tower kernel: WARNING: CPU: 19 PID: 7623 at fs/nfsd/nfsproc.c:909 nfserrno+0x45/0x51 [nfsd] Mar 3 12:27:13 Tower kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle xt_nat vhost_net vhost vhost_iotlb tap veth xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs xt_MASQUERADE xt_tcpudp xt_mark iptable_nat ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 tun nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iosf_mbi drm_buddy i2c_algo_bit btusb ttm btrtl btbcm drm_display_helper btintel kvm drm_kms_helper bluetooth drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd intel_gtt input_leds cryptd rapl ecdh_generic Mar 3 12:27:13 Tower kernel: intel_cstate mei_hdcp mei_pxp wmi_bmof joydev led_class ecc agpgart intel_uncore nvme i2c_i801 ahci syscopyarea mei_me i2c_smbus sysfillrect sysimgblt igc video i2c_core nvme_core libahci vmd fb_sys_fops thermal fan mei tpm_crb tpm_tis tpm_tis_core wmi tpm backlight acpi_tad intel_pmc_core acpi_pad button unix Mar 3 12:27:13 Tower kernel: CPU: 19 PID: 7623 Comm: nfsd Tainted: P O 6.1.74-Unraid #1 Mar 3 12:27:13 Tower kernel: Hardware name: ASUS System Product Name/ROG STRIX B760-I GAMING WIFI, BIOS 1220 07/28/2023 Mar 3 12:27:13 Tower kernel: RIP: 0010:nfserrno+0x45/0x51 [nfsd] Mar 3 12:27:13 Tower kernel: Code: c3 cc cc cc cc 48 ff c0 48 83 f8 26 75 e0 80 3d a4 c9 05 00 00 75 15 48 c7 c7 b5 32 17 a1 c6 05 94 c9 05 00 01 e8 2f c9 f2 df <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 48 83 ec 18 31 c9 ba ff 07 00 Mar 3 12:27:13 Tower kernel: RSP: 0018:ffffc90001d5fd60 EFLAGS: 00010282 Mar 3 12:27:13 Tower kernel: RAX: 0000000000000000 RBX: ffff88814dd18028 RCX: 0000000000000027 Mar 3 12:27:13 Tower kernel: RDX: 0000000000000002 RSI: ffffffff820d8766 RDI: 00000000ffffffff Mar 3 12:27:13 Tower kernel: RBP: ffff88814cdf6e40 R08: 0000000000000000 R09: ffffffff829513f0 Mar 3 12:27:13 Tower kernel: R10: 00003fffffffffff R11: ffff88907f7b9e96 R12: ffff88814dc58000 Mar 3 12:27:13 Tower kernel: R13: ffff888f83c22400 R14: 000000000000000b R15: 0000000000000000 Mar 3 12:27:13 Tower kernel: FS: 0000000000000000(0000) GS:ffff88903f6c0000(0000) knlGS:0000000000000000 Mar 3 12:27:13 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 3 12:27:13 Tower kernel: CR2: 000000c0002c6061 CR3: 000000000420a000 CR4: 0000000000750ee0 Mar 3 12:27:13 Tower kernel: PKRU: 55555554 Mar 3 12:27:13 Tower kernel: Call Trace: Mar 3 12:27:13 Tower kernel: <TASK> Mar 3 12:27:13 Tower kernel: ? __warn+0xab/0x122 Mar 3 12:27:13 Tower kernel: ? report_bug+0x109/0x17e Mar 3 12:27:13 Tower kernel: ? nfserrno+0x45/0x51 [nfsd] Mar 3 12:27:13 Tower kernel: ? handle_bug+0x41/0x6f Mar 3 12:27:13 Tower kernel: ? exc_invalid_op+0x13/0x60 Mar 3 12:27:13 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 Mar 3 12:27:13 Tower kernel: ? nfserrno+0x45/0x51 [nfsd] Mar 3 12:27:13 Tower kernel: fh_verify+0x4f9/0x5c6 [nfsd] Mar 3 12:27:13 Tower kernel: nfsd_lookup+0x3f/0xdb [nfsd] Mar 3 12:27:13 Tower kernel: nfsd4_proc_compound+0x43c/0x575 [nfsd] Mar 3 12:27:13 Tower kernel: nfsd_dispatch+0x1db/0x296 [nfsd] Mar 3 12:27:13 Tower kernel: svc_process_common+0x32f/0x4df [sunrpc] Mar 3 12:27:13 Tower kernel: ? ktime_get+0x35/0x49 Mar 3 12:27:13 Tower kernel: ? nfsd_svc+0x2b6/0x2b6 [nfsd] Mar 3 12:27:13 Tower kernel: ? nfsd_shutdown_threads+0x5b/0x5b [nfsd] Mar 3 12:27:13 Tower kernel: svc_process+0xc7/0xe4 [sunrpc] Mar 3 12:27:13 Tower kernel: nfsd+0xd5/0x155 [nfsd] Mar 3 12:27:13 Tower kernel: kthread+0xe4/0xef Mar 3 12:27:13 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b Mar 3 12:27:13 Tower kernel: ret_from_fork+0x1f/0x30 Mar 3 12:27:13 Tower kernel: </TASK> Mar 3 12:27:13 Tower kernel: ---[ end trace 0000000000000000 ]--- Mar 3 12:27:34 Tower kernel: veth5ba1152: renamed from eth0 Mar 3 12:27:34 Tower kernel: docker0: port 9(veth6a244cc) entered disabled state Mar 3 12:27:34 Tower kernel: docker0: port 9(veth6a244cc) entered disabled state Mar 3 12:27:34 Tower kernel: device veth6a244cc left promiscuous mode Mar 3 12:27:34 Tower kernel: docker0: port 9(veth6a244cc) entered disabled state
March 10, 20242 yr Still happening for me in Unraid 6.12.8 [354923.452915] shfs[21467]: segfault at 10 ip 0000147b193ea5c2 sp 0000147b182d3c20 error 4 in libfuse3.so.3.12.0[147b193e6000+19000] likely on CPU 14 (core 6, socket 0) [354923.452928] Code: f4 c8 ff ff 8b b3 08 01 00 00 85 f6 0f 85 46 01 00 00 4c 89 ee 48 89 df 45 31 ff e8 18 dc ff ff 4c 89 e7 45 31 e4 48 8b 40 20 <4c> 8b 68 10 e8 15 c2 ff ff 48 8d 4c 24 18 45 31 c0 31 d2 4c 89 ee [354923.464890] ------------[ cut here ]------------ [354923.464893] nfsd: non-standard errno: -103 [354923.464917] WARNING: CPU: 2 PID: 9872 at fs/nfsd/nfsproc.c:909 nfserrno+0x45/0x51 [nfsd] [354923.464942] Modules linked in: nvidia_uvm(PO) wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha rpcsec_gss_krb5 xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag apex(O) gasket(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc bonding tls intel_rapl_msr nvidia_drm(PO) intel_rapl_common nvidia_modeset(PO) iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm nvidia(PO) crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel [354923.464993] sha512_ssse3 sha256_ssse3 mei_hdcp mei_pxp sha1_ssse3 aesni_intel crypto_simd cryptd drm_kms_helper mei_me i2c_i801 rapl nvme intel_cstate drm i2c_smbus wmi_bmof intel_uncore r8169 nvme_core mei ahci i2c_core libahci realtek syscopyarea sysfillrect sysimgblt thermal fb_sys_fops fan tpm_crb video tpm_tis tpm_tis_core wmi tpm backlight intel_pmc_core acpi_pad acpi_tad button unix [354923.465014] CPU: 2 PID: 9872 Comm: nfsd Tainted: P O 6.1.74-Unraid #1 [354923.465016] Hardware name: INTEL HM570/HM570, BIOS THM570106 06/14/2022 [354923.465017] RIP: 0010:nfserrno+0x45/0x51 [nfsd] [354923.465029] Code: c3 cc cc cc cc 48 ff c0 48 83 f8 26 75 e0 80 3d a4 c9 05 00 00 75 15 48 c7 c7 b5 02 22 a4 c6 05 94 c9 05 00 01 e8 2f f9 e7 dc <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 48 83 ec 18 31 c9 ba ff 07 00 [354923.465030] RSP: 0018:ffffc90001eebd40 EFLAGS: 00010286 [354923.465032] RAX: 0000000000000000 RBX: ffff8881649ce028 RCX: 0000000000000027 [354923.465033] RDX: 0000000000000002 RSI: ffffffff820d8766 RDI: 00000000ffffffff [354923.465034] RBP: ffffc90001eebd88 R08: 0000000000000000 R09: ffffffff82245f30 [354923.465035] R10: 00007fffffffffff R11: ffffffff82966b3e R12: ffff8881649ce100 [354923.465035] R13: ffff8881611c1a00 R14: 0000000000000080 R15: ffff88811df79a00 [354923.465036] FS: 0000000000000000(0000) GS:ffff88906fa80000(0000) knlGS:0000000000000000 [354923.465037] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [354923.465038] CR2: 000014927424311c CR3: 00000002f9642003 CR4: 0000000000770ee0 [354923.465039] PKRU: 55555554 [354923.465039] Call Trace: Some have said it might be an interaction between libfuse and nfsd, others have suggested memory or SATA cable issues. This *only* happens for me when deleting files via NFS, and it seems to happen pretty reliably now. If anyone can suggest troubleshooting steps or wants me to provide diagnostics, please let me know. This is relaly holding me back and is bad enough to make me think about switching away from Unraid (though this would not be my first choice).
March 10, 20242 yr Community Expert 1 minute ago, tensiondriven said: provide diagnostic Yes Attach Diagnostics to your NEXT post in this thread.
March 10, 20242 yr Author 5 minutes ago, tensiondriven said: Still happening for me in Unraid 6.12.8 Looks like it's going to continue to happen until libfuse is fixed, but won't be fixed as the project does not currently have any active, regular contributors.. Limetech has an closed issue at github https://github.com/libfuse/libfuse/issues/589 my "fix" for it was to stop using NFS. That's the only time I had an issue with it outside of a once messed up appdata folder, minus one singular time I encountered it with SMB as others also have reported. Use SMB instead. If you absolutely need to use NFS then access the disk directly instead of via fuse. Enable disk shares and exclusive shares in settings-->global share settings.
March 20, 20242 yr On 3/9/2024 at 10:46 PM, trurl said: Yes Attach Diagnostics to your NEXT post in this thread. Diagnostics attached. Please advise. elephant-diagnostics-20240319-2246.zip
March 20, 20242 yr On 3/9/2024 at 10:58 PM, grants169 said: Looks like it's going to continue to happen until libfuse is fixed, but won't be fixed as the project does not currently have any active, regular contributors.. Limetech has an closed issue at github https://github.com/libfuse/libfuse/issues/589 my "fix" for it was to stop using NFS. That's the only time I had an issue with it outside of a once messed up appdata folder, minus one singular time I encountered it with SMB as others also have reported. Use SMB instead. If you absolutely need to use NFS then access the disk directly instead of via fuse. Enable disk shares and exclusive shares in settings-->global share settings. Thanks for the thorough reply. If a solution isn't found soon, my "fix" will be to stop using Unraid. I want to love unraid, and do love a lot of things about it, but "file sharing using the operating system native file sharing protocol does not work" is not a good look for a product whose primary purpose is sharing files. I just posted my diagnostics and also posted a comment on the Github issue. Thankfully a mod asked me to post my diagnostics so I think there's a fairly high chance that the issue will get some kind of attention. Hopefully something will come of it.
March 20, 20242 yr Author 40 minutes ago, tensiondriven said: Hopefully something will come of it. Consider this thread:
November 21, 20241 yr NFS shares are completely unusable. This is after I switched al my business computers to Linux Mint. AutoFS is used to mount these shares; tried all the arguments that are floating around. The problem is always after deleting a file and completely crashes ALL shares. Guess we're switching it all to Samba /sigh. text error warn system array login Nov 19 16:55:55 Fatsally root: plugin: skipping: /boot/config/plugins/unassigned.devices/iso_mount.cfg already exists Nov 19 16:55:55 Fatsally root: plugin: creating: /tmp/unassigned.devices/add-smb - from INLINE content Nov 19 16:55:55 Fatsally root: plugin: setting: /tmp/unassigned.devices/add-smb - mode to 0770 Nov 19 16:55:55 Fatsally root: plugin: running: anonymous Nov 19 16:55:55 Fatsally unassigned.devices: Updating share settings... Nov 19 16:55:55 Fatsally unassigned.devices: Removing SMB share 'HIBERNATION'. Nov 19 16:55:55 Fatsally unassigned.devices: Removing NFS share '/mnt/disks/HIBERNATION'. Nov 19 16:55:55 Fatsally unassigned.devices: Adding SMB share 'HIBERNATION'. Nov 19 16:55:55 Fatsally unassigned.devices: Adding NFS share '/mnt/disks/HIBERNATION'. Nov 19 16:55:55 Fatsally unassigned.devices: Share settings updated. Nov 19 16:55:55 Fatsally root: plugin: unassigned.devices.plg updated Nov 19 17:39:19 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e8a8671590a3 from "192.168.88.23:739" Nov 19 17:40:35 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e8a8671590a3 from "192.168.88.23:739" Nov 19 17:51:53 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e8bc671590a3 from "192.168.88.23:893" Nov 19 17:53:08 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e8bc671590a3 from "192.168.88.23:893" Nov 19 18:07:26 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e8d4671590a3 from "192.168.88.23:706" Nov 19 18:08:41 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e8d4671590a3 from "192.168.88.23:706" Nov 19 18:28:01 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e8f4671590a3 from "192.168.88.23:681" Nov 19 18:29:16 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e8f4671590a3 from "192.168.88.23:681" Nov 19 18:44:20 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e90e671590a3 from "192.168.88.23:897" Nov 19 18:45:35 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e90e671590a3 from "192.168.88.23:897" Nov 19 18:51:52 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e91a671590a3 from "192.168.88.23:677" Nov 19 18:53:07 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e91a671590a3 from "192.168.88.23:677" Nov 19 19:04:55 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e92e671590a3 from "192.168.88.23:937" Nov 19 19:06:10 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e92e671590a3 from "192.168.88.23:937" Nov 19 21:13:11 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660e9f4671590a3 from "192.168.88.23:697" Nov 19 21:14:26 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660e9f4671590a3 from "192.168.88.23:697" Nov 19 21:28:15 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660ea0c671590a3 from "192.168.88.23:727" Nov 19 21:29:30 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660ea0c671590a3 from "192.168.88.23:727" Nov 19 21:42:03 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660ea22671590a3 from "192.168.88.23:802" Nov 19 21:43:18 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660ea22671590a3 from "192.168.88.23:802" Nov 19 21:47:05 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660ea2a671590a3 from "192.168.88.23:778" Nov 19 21:48:20 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660ea2a671590a3 from "192.168.88.23:778" Nov 19 22:36:17 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660ea78671590a3 from "192.168.88.23:762" Nov 19 22:37:32 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660ea78671590a3 from "192.168.88.23:762" Nov 19 23:03:38 Fatsally rpc.mountd[25994]: v4.2 client attached: 0xa660eaa0671590a3 from "192.168.88.23:863" Nov 19 23:04:53 Fatsally rpc.mountd[25994]: v4.2 client detached: 0xa660eaa0671590a3 from "192.168.88.23:863" Nov 20 02:00:04 Fatsally root: /etc/libvirt: 30.3 MiB (31797248 bytes) trimmed on /dev/loop3 Nov 20 02:00:04 Fatsally root: /var/lib/docker: 1000.3 MiB (1048875008 bytes) trimmed on /dev/loop2 Nov 20 02:00:04 Fatsally root: /mnt/cache: 220.6 GiB (236889636864 bytes) trimmed on /dev/nvme0n1p1 Nov 20 09:39:30 Fatsally kernel: shfs[2209]: segfault at 10 ip 000014dacd22a5c2 sp 000014dab784fc20 error 4 in libfuse3.so.3.12.0[14dacd226000+19000] likely on CPU 9 (core 14, socket 0) Nov 20 09:39:30 Fatsally kernel: Code: f4 c8 ff ff 8b b3 08 01 00 00 85 f6 0f 85 46 01 00 00 4c 89 ee 48 89 df 45 31 ff e8 18 dc ff ff 4c 89 e7 45 31 e4 48 8b 40 20 <4c> 8b 68 10 e8 15 c2 ff ff 48 8d 4c 24 18 45 31 c0 31 d2 4c 89 ee Nov 20 09:39:30 Fatsally kernel: ------------[ cut here ]------------ Nov 20 09:39:30 Fatsally kernel: nfsd: non-standard errno: -107 Nov 20 09:39:30 Fatsally kernel: WARNING: CPU: 10 PID: 3960 at fs/nfsd/vfs.c:111 nfserrno+0x45/0x51 [nfsd] Nov 20 09:39:30 Fatsally kernel: Modules linked in: nf_tables rpcsec_gss_krb5 vhost_net tun vhost tap kvm_intel kvm md_mod xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_iotlb veth ipvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter nvidia_uvm(PO) xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) i915 drm_buddy i2c_algo_bit ttm drm_display_helper intel_gtt agpgart tcp_diag inet_diag wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls e1000e atlantic nvidia_drm(PO) nvidia_modeset(PO) intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp Nov 20 09:39:30 Fatsally kernel: nvidia(PO) crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd video rapl drm_kms_helper btusb btrtl intel_cstate drm btbcm btintel nvme backlight i2c_i801 bluetooth mxm_wmi mpt3sas intel_uncore syscopyarea thunderbolt nvme_core intel_wmi_thunderbolt i2c_smbus sysfillrect mei_me sysimgblt fb_sys_fops i2c_core raid_class scsi_transport_sas ahci mei libahci input_leds ecdh_generic led_class joydev ecc tpm_crb tpm_tis tpm_tis_core tpm wmi acpi_tad button unix [last unloaded: md_mod] Nov 20 09:39:30 Fatsally kernel: CPU: 10 PID: 3960 Comm: nfsd Tainted: P O 6.1.106-Unraid #1 Nov 20 09:39:30 Fatsally kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X299 Creator, BIOS L1.52C 08/05/2022 Nov 20 09:39:30 Fatsally kernel: RIP: 0010:nfserrno+0x45/0x51 [nfsd] Nov 20 09:39:30 Fatsally kernel: Code: c3 cc cc cc cc 48 ff c0 48 83 f8 26 75 e0 80 3d 41 b6 05 00 00 75 15 48 c7 c7 e6 6a 24 a5 c6 05 31 b6 05 00 01 e8 44 a2 e5 db <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 0f 1f 44 00 00 41 57 41 56 41 Nov 20 09:39:30 Fatsally kernel: RSP: 0018:ffffc90000eafd50 EFLAGS: 00010286 Nov 20 09:39:30 Fatsally kernel: RAX: 0000000000000000 RBX: ffff88817fc4c028 RCX: 0000000000000027 Nov 20 09:39:30 Fatsally kernel: RDX: 0000000000000002 RSI: ffffffff820d99e1 RDI: 00000000ffffffff Nov 20 09:39:30 Fatsally kernel: RBP: ffff88817fc10000 R08: 0000000000000000 R09: ffffffff829573f0 Nov 20 09:39:30 Fatsally kernel: R10: 00003fffffffffff R11: ffff88909ffcf08e R12: ffff888104f67b00 Nov 20 09:39:30 Fatsally kernel: R13: ffff888961ec9100 R14: 000000000000000b R15: 0000000000000000 Nov 20 09:39:30 Fatsally kernel: FS: 0000000000000000(0000) GS:ffff88905fe80000(0000) knlGS:0000000000000000 Nov 20 09:39:30 Fatsally kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 20 09:39:30 Fatsally kernel: CR2: 000014f0fca601e0 CR3: 000000000220a004 CR4: 00000000003726e0 Nov 20 09:39:30 Fatsally kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Nov 20 09:39:30 Fatsally kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Nov 20 09:39:30 Fatsally kernel: Call Trace: Nov 20 09:39:30 Fatsally kernel: <TASK> Nov 20 09:39:30 Fatsally kernel: ? __warn+0xab/0x122 Nov 20 09:39:30 Fatsally kernel: ? report_bug+0x109/0x17e Nov 20 09:39:30 Fatsally kernel: ? nfserrno+0x45/0x51 [nfsd] Nov 20 09:39:30 Fatsally kernel: ? handle_bug+0x41/0x6f Nov 20 09:39:30 Fatsally kernel: ? exc_invalid_op+0x13/0x60 Nov 20 09:39:30 Fatsally kernel: ? asm_exc_invalid_op+0x16/0x20 Nov 20 09:39:30 Fatsally kernel: ? nfserrno+0x45/0x51 [nfsd] Nov 20 09:39:30 Fatsally kernel: fh_verify+0x531/0x610 [nfsd] Nov 20 09:39:30 Fatsally kernel: nfsd_lookup+0x3f/0xdb [nfsd] Nov 20 09:39:30 Fatsally kernel: nfsd4_proc_compound+0x444/0x57f [nfsd] Nov 20 09:39:30 Fatsally kernel: nfsd_dispatch+0x1db/0x28f [nfsd] Nov 20 09:39:30 Fatsally kernel: svc_process_common+0x300/0x511 [sunrpc] Nov 20 09:39:30 Fatsally kernel: ? ktime_get+0x35/0x49 Nov 20 09:39:30 Fatsally kernel: ? nfsd_svc+0x2cf/0x2cf [nfsd] Nov 20 09:39:30 Fatsally kernel: ? nfsd_shutdown_threads+0x5b/0x5b [nfsd] Nov 20 09:39:30 Fatsally kernel: svc_process+0xcc/0xe9 [sunrpc] Nov 20 09:39:30 Fatsally kernel: nfsd+0x96/0x108 [nfsd] Nov 20 09:39:30 Fatsally kernel: kthread+0xe4/0xef Nov 20 09:39:30 Fatsally kernel: ? kthread_complete_and_exit+0x1b/0x1b Nov 20 09:39:30 Fatsally kernel: ret_from_fork+0x1f/0x30 Nov 20 09:39:30 Fatsally kernel: </TASK> Nov 20 09:39:30 Fatsally kernel: ---[ end trace 0000000000000000 ]--- Nov 20 09:39:30 Fatsally rsyslogd: file '/mnt/user/appdata/syslog-192.168.88.217.log'[2] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: Transport endpoint is not connected [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Nov 20 09:39:30 Fatsally rsyslogd: file '/mnt/user/appdata/syslog-192.168.88.217.log': open error: Transport endpoint is not connected [v8.2102.0 try https://www.rsyslog.com/e/2433 ] Nov 20 09:42:12 Fatsally smbd[25503]: [2024/11/20 09:42:12.625485, 0] ../../source3/smbd/smb2_service.c:772(make_connection_snum) Nov 20 09:42:12 Fatsally smbd[25503]: make_connection_snum: canonicalize_connect_path failed for service Downloads, path /mnt/user/Downloads Edited November 21, 20241 yr by Gabriel_B clarification
June 1, 20251 yr Jun 1 13:47:18 Tower kernel: shfs[10605]: segfault at 10 ip 000014d7e6c166d2 sp 000014d7e58e5c20 error 4 in libfuse3.so.3.16.2[d6d2,14d7e6c12000+1a000] likely on CPU 0 (core 0, socket 0) Jun 1 13:47:18 Tower kernel: Code: 14 c8 ff ff 8b b3 10 01 00 00 85 f6 0f 85 46 01 00 00 4c 89 ee 48 89 df 45 31 ff e8 b8 dc ff ff 4c 89 e7 45 31 e4 48 8b 40 20 <4c> 8b 68 10 e8 35 c1 ff ff 48 8d 4c 24 18 45 31 c0 31 d2 4c 89 ee Jun 1 13:47:18 Tower kernel: ------------[ cut here ]------------ Jun 1 13:47:18 Tower kernel: nfsd: non-standard errno: -103 Jun 1 13:47:18 Tower kernel: WARNING: CPU: 5 PID: 14402 at fs/nfsd/vfs.c:111 nfserrno+0x45/0x60 [nfsd] Jun 1 13:47:18 Tower kernel: Modules linked in: xt_connmark xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ipvlan xt_CHECKSUM nf_conntrack_netlink xt_nat ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net vhost vhost_iotlb tap veth xt_conntrack xfrm_user xfrm_algo xt_addrtype xt_MASQUERADE xt_tcpudp xt_mark tun nf_tables nfnetlink ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfsd auth_rpcgss lockd grace sunrpc md_mod zfs(PO) spl(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls xe drm_gpuvm drm_exec gpu_sched drm_ttm_helper drm_suballoc_helper iwlmvm i915 mac80211 intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel libarc4 kvm iosf_mbi drm_buddy ttm i2c_algo_bit drm_display_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 drm_kms_helper sha256_ssse3 Jun 1 13:47:18 Tower kernel: btusb sha1_ssse3 aesni_intel btrtl btbcm crypto_simd btintel cryptd drm bluetooth iwlwifi mei_hdcp mei_pxp nvme rapl intel_gtt intel_cstate cfg80211 wmi_bmof intel_uncore igc i2c_i801 agpgart mei_me i2c_smbus nvme_core mei i2c_core ahci led_class tpm_crb rfkill libahci tpm_tis vmd tpm_tis_core video thermal fan tpm libaescfb wmi ecdh_generic ecc backlight acpi_pad acpi_tad button Jun 1 13:47:18 Tower kernel: CPU: 5 UID: 0 PID: 14402 Comm: nfsd Tainted: P O 6.12.24-Unraid #1 Jun 1 13:47:18 Tower kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE Jun 1 13:47:18 Tower kernel: Hardware name: ASUS System Product Name/ROG STRIX B760-I GAMING WIFI, BIOS 1220 07/28/2023 Jun 1 13:47:18 Tower kernel: RIP: 0010:nfserrno+0x45/0x60 [nfsd] Jun 1 13:47:18 Tower kernel: Code: c3 cc cc cc cc 48 ff c0 48 83 f8 27 75 e0 80 3d a1 aa 04 00 00 75 15 48 c7 c7 75 41 ab a1 c6 05 91 aa 04 00 01 e8 2b f2 50 df <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 66 66 2e 0f 1f 84 00 00 00 00 Jun 1 13:47:18 Tower kernel: RSP: 0018:ffffc90005607b60 EFLAGS: 00010282 Jun 1 13:47:18 Tower kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027 Jun 1 13:47:18 Tower kernel: RDX: 0000000000000002 RSI: ffffffff823430e7 RDI: 00000000ffffffff Jun 1 13:47:18 Tower kernel: RBP: ffff8881e992c240 R08: 0000000000000000 R09: ffffffff82da6e70 Jun 1 13:47:18 Tower kernel: R10: 00003fffffffffff R11: 0000000000000173 R12: ffff888150b85740 Jun 1 13:47:18 Tower kernel: R13: ffff8881e992c000 R14: ffff88849ae3cc00 R15: ffff888289cb8028 Jun 1 13:47:18 Tower kernel: FS: 0000000000000000(0000) GS:ffff88903f340000(0000) knlGS:0000000000000000 Jun 1 13:47:18 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 1 13:47:18 Tower kernel: CR2: 0000145e2c2ada50 CR3: 00000001ada40004 CR4: 0000000000772ef0 Jun 1 13:47:18 Tower kernel: PKRU: 55555554 Jun 1 13:47:18 Tower kernel: Call Trace: Jun 1 13:47:18 Tower kernel: <TASK> Jun 1 13:47:18 Tower kernel: nfsd4_encode_fattr4+0x393/0x3d0 [nfsd] Jun 1 13:47:18 Tower kernel: ? nfsd_setuser_and_check_port+0x80/0xd0 [nfsd] Jun 1 13:47:18 Tower kernel: ? call_rcu+0x3cd/0x4a0 Jun 1 13:47:18 Tower kernel: ? write_bytes_to_xdr_buf+0x7d/0xc0 [sunrpc] Jun 1 13:47:18 Tower kernel: nfsd4_encode_getattr+0x2b/0x40 [nfsd] Jun 1 13:47:18 Tower kernel: nfsd4_encode_operation+0x9e/0x240 [nfsd] Jun 1 13:47:18 Tower kernel: nfsd4_proc_compound+0x24e/0x5f0 [nfsd] Jun 1 13:47:18 Tower kernel: nfsd_dispatch+0x112/0x200 [nfsd] Jun 1 13:47:18 Tower kernel: svc_process_common+0x396/0x5d0 [sunrpc] Jun 1 13:47:18 Tower kernel: ? __pfx_nfsd_dispatch+0x10/0x10 [nfsd] Jun 1 13:47:18 Tower kernel: svc_process+0xce/0x130 [sunrpc] Jun 1 13:47:18 Tower kernel: svc_recv+0x62a/0x740 [sunrpc] Jun 1 13:47:18 Tower kernel: nfsd+0xbb/0xe0 [nfsd] Jun 1 13:47:18 Tower kernel: ? __pfx_nfsd+0x10/0x10 [nfsd] Jun 1 13:47:18 Tower kernel: kthread+0xec/0x100 Jun 1 13:47:18 Tower kernel: ? __pfx_kthread+0x10/0x10 Jun 1 13:47:18 Tower kernel: ret_from_fork+0x21/0x40 Jun 1 13:47:18 Tower kernel: ? __pfx_kthread+0x10/0x10 Jun 1 13:47:18 Tower kernel: ret_from_fork_asm+0x1a/0x30 Jun 1 13:47:18 Tower kernel: </TASK> Jun 1 13:47:18 Tower kernel: ---[ end trace 0000000000000000 ]--- Jun 1 13:47:33 Tower rpc.mountd[14411]: Cannot export /mnt/user/general, possibly unsupported filesystem or fsid= required Jun 1 13:48:00 Tower kernel: mdcmd (36): nocheck cancelStill happening
March 9Mar 9 issue started about 2 months ago, I had a failing USB drive at that time so I dismissed it. now fresh USB drive, it keeps happening, with time between crashes in the 1 to 7 days. 16 docker containers, most of them in br0 network mode with fixed IP.where to look to find debug info?
March 9Mar 9 Community Expert In principle you would look in your system's diagnostics, and perhaps post the zip file for informed feedback.The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. If you want a version that services a crash/reboot then you should enable the syslog server (probably with the option to Mirror to Flash set) to see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.
April 4Apr 4 Author I'm screaming into the abyss here probably, but here we go again with this problem. I've gone for about 2 years without this problem and all of the sudden BAM, I'm plagued again. It has happened to me twice in the few days, about 3 days apart from each other.First time, I was on the shell moving files from a disk to cache and within a half second of typing this command:#mv /mnt/disk5/some/files/* /mnt/cache/some/directory--transport endpoint not connected.The second time, I was using lidarr and within lidarr I changed the parent directory of music files:/mnt/user/media/music/artist to /mnt/user/media/other-music-dir/artist (where, "media" is the share name. moved within the share itself)--transport endpoint not connected.^^^ I don't know if related of not, but I noticed the problem when I was in nemo (linux mint file manager), and nemo was fixed on the directory I moved FROM and it flipped out with a bunch of errors about not being able to reach the server. At first I thought it was simply because I moved that directory within lidarr so of course it couldn't reach it, but then soon noticed it was more severe than that.Both times the server was not doing anything out of the ordinary. The only (major) recent change the server has had is the addition of an nvidia RTX video card. Come to think of it, that's the only time I've had this problem is with a video card installed... HMM, I doubt it's related, but as long as we're throwing darts..... I was problem-free the past 2 years with no video card installed.
April 4Apr 4 Community Expert There's a known limitation using NFS with FUSE, mostly because NFS uses inodes to track files, and they change if the file changes storage, which can sometimes make shfs crash, this is a very old issue.If you need to go through user shares, I recommend using SMB only. NFS will be OK if used with disk or exclusive shares.
April 6Apr 6 Author On 4/4/2026 at 5:27 PM, JorgeB said:There's a known limitation using NFS with FUSE, mostly because NFS uses inodes to track files, and they change if the file changes storage, which can sometimes make shfs crash, this is a very old issue.If you need to go through user shares, I recommend using SMB only. NFS will be OK if used with disk or exclusive shares.I don't use NFS. At all. None of my shares are NFS exported. And as I stated, one of the times it happened I was on the shell using the 'mv' command.
April 6Apr 6 Community Expert 4 hours ago, grants169 said:I don't use NFS. At all. None of my shares are NFS exported.Is the NFS service enabled? It just needs that to cause the issue. If it's disabled and you are still having issues, please post the diags after the problem occurs.
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.