nfsd Tainted error? - Anyone else seen this before?

[blade316]

I have had a new error pop up this morning ... the trigger was when I logged back into my Mac Mini, and it was telling me it couldn't reconnect to the nfs shares on my unraid server. Quick check in unraid and all the shares are now missing, obviously due to the error. The only device in the house that uses nfs is my mac, which I have been using with nfs for a long time with unraid.

 

I've not seen this error before, the only thing I can think of that may have led to this is leaving some finder windows open with those nfs shares overnight.

 

Here is the syslog portion:

 

ar 25 05:21:59 unRAID CA Backup/Restore: #######################
Mar 25 05:21:59 unRAID CA Backup/Restore: appData Backup complete
Mar 25 05:21:59 unRAID CA Backup/Restore: #######################
Mar 25 05:21:59 unRAID CA Backup/Restore: Backup / Restore Completed
Mar 25 07:00:01 unRAID root: mover: started
Mar 25 07:00:02 unRAID root: mover: finished
Mar 25 08:12:40 unRAID autofan: Highest disk temp is 40C, adjusting fan speed from: 112 (43% @ 771rpm) to: 135 (52% @ 713rpm)
Mar 25 10:27:43 unRAID  shfs: shfs: ../lib/fuse.c:1450: unlink_node: Assertion `node->nlookup > 1' failed.
Mar 25 10:27:44 unRAID kernel: ------------[ cut here ]------------
Mar 25 10:27:44 unRAID kernel: nfsd: non-standard errno: -107
Mar 25 10:27:44 unRAID kernel: WARNING: CPU: 6 PID: 7793 at fs/nfsd/nfsproc.c:889 nfserrno+0x45/0x51 [nfsd]
Mar 25 10:27:44 unRAID kernel: Modules linked in: veth nvidia_uvm(PO) xt_nat macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod it87 hwmon_vid efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc ipv6 nvidia_drm(PO) x86_pkg_temp_thermal intel_powerclamp nvidia_modeset(PO) coretemp i915 kvm_intel iosf_mbi drm_buddy ttm nvidia(PO) kvm drm_display_helper drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_gtt mxm_wmi drm intel_cstate agpgart mpt3sas igb i2c_i801 ahci i2c_algo_bit i2c_smbus syscopyarea intel_uncore sysfillrect raid_class libahci sysimgblt atl1c i2c_core scsi_transport_sas fb_sys_fops video
Mar 25 10:27:44 unRAID kernel: wmi thermal fan backlight button unix
Mar 25 10:27:44 unRAID kernel: CPU: 6 PID: 7793 Comm: nfsd Tainted: P           O      5.19.9-Unraid #1
Mar 25 10:27:44 unRAID kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z77MX-D3H, BIOS F17b 01/06/2014
Mar 25 10:27:44 unRAID kernel: RIP: 0010:nfserrno+0x45/0x51 [nfsd]
Mar 25 10:27:44 unRAID 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 34 ef a2 c6 05 bc 47 05 00 01 e8 06 99 90 de <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 48 83 ec 18 31 c9 ba ff 07 00
Mar 25 10:27:44 unRAID kernel: RSP: 0018:ffffc900009a3e30 EFLAGS: 00010286
Mar 25 10:27:44 unRAID kernel: RAX: 0000000000000000 RBX: ffff8881c1490000 RCX: 0000000000000027
Mar 25 10:27:44 unRAID kernel: RDX: 0000000000000001 RSI: ffffffff81ec827f RDI: 00000000ffffffff
Mar 25 10:27:44 unRAID kernel: RBP: ffff888103d64000 R08: 0000000000000000 R09: ffffffff82044990
Mar 25 10:27:44 unRAID kernel: R10: 0000000000000000 R11: ffffffff8264afbe R12: ffff8881c1490008
Mar 25 10:27:44 unRAID kernel: R13: ffff8881c1488000 R14: ffffffffa2f12600 R15: ffffffffa2eeda98
Mar 25 10:27:44 unRAID kernel: FS:  0000000000000000(0000) GS:ffff888810380000(0000) knlGS:0000000000000000
Mar 25 10:27:44 unRAID kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 25 10:27:44 unRAID kernel: CR2: 0000153ca414d638 CR3: 000000000500a002 CR4: 00000000001726e0
Mar 25 10:27:44 unRAID kernel: Call Trace:
Mar 25 10:27:44 unRAID kernel: <TASK>
Mar 25 10:27:44 unRAID kernel: nfsd3_proc_getattr+0xaf/0xd7 [nfsd]
Mar 25 10:27:44 unRAID kernel: nfsd_dispatch+0x194/0x24d [nfsd]
Mar 25 10:27:44 unRAID kernel: svc_process+0x3f1/0x5d6 [sunrpc]
Mar 25 10:27:44 unRAID kernel: ? nfsd_svc+0x2b6/0x2b6 [nfsd]
Mar 25 10:27:44 unRAID kernel: ? nfsd_shutdown_threads+0x5b/0x5b [nfsd]
Mar 25 10:27:44 unRAID kernel: nfsd+0xd5/0x155 [nfsd]
Mar 25 10:27:44 unRAID kernel: kthread+0xe7/0xef
Mar 25 10:27:44 unRAID kernel: ? kthread_complete_and_exit+0x1b/0x1b
Mar 25 10:27:44 unRAID kernel: ret_from_fork+0x22/0x30
Mar 25 10:27:44 unRAID kernel: </TASK>
Mar 25 10:27:44 unRAID kernel: ---[ end trace 0000000000000000 ]---

 

Diagnostic files attached:

 

unraid-diagnostics-20230325-1311.zip

 

Would be great if anyone could shed some light on this one, and where I can start looking.

 

Also side note: other than a reboot or restarting the array, nothing seems to bring the shares back ... unless there is a command I can run that will export all the array shares again?

 

 

[Howboys]

Exact same. I started seeing it a few months ago too but I don't think I had upgraded unraid at all.

 

I can reproduce it by deleting large files from the nfs mount.

 

Related:

 

 

Unfortunately no one from the team has responded

 

 

[dlandon]

Start by updating to a later stable version like 6.11.5 or preferrably 6.12.

[Squid]

FWIW, "Tainted" doesn't particularly mean anything is wrong.  "Tainted" is logged as a message to the kernal maintainers that the OS is not stock linux and that technically because it is not stock they don't have to address any issues which may pop up.

 

IE: "Tainted" is 100% normal in the context of Unraid and isn't an issue in and by itself.  But what @dlandon is suggestion is your first steps.

[Howboys]

3 hours ago, dlandon said:

Start by updating to a later stable version like 6.11.5 or preferrably 6.12.

I'm already on 11.5. 

[dlandon]

1 minute ago, Howboys said:

I'm already on 11.5. 

Provide diagnostics then.  The original poster is still on 6.11.0.