CS01-HS

Running ffmpeg on (I believe) a corrupted video file mapped via 9p caused a fuse error rendering shares inaccessible. Any idea how I can prevent that? The error's fine but I'd prefer if it didn't take down the array. Is there anything obviously wrong with my setup? It's been running stably for a couple of years now. Error in script running in Debian VM. The next line after ffmpeg is a move which fails: frame=200798 fps=531 q=-1.0 Lsize= 2492607kB time=00:55:49.97 bitrate=6095.4kbits/s speed=8.86x mv: failed to access '/mnt/unraid/scratch//test.mp4': Transport endpoint is not connected /etc/fstab: unraid /mnt/unraid 9p trans=virtio,9p2000.L,_netdev,nofail 0 0 VM share config: Error in unraid syslog (I was tailing the syslog server's output when it failed) Nov 17 12:04:14 NAS shfs: shfs: ../lib/fuse.c:1450: unlink_node: Assertion `node->nlookup > 1' failed. Nov 17 12:04:14 NAS rsyslogd: file '/mnt/user/system/logs/syslog-nas.log'[9] 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 17 12:04:14 NAS rsyslogd: file '/mnt/user/system/logs/syslog-nas.log': open error: Transport endpoint is not connected [v8.2102.0 try https://www.rsyslog.com/e/2433 ] Nov 17 12:04:30 NAS kernel: ------------[ cut here ]------------ Nov 17 12:04:30 NAS kernel: nfsd: non-standard errno: -107 Nov 17 12:04:30 NAS kernel: WARNING: CPU: 2 PID: 8911 at fs/nfsd/nfsproc.c:889 nfserrno+0x45/0x51 [nfsd] Nov 17 12:04:30 NAS kernel: Modules linked in: xt_connmark xt_comment iptable_raw xt_mark cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver xt_CHECKSUM xt_nat veth ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc bluetooth ecdh_generic ecc md_mod nct6775 nct6775_core hwmon_vid wmi efivarfs iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 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 af_packet 8021q garp mrp bridge stp llc bonding tls i915 drm_buddy i2c_algo_bit ttm drm_display_helper x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel drm_kms_helper drm kvm processor_thermal_device_pci_legacy Nov 17 12:04:30 NAS kernel: processor_thermal_device processor_thermal_rfim processor_thermal_mbox intel_gtt crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel mpt3sas i2c_i801 aesni_intel agpgart intel_soc_dts_iosf crypto_simd i2c_smbus cryptd rapl r8169 syscopyarea intel_cstate ahci sysfillrect raid_class i2c_core scsi_transport_sas sysimgblt realtek libahci iosf_mbi fb_sys_fops thermal button int3406_thermal video backlight fan dptf_power int3400_thermal acpi_thermal_rel int3403_thermal int340x_thermal_zone unix Nov 17 12:04:30 NAS kernel: CPU: 2 PID: 8911 Comm: nfsd Not tainted 5.19.17-Unraid #2 Nov 17 12:04:30 NAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J5005-ITX, BIOS P1.40 08/06/2018 Nov 17 12:04:30 NAS kernel: RIP: 0010:nfserrno+0x45/0x51 [nfsd] Nov 17 12:04:30 NAS 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 a4 99 a0 c6 05 ab 47 05 00 01 e8 42 07 eb e0 <0f> 0b b8 00 00 00 05 c3 cc cc cc cc 48 83 ec 18 31 c9 ba ff 07 00 Nov 17 12:04:30 NAS kernel: RSP: 0018:ffffc900005ffb58 EFLAGS: 00010282 Nov 17 12:04:30 NAS kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027 Nov 17 12:04:30 NAS kernel: RDX: 0000000000000001 RSI: ffffffff820d7be1 RDI: 00000000ffffffff Nov 17 12:04:30 NAS kernel: RBP: ffffc900005ffdb0 R08: 0000000000000000 R09: ffffffff82244bd0 Nov 17 12:04:30 NAS kernel: R10: 00007fffffffffff R11: ffffffff82876e76 R12: 0000000000000011 Nov 17 12:04:30 NAS kernel: R13: 0000000000e00000 R14: ffff88815a2591a0 R15: ffffffff82909480 Nov 17 12:04:30 NAS kernel: FS: 0000000000000000(0000) GS:ffff888470100000(0000) knlGS:0000000000000000 Nov 17 12:04:30 NAS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 17 12:04:30 NAS kernel: CR2: 000055d456171350 CR3: 00000003229b0000 CR4: 0000000000352ee0 Nov 17 12:04:30 NAS kernel: Call Trace: Nov 17 12:04:30 NAS kernel: <TASK> Nov 17 12:04:30 NAS kernel: nfsd4_encode_fattr+0x1372/0x13d9 [nfsd] Nov 17 12:04:30 NAS kernel: ? getboottime64+0x20/0x2e Nov 17 12:04:30 NAS kernel: ? kvmalloc_node+0x44/0xbc Nov 17 12:04:30 NAS kernel: ? __kmalloc_node+0x1b4/0x1df Nov 17 12:04:30 NAS kernel: ? kvmalloc_node+0x44/0xbc Nov 17 12:04:30 NAS kernel: ? override_creds+0x21/0x34 Nov 17 12:04:30 NAS kernel: ? nfsd_setuser+0x185/0x1a5 [nfsd] Nov 17 12:04:30 NAS kernel: ? nfsd_setuser_and_check_port+0x76/0xb4 [nfsd] Nov 17 12:04:30 NAS kernel: ? nfsd_setuser_and_check_port+0x76/0xb4 [nfsd] Nov 17 12:04:30 NAS kernel: nfsd4_encode_getattr+0x28/0x2e [nfsd] Nov 17 12:04:30 NAS kernel: nfsd4_encode_operation+0xad/0x201 [nfsd] Nov 17 12:04:30 NAS kernel: nfsd4_proc_compound+0x2a7/0x56c [nfsd] Nov 17 12:04:30 NAS kernel: nfsd_dispatch+0x1a6/0x262 [nfsd] Nov 17 12:04:30 NAS kernel: svc_process+0x3ee/0x5d6 [sunrpc] Nov 17 12:04:30 NAS kernel: ? nfsd_svc+0x2b6/0x2b6 [nfsd] Nov 17 12:04:30 NAS kernel: ? nfsd_shutdown_threads+0x5b/0x5b [nfsd] Nov 17 12:04:30 NAS kernel: nfsd+0xd5/0x155 [nfsd] Nov 17 12:04:30 NAS kernel: kthread+0xe4/0xef Nov 17 12:04:30 NAS kernel: ? kthread_complete_and_exit+0x1b/0x1b Nov 17 12:04:30 NAS kernel: ret_from_fork+0x1f/0x30 Nov 17 12:04:30 NAS kernel: </TASK> Nov 17 12:04:30 NAS kernel: ---[ end trace 0000000000000000 ]---Nov 17 12:04:14 NAS shfs: shfs: ../lib/fuse.c:1450:

Yes I've done all of that. My only aim with smb-custom was to define the path explicitly - bypass shfs to avoid SMB-related fuse errors which have broken my shares/necessitated restarts. The rest of those settings I took as-is from testparm.

Got it. Shame there's no simple way to confirm, makes me wonder about my own customizations. Huh, so is it better to put the smb-custom include at the top of smb-extras so scope is [global] when it returns? e.g. #Custom include = /boot/config/smb-custom.conf [global] # Fix for 6.9.0-rc2 Mac client search spotlight backend = tracker # tweaks from https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X min protocol = SMB2 I have a dedicated pool that serves docker, VM and scratch called active (single-disk, XFS), cache is separate. Here's my full smb-custom.conf if you're curious:

That's strange because I don't think spotlight indexing enters into it. If I had to guess maybe some time within those few hours you disconnected/reconnected automatically or explicitly and that's what did it. Either way, glad it worked.

Installed and rebooted - mixed results: The smb-shares include line is still present in the share: [system] case sensitive = Yes comment = system data include = /etc/samba/smb-shares.conf The smb-unassigned include line is gone from the share but it's not present anywhere (according to testparm) Should I add it manually to smb-extras and if so where? [global] # Fix for 6.9.0-rc2 Mac client search spotlight backend = tracker # tweaks from https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X min protocol = SMB2 #Custom include = /boot/config/smb-custom.conf

Only WARNINGS before hitting enter but I think those were always there: root@NAS:/boot/config# testparm -v Load smb config files from /etc/samba/smb.conf lpcfg_do_global_parameter: WARNING: The "null passwords" option is deprecated lpcfg_do_global_parameter: WARNING: The "syslog" option is deprecated Loaded services file OK. Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback) Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions

Add the following line to the [global] section of SMB Extras (which you can do via the GUI): spotlight backend = tracker And the following line to /boot/config/smb-fruit.conf (which will add it to each share) spotlight = yes You can use this post as a reference but I wrote it before the advent of smb-fruit, so this new way is better.

I did a quick test on a share with only a dozen files and no subdirs: With my setup search returned the matching result instantly. Then I added spotlight backend = noindex (the default) to smb-custom, restarted samba and searched again. No results after 30 seconds. So I want to say the fix is an improvement except when I removed the newly-added backend line from smb-custom and restarted, nothing changed - still no results. Maybe a proper test requires stopping and starting the array, which I can't do at the moment.

Oh! Well that's useful information. I've had the fix in place since 6.9 broke it. I must have missed a fix in the release notes. I'll test without it, thanks.

Partially - with the fix I can (once again) search my shares in Finder. That backend override to a nonexistent tracker fails gracefully (the default does not.) Proper "spotlight" is more comprehensive, some solutions on this forum but I haven't investigated.

AFAIK the fix still requires a global setting (which you're seeing in extras) and a per-share setting (which I have in fruit)

Right, I have my per-share customizations in smb-fruit. Why does something look off? (Ignore the commented lines, they're leftover from earlier experimentation)

I noticed a couple of strange entries when I ran testparm -v The include for smb-unassigned.conf was added to my isos share (it's nowhere else in the output): [isos] case sensitive = Yes comment = iso images include = /etc/samba/smb-unassigned.conf ... And similarly smb-shares.conf was added to my system share (which, in case it's relevant, is a cache-only share I export through /boot/config/smb-custom.conf to bypass shfs): [system] comment = system data include = /etc/samba/smb-shares.conf path = /mnt/active/system ... Restarting smb and the server didn't change it so something's adding them. Is that where they belong? I run the UD and Recycle Bin plugins which I know make some modifications. And for reference here's my SMB Extras: [global] # Fix for 6.9.0-rc2 Mac client search spotlight backend = tracker # force inclusion of acl_xattr # (doesn't work because it doesn't propagate to shares) ##vfs objects = acl_xattr catia fruit streams_xattr # tweaks from https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X min protocol = SMB2 #Custom include = /boot/config/smb-custom.conf

Happened to me recently with 6.11.2. In my case it's always triggered by SMB file operations - macOS's poor implementation acting on a stale version of the directory tree, causing invalid operations and the fuse exception. I have to remember to navigate down or up then back to force a refresh.

Interesting - the containers that didn't autostart use my vpn container's custom network. I have the order right (vpn before the others) and wait 60 set on the vpn container but I never considered whether ca.backup observed wait time since it always "just worked" – maybe it used to and now it doesn't. If the plan's to go to container-specific tar files, that delay's probably sufficient to make observance irrelevant.

I had a similar issue with my Debian VM and yt-dlp with 6.11.1. Ended up reverting to 9p.

Kind of, from SimonF's post above - sdspin. I haven't used it in a while though and this post suggests some issues spinning down:

That's probably a different problem - my containers were fine aside from having to start them manually.

Strange problem with my first appdata backup on 6.11.2 - some containers (which were running and set to autostart) weren't restarted post-backup. Maybe coincidence but all the affected containers use a custom network (none of the non-custom network containers failed to start.) Maybe a fluke or maybe an issue with my setup, although I haven't changed anything and this plugin's been rock solid. Anyone else see this?

I have a Media share setup as follows: Media/ Movies/ TV/ I have Recycle Bin enabled for that share: Media/ .Recycle.Bin/ I have a container that deals specifically with Movies. I'd like to restrict its access to the movie dir by setting the container path: /mnt/user/Media/Movies -> /movies But I'd also like to give it access to the Recycle Bin which lives one directory up. I thought I could "trick" it by overlaying the recycling dir on the existing path with an additional path var: /mnt/user/Media/.Recycle.Bin -> /movies/.Recycle.Bin but that didn't work. (It results in the creation of the host path below) /mnt/user/Media/Movies/.Recycle.Bin Currently I pass it the Media share which allows it to access both Movies and .Recycling.Bin - it works but it's not ideal. Is there a proper way to accomplish what I want?

In Live TV -> Advanced I see Default recording path Does setting that change where emby stores tmp live TV files? Well that's easy enough to fix even with an unraid user script. Something like this that runs every hour, deleting ts files more than an hour old: find /host/path/to/transcode/dir/ -type f -name '*.ts' -mindepth 1 -mmin +60 -delete You could even restrict it to files above a certain size with -size +100M

No sorry, I don't use live TV so I've never tested it. I'm guessing they do that for DVR functionality (serves as a reference file which in the standard case is the media itself.) In the best case my script won't have any effect, in the worst case it'll delete it which could break things. If active live TV files can be differentiated by name the script could be tweaked to ignore them, or if not we can infer by size (greater than X.) What are you trying to solve exactly, because my guess is creation of these large files with live TV is unavoidable.

Is it normal to see frequent entries like this in the Recycle Bin's deleted file log? I did have a time machine share at one point but deleted it a while ago. None of my existing shares are exported as "Yes/Time Machine" root@NAS:~# testparm -sv | grep -i 'time machine' Load smb config files from /etc/samba/smb.conf lpcfg_do_global_parameter: WARNING: The "null passwords" option is deprecated lpcfg_do_global_parameter: WARNING: The "syslog only" option is deprecated lpcfg_do_global_parameter: WARNING: The "syslog" option is deprecated Loaded services file OK. Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback) Server role: ROLE_STANDALONE root@NAS:~# I do have Enhanced macOS interoperability enabled if that matters.

That definitely works as long as they don't decide to change the directory structure again. The find should be structure-agnostic (unless I screwed up.)

Initial post updated with fix and various improvements.