I don't enabled the visibility of Recycle Bin on Shares, than I have only the Option with File Manager or a Docker Container like Krusader.

Is there something in particular i have to do to get a linux machine to correctly move deleted files into the .Recycle.Bin folder instead of creating its own .trash-1000 folder? I have previously only accessed shares via a windows machine.

Confirmed.
Installed, Setup. Delete a file. Didn't Work. (But saw the .Recycle Bin folder. Empty)
Restarting the Array fixed it.

Only thing buggier than this Plugin would be a locust swarm, like literally. Stupid thing never works properly, deleted things either get fully deleted with this plugin on or they end up in the trash folder even if this plugin is turned off and even an uninstallation wouldn't correct that one needs to restart their mfking server to stop this plugin's nonsense. now I ask with genuine sincerity, was the dev who made this plugin high while coding this or is he/she plainly punking us ?

That's look really Strange!

Its only working for SMB. When over ways used to delete data that's not involved by the Plugin.

But the Developer can this more clarified for you.

Many years ago I posted example code showing that it was excluding many file extensions from the recycle bin.

I think I did all single, two, three and four digit extensions and most were not moved to the recycle bin. I had about two million files with the extension text put into the text file and only a few types made it into the recycle bin.

It must have changed by now.

On 7/14/2025 at 1:35 AM, Revan335 said:

That's look really Strange!

Its only working for SMB. When over ways used to delete data that's not involved by the Plugin.

But the Developer can this more clarified for you.

That's correct. This plugin is only for deletions via SMB. Any other deletions are not handled and are out of scope for this at least short term.

On 7/13/2025 at 6:58 PM, mrchem said:

Only thing buggier than this Plugin would be a locust swarm, like literally. Stupid thing never works properly, deleted things either get fully deleted with this plugin on or they end up in the trash folder even if this plugin is turned off and even an uninstallation wouldn't correct that one needs to restart their mfking server to stop this plugin's nonsense. now I ask with genuine sincerity, was the dev who made this plugin high while coding this or is he/she plainly punking us ?

There are some issues I've identified that should help with this situation. Unfortunately I am unable to make any changes. LT has forked my plugin and I no longer have access to make any updates because LT is supporting and maintaining the plugin at this point.

Since I can't make any updates, please don't take it out on me for a poorly running plugin I originally authored, but can no longer update.

Edited July 15, 2025Jul 15 by dlandon

On 7/15/2025 at 1:38 PM, dlandon said:

Since I can't make any updates,

Everyone is free to issue PRs if there is an issue they've identified and fixed that LT hasn't done yet

Hi dlandon,

Many thanks for the plugin! I am using the latest version and we have a Mac environment in our office. Recently we noticed that when deleting files from shares, they get removed and then pop up again where they were. When we delete again, they finally get removed. I assume this is an issue with your plugin and not with Unraid itself. Maybe a special MacOS SMB "bug behaviour"?

Maybe someone else having the same issue or you know where I could look at in my settings?

Thanks a bunch in advance!

I am no longer working on this plugin. LT has taken over the maintenance and support. You will need to contact them about any issues or concerns you have. Future releases will come from them, and not me.

Forgive me if this has already been asked; I wasn't able to find a response...but can I specify multiple excluded shares? For example, a comma separated list of different explicit share names?

Edited September 4, 2025Sep 4 by sydlexius
clarifying the question with an example.

5 hours ago, sydlexius said:

Forgive me if this has already been asked; I wasn't able to find a response...but can I specify multiple excluded shares? For example, a comma separated list of different explicit share names?

On 8/11/2025 at 9:52 AM, dlandon said:

I am no longer working on this plugin. LT has taken over the maintenance and support. You will need to contact them about any issues or concerns you have. Future releases will come from them, and not me.

FYI I want to mention your plugins are great man and I appreciate all the work you put into it.

I hve some issues with recycle bin again, not sure if it started when i upgraded to 7.1.4 but for whatever reason recycle bin will not pickup files inside /mnt/user/Temp/.Recycle.Bin , it does however pickup all the files from other shares such as /mnt/user/Media/.Recycle.Bin /mnt/user/Applications/.Recycle.Bin

when i delete a file inside /mnt/user/Temp it is successfully logged (Oct 29 12:30:42 MOVED_TO => /mnt/user/Temp/.Recycle.Bin/fdsfdsfdsfsfdsf.txt) but the bin itself wil not be displayed in the row above shere you can see the size of each bin for each share that has contents in their bins, i can see the other bins just fine.

Checking the permissions for the bin, all seems fine:

root@NAS:~# ls -ld /mnt/user/Temp/.Recycle.Bin

drwxrwxrwx 1 nobody users 84 Oct 29 12:30 /mnt/user/Temp/.Recycle.Bin/

Ive reinstalled the plugin, restarted the plugin, tweaked settings, ive verified the share setting for the Temp share, nothing seem to help, the plugin will not display the contents of the bin for the Temp share even though the bin has multiple files and the plugin itself is also logging the deletions that are being made to the bin itself.

Worth noting the recycle bin is showing "Recycle Bin total size 0B" even though right below in the share section we see 3 different shares with 65gb, 392gb and 13.8gb as well

This was not a problem previously, i am unsure when it started but pretty sure it started when i updated to 7.1.4

Your ideas are welcome.

EDIT: I found the issue, the data contained in /mnt/user/Temp/.Recycle.Bin was so large the script that builds the stats for recycle bin timed out which was why temp never showed up in the list, i went in and manually deleted some stuff and there were over a million files and 24tb of data in there, yeah ive been doing some cleaning, now it works fine again.

Edited October 29, 2025Oct 29 by je82

On 11/1/2025 at 3:40 PM, Zombexx said:

Hey it seems like this plugin is broken in Unraid version 7.2.0? Every file that i delete wont move into the recycling folder and is deleted permanently from the server.

It works fine for me. How are you trying to delete?

20 hours ago, Squid said:

It works fine for me. How are you trying to delete?

hey i deleted my comment. It seems like that it was an issue with my system at the time

Is anyone else having issues on 7.2.2? When I upgraded from 7.0.1 attempting to delete files/folders created prior to the upgrade caused SMBd panics and fails to delete the file whilst I could delete newer files just file.

I downgraded back to 7.0.1 and it now works.

Dec 10 12:10:45 HP-SVR smbd[11000]: [2025/12/10 12:10:45.912632, 0] ../../source3/smbd/files.c:1141(openat_pathref_fsp_nosymlink)

Dec 10 12:10:45 HP-SVR smbd[11000]: PANIC: assert failed at ../../source3/smbd/files.c(1141): rel_fname.base_name[0] != '\0'

Dec 10 12:10:45 HP-SVR smbd[11000]: [2025/12/10 12:10:45.912693, 0] ../../lib/util/fault.c:178(smb_panic_log)

Dec 10 12:10:45 HP-SVR smbd[11000]: ===============================================================

Dec 10 12:10:45 HP-SVR smbd[11000]: [2025/12/10 12:10:45.912708, 0] ../../lib/util/fault.c:179(smb_panic_log)

Dec 10 12:10:45 HP-SVR smbd[11000]: INTERNAL ERROR: assert failed: rel_fname.base_name[0] != '\0' in smbd (smbd[192.168.0.) (client [192.168.0.45]) pid 11000 (4.23.2)

Dec 10 12:10:45 HP-SVR smbd[11000]: [2025/12/10 12:10:45.912719, 0] ../../lib/util/fault.c:186(smb_panic_log)

Dec 10 12:10:45 HP-SVR smbd[11000]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting

Dec 10 12:10:45 HP-SVR smbd[11000]: [2025/12/10 12:10:45.912729, 0] ../../lib/util/fault.c:191(smb_panic_log)

Dec 10 12:10:45 HP-SVR smbd[11000]: ===============================================================

Dec 10 12:10:45 HP-SVR smbd[11000]: [2025/12/10 12:10:45.912739, 0] ../../lib/util/fault.c:192(smb_panic_log)

Dec 10 12:10:45 HP-SVR smbd[11000]: PANIC (pid 11000): assert failed: rel_fname.base_name[0] != '\0' in 4.23.2

Dec 10 12:10:45 HP-SVR smbd[11000]: [2025/12/10 12:10:45.913049, 0] ../../lib/util/fault.c:303(log_stack_trace)

Dec 10 12:10:45 HP-SVR smbd[11000]: BACKTRACE: 38 stack frames:

Dec 10 12:10:45 HP-SVR smbd[11000]: #0 /usr/lib64/libgenrand-private-samba.so(log_stack_trace+0x29) [0x146ed2fe95b9]

Dec 10 12:10:45 HP-SVR smbd[11000]: #1 /usr/lib64/libgenrand-private-samba.so(smb_panic+0x9) [0x146ed2fe9849]

Dec 10 12:10:45 HP-SVR smbd[11000]: #2 /usr/lib64/libsmbd-base-private-samba.so(openat_pathref_fsp_nosymlink+0x35b) [0x146ed341df4b]

Dec 10 12:10:45 HP-SVR smbd[11000]: #3 /usr/lib64/libsmbd-base-private-samba.so(filename_convert_dirfsp_nosymlink+0x439) [0x146ed343d109]

Dec 10 12:10:45 HP-SVR smbd[11000]: #4 /usr/lib64/libsmbd-base-private-samba.so(filename_convert_dirfsp_rel+0xb8) [0x146ed343de48]

Dec 10 12:10:45 HP-SVR smbd[11000]: #5 /usr/lib64/libsmbd-base-private-samba.so(fd_openat+0xf9) [0x146ed3441629]

Dec 10 12:10:45 HP-SVR smbd[11000]: #6 /usr/lib64/libsmbd-base-private-samba.so(+0x5261c) [0x146ed341d61c]

Dec 10 12:10:45 HP-SVR smbd[11000]: #7 /usr/lib64/libsmbd-base-private-samba.so(openat_pathref_fsp+0x1d2) [0x146ed3420102]

Dec 10 12:10:45 HP-SVR smbd[11000]: #8 /usr/lib64/vfs/fruit.so(+0xe6d2) [0x146ecdf216d2]

Dec 10 12:10:45 HP-SVR smbd[11000]: #9 /usr/lib64/vfs/fruit.so(+0xe884) [0x146ecdf21884]

Dec 10 12:10:45 HP-SVR smbd[11000]: #10 /usr/lib64/vfs/fruit.so(+0x10803) [0x146ecdf23803]

Dec 10 12:10:45 HP-SVR smbd[11000]: #11 /usr/lib64/vfs/catia.so(+0x4adf) [0x146ecdf09adf]

Dec 10 12:10:45 HP-SVR smbd[11000]: #12 /usr/lib64/vfs/recycle.so(+0x31e3) [0x146ece2e21e3]

Dec 10 12:10:45 HP-SVR smbd[11000]: #13 /usr/lib64/vfs/streams_xattr.so(+0x6061) [0x146ecdf3d061]

Dec 10 12:10:45 HP-SVR smbd[11000]: #14 /usr/lib64/vfs/catia.so(+0x6949) [0x146ecdf0b949]

Dec 10 12:10:45 HP-SVR smbd[11000]: #15 /usr/lib64/libsmbd-base-private-samba.so(close_file_smb+0x732) [0x146ed344d982]

Dec 10 12:10:45 HP-SVR smbd[11000]: #16 /usr/lib64/libsmbd-base-private-samba.so(+0xba2fb) [0x146ed34852fb]

Dec 10 12:10:45 HP-SVR smbd[11000]: #17 /usr/lib64/libsmbd-base-private-samba.so(smbd_smb2_request_process_close+0x1fe) [0x146ed3485d2e]

Dec 10 12:10:45 HP-SVR smbd[11000]: #18 /usr/lib64/libsmbd-base-private-samba.so(smbd_smb2_request_dispatch+0x10f4) [0x146ed3478904]

Dec 10 12:10:45 HP-SVR smbd[11000]: #19 /usr/lib64/libsmbd-base-private-samba.so(+0xae9b8) [0x146ed34799b8]

Dec 10 12:10:45 HP-SVR smbd[11000]: #20 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x146ed2f9dc41]

Dec 10 12:10:45 HP-SVR smbd[11000]: #21 /usr/lib64/libtevent.so.0(+0x100ae) [0x146ed2fa50ae]

Dec 10 12:10:45 HP-SVR smbd[11000]: #22 /usr/lib64/libtevent.so.0(+0xdb37) [0x146ed2fa2b37]

Dec 10 12:10:45 HP-SVR smbd[11000]: #23 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8f) [0x146ed2f9cd9f]

Dec 10 12:10:45 HP-SVR smbd[11000]: #24 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x146ed2f9d09b]

Dec 10 12:10:45 HP-SVR smbd[11000]: #25 /usr/lib64/libtevent.so.0(+0xdad7) [0x146ed2fa2ad7]

Dec 10 12:10:45 HP-SVR smbd[11000]: #26 /usr/lib64/libsmbd-base-private-samba.so(smbd_process+0x88c) [0x146ed346739c]

Dec 10 12:10:45 HP-SVR smbd[11000]: #27 /usr/sbin/smbd() [0x40b97b]

Dec 10 12:10:45 HP-SVR smbd[11000]: #28 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x146ed2f9dc41]

Dec 10 12:10:45 HP-SVR smbd[11000]: #29 /usr/lib64/libtevent.so.0(+0x100ae) [0x146ed2fa50ae]

Dec 10 12:10:45 HP-SVR smbd[11000]: #30 /usr/lib64/libtevent.so.0(+0xdb37) [0x146ed2fa2b37]

Dec 10 12:10:45 HP-SVR smbd[11000]: #31 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8f) [0x146ed2f9cd9f]

Dec 10 12:10:45 HP-SVR smbd[11000]: #32 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x146ed2f9d09b]

Dec 10 12:10:45 HP-SVR smbd[11000]: #33 /usr/lib64/libtevent.so.0(+0xdad7) [0x146ed2fa2ad7]

Dec 10 12:10:45 HP-SVR smbd[11000]: #34 /usr/sbin/smbd(main+0x1533) [0x408433]

Dec 10 12:10:45 HP-SVR smbd[11000]: #35 /lib64/libc.so.6(+0x2ad14) [0x146ed2dafd14]

Dec 10 12:10:45 HP-SVR smbd[11000]: #36 /lib64/libc.so.6(__libc_start_main+0x86) [0x146ed2dafdc6]

Dec 10 12:10:45 HP-SVR smbd[11000]: #37 /usr/sbin/smbd(_start+0x21) [0x409021]

Dec 10 12:10:45 HP-SVR smbd[11000]: [2025/12/10 12:10:45.913293, 0] ../../source3/lib/dumpcore.c:316(dump_core)

Dec 10 12:10:45 HP-SVR smbd[11000]: dumping core in /var/log/samba/cores/smbd

Dec 10 12:10:45 HP-SVR smbd[11000]:

Dec 10 12:11:20 HP-SVR smbd[47714]: [2025/12/10 12:11:20.537255, 0] ../../source3/smbd/files.c:1141(openat_pathref_fsp_nosymlink)

Dec 10 12:11:20 HP-SVR smbd[47714]: PANIC: assert failed at ../../source3/smbd/files.c(1141): rel_fname.base_name[0] != '\0'

Dec 10 12:11:20 HP-SVR smbd[47714]: [2025/12/10 12:11:20.537319, 0] ../../lib/util/fault.c:178(smb_panic_log)

Dec 10 12:11:20 HP-SVR smbd[47714]: ===============================================================

Dec 10 12:11:20 HP-SVR smbd[47714]: [2025/12/10 12:11:20.537337, 0] ../../lib/util/fault.c:179(smb_panic_log)

Dec 10 12:11:20 HP-SVR smbd[47714]: INTERNAL ERROR: assert failed: rel_fname.base_name[0] != '\0' in smbd (smbd[192.168.0.) (client [192.168.0.45]) pid 47714 (4.23.2)

Dec 10 12:11:20 HP-SVR smbd[47714]: [2025/12/10 12:11:20.537351, 0] ../../lib/util/fault.c:186(smb_panic_log)

Dec 10 12:11:20 HP-SVR smbd[47714]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting

Dec 10 12:11:20 HP-SVR smbd[47714]: [2025/12/10 12:11:20.537365, 0] ../../lib/util/fault.c:191(smb_panic_log)

Dec 10 12:11:20 HP-SVR smbd[47714]: ===============================================================

Dec 10 12:11:20 HP-SVR smbd[47714]: [2025/12/10 12:11:20.537381, 0] ../../lib/util/fault.c:192(smb_panic_log)

Dec 10 12:11:20 HP-SVR smbd[47714]: PANIC (pid 47714): assert failed: rel_fname.base_name[0] != '\0' in 4.23.2

Dec 10 12:11:20 HP-SVR smbd[47714]: [2025/12/10 12:11:20.537747, 0] ../../lib/util/fault.c:303(log_stack_trace)

Dec 10 12:11:20 HP-SVR smbd[47714]: BACKTRACE: 38 stack frames:

Dec 10 12:11:20 HP-SVR smbd[47714]: #0 /usr/lib64/libgenrand-private-samba.so(log_stack_trace+0x29) [0x146ed2fe95b9]

Dec 10 12:11:20 HP-SVR smbd[47714]: #1 /usr/lib64/libgenrand-private-samba.so(smb_panic+0x9) [0x146ed2fe9849]

Dec 10 12:11:20 HP-SVR smbd[47714]: #2 /usr/lib64/libsmbd-base-private-samba.so(openat_pathref_fsp_nosymlink+0x35b) [0x146ed341df4b]

Dec 10 12:11:20 HP-SVR smbd[47714]: #3 /usr/lib64/libsmbd-base-private-samba.so(filename_convert_dirfsp_nosymlink+0x439) [0x146ed343d109]

Dec 10 12:11:20 HP-SVR smbd[47714]: #4 /usr/lib64/libsmbd-base-private-samba.so(filename_convert_dirfsp_rel+0xb8) [0x146ed343de48]

Dec 10 12:11:20 HP-SVR smbd[47714]: #5 /usr/lib64/libsmbd-base-private-samba.so(fd_openat+0xf9) [0x146ed3441629]

Dec 10 12:11:20 HP-SVR smbd[47714]: #6 /usr/lib64/libsmbd-base-private-samba.so(+0x5261c) [0x146ed341d61c]

Dec 10 12:11:20 HP-SVR smbd[47714]: #7 /usr/lib64/libsmbd-base-private-samba.so(openat_pathref_fsp+0x1d2) [0x146ed3420102]

Dec 10 12:11:20 HP-SVR smbd[47714]: #8 /usr/lib64/vfs/fruit.so(+0xe6d2) [0x146ecdf216d2]

Dec 10 12:11:20 HP-SVR smbd[47714]: #9 /usr/lib64/vfs/fruit.so(+0xe884) [0x146ecdf21884]

Dec 10 12:11:20 HP-SVR smbd[47714]: #10 /usr/lib64/vfs/fruit.so(+0x10803) [0x146ecdf23803]

Dec 10 12:11:20 HP-SVR smbd[47714]: #11 /usr/lib64/vfs/catia.so(+0x4adf) [0x146ecdf09adf]

Dec 10 12:11:20 HP-SVR smbd[47714]: #12 /usr/lib64/vfs/recycle.so(+0x31e3) [0x146ece2e21e3]

Dec 10 12:11:20 HP-SVR smbd[47714]: #13 /usr/lib64/vfs/streams_xattr.so(+0x6061) [0x146ecdf3d061]

Dec 10 12:11:20 HP-SVR smbd[47714]: #14 /usr/lib64/vfs/catia.so(+0x6949) [0x146ecdf0b949]

Dec 10 12:11:20 HP-SVR smbd[47714]: #15 /usr/lib64/libsmbd-base-private-samba.so(close_file_smb+0x732) [0x146ed344d982]

Dec 10 12:11:20 HP-SVR smbd[47714]: #16 /usr/lib64/libsmbd-base-private-samba.so(+0xba2fb) [0x146ed34852fb]

Dec 10 12:11:20 HP-SVR smbd[47714]: #17 /usr/lib64/libsmbd-base-private-samba.so(smbd_smb2_request_process_close+0x1fe) [0x146ed3485d2e]

Dec 10 12:11:20 HP-SVR smbd[47714]: #18 /usr/lib64/libsmbd-base-private-samba.so(smbd_smb2_request_dispatch+0x10f4) [0x146ed3478904]

Dec 10 12:11:20 HP-SVR smbd[47714]: #19 /usr/lib64/libsmbd-base-private-samba.so(+0xae9b8) [0x146ed34799b8]

Dec 10 12:11:20 HP-SVR smbd[47714]: #20 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x146ed2f9dc41]

Dec 10 12:11:20 HP-SVR smbd[47714]: #21 /usr/lib64/libtevent.so.0(+0x100ae) [0x146ed2fa50ae]

Dec 10 12:11:20 HP-SVR smbd[47714]: #22 /usr/lib64/libtevent.so.0(+0xdb37) [0x146ed2fa2b37]

Dec 10 12:11:20 HP-SVR smbd[47714]: #23 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8f) [0x146ed2f9cd9f]

Dec 10 12:11:20 HP-SVR smbd[47714]: #24 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x146ed2f9d09b]

Dec 10 12:11:20 HP-SVR smbd[47714]: #25 /usr/lib64/libtevent.so.0(+0xdad7) [0x146ed2fa2ad7]

Dec 10 12:11:20 HP-SVR smbd[47714]: #26 /usr/lib64/libsmbd-base-private-samba.so(smbd_process+0x88c) [0x146ed346739c]

Dec 10 12:11:20 HP-SVR smbd[47714]: #27 /usr/sbin/smbd() [0x40b97b]

Dec 10 12:11:20 HP-SVR smbd[47714]: #28 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x146ed2f9dc41]

Dec 10 12:11:20 HP-SVR smbd[47714]: #29 /usr/lib64/libtevent.so.0(+0x100ae) [0x146ed2fa50ae]

Dec 10 12:11:20 HP-SVR smbd[47714]: #30 /usr/lib64/libtevent.so.0(+0xdb37) [0x146ed2fa2b37]

Dec 10 12:11:20 HP-SVR smbd[47714]: #31 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8f) [0x146ed2f9cd9f]

Dec 10 12:11:20 HP-SVR smbd[47714]: #32 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x146ed2f9d09b]

Dec 10 12:11:20 HP-SVR smbd[47714]: #33 /usr/lib64/libtevent.so.0(+0xdad7) [0x146ed2fa2ad7]

Dec 10 12:11:20 HP-SVR smbd[47714]: #34 /usr/sbin/smbd(main+0x1533) [0x408433]

Dec 10 12:11:20 HP-SVR smbd[47714]: #35 /lib64/libc.so.6(+0x2ad14) [0x146ed2dafd14]

Dec 10 12:11:20 HP-SVR smbd[47714]: #36 /lib64/libc.so.6(__libc_start_main+0x86) [0x146ed2dafdc6]

Dec 10 12:11:20 HP-SVR smbd[47714]: #37 /usr/sbin/smbd(_start+0x21) [0x409021]

Dec 10 12:11:20 HP-SVR smbd[47714]: [2025/12/10 12:11:20.538038, 0] ../../source3/lib/dumpcore.c:316(dump_core)

Dec 10 12:11:20 HP-SVR smbd[47714]: dumping core in /var/log/samba/cores/smbd

Dec 10 12:11:20 HP-SVR smbd[47714]:

Note: I have run docker safe new permissions and run a file system check on all drives.

hp-svr-diagnostics-20251210-1240.zip

On 12/14/2025 at 8:49 PM, tech3475 said:

Is anyone else having issues on 7.2.2? When I upgraded from 7.0.1 attempting to delete files/folders created prior to the upgrade caused SMBd panics and fails to delete the file whilst I could delete newer files just file.

I downgraded back to 7.0.1 and it now works.

Note: I have run docker safe new permissions and run a file system check on all drives.

hp-svr-diagnostics-20251210-1240.zip

There is a problem with the configuration written by the plugin。

plugin error fix: https://raw.githubusercontent.com/bigfoxtail/recycle.bin/refs/heads/master/recycle.bin.plg

https://github.com/bigfoxtail/recycle.bin

No, I was wrong. It still doesn’t work.

😭😭😭

Edited January 16Jan 16 by bigfoxtail

7 hours ago, bigfoxtail said:

There is a problem with the configuration written by the plugin。

There is, but it is not addressed by this forked plugin. This forked plugin adds the fruit config that is already managed by Unraid - when not needed and potentially twice:
[isos]

browseable = No

comment = ISO images

path = /mnt/user/isos

valid users = *********

veto files = /.Recycle.Bin

vfs objects = catia fruit streams_xattr catia fruit streams_xattr recycle <= fruit potentially added twice

write list = *********

recycle:exclude_dir = ".Recycle.Bin"

recycle:exclude = *.tmp

recycle:versions = Yes

recycle:minsize = 1

recycle:touch_mtime = No

recycle:touch = Yes

recycle:keeptree = Yes

recycle:directory_mode = 0777

recycle:repository = .Recycle.Bin

fruit:encoding = native

This plugin adds the "/etc/samba/smb-fruit.conf" extra settings to the share configuration regardless of the "Enhanced macOS interoperability:" setting. If it is set to "Yes", this plugin adds the extra settings a second time resulting in duplicate vfs_objects. This is an inappropriate samba configuration and could result in redundant operations and issues. There don't seem to be any other changes made by this plugin to the share configuration, so it's unclear as to what's been "fixed". If having those vfs_objects added appears to fix the samba fault, it is a fluke because that is not the solution.

The issue is in how samba handles the repository. The older versions of samba were a bit more tolerant of inappropriate confiuguration settings. The newer versions of samba are stricter about the configuration settings.

I discourage the use of this forked plugin as it does nothing to address the issue amd may in fact cause problems.

Edited December 21, 2025Dec 21 by dlandon

On 11/6/2025 at 4:13 PM, Zombexx said:

hey i deleted my comment. It seems like that it was an issue with my system at the time

It's not just you. It does not work for me and I found a few people on Reddit who cannot get it to work either.

I have restarted the server, restarted just the array, enabled file delete logs, unmounted and remounted the share in Windows, tried deleting files through the Unraid web interface directly and no matter what I do, it never logs a file being deleted and the recycle bin folders the plugin creates remain empty.

I have tried it on 7.2.2 and 7.2.3 with the same results.

1 hour ago, AdmiralSpeedy said:

tried deleting files through the Unraid web interface directly

It only works with SMB as in the title and explained in the first post.

8 hours ago, trurl said:

It only works with SMB as in the title and explained in the first post.

If you read my comment, you'll see I am using SMB with the share mounted in Windows and it doesn't work.

I only tried through the Unraid interface as a last resort (because at the time I didn't realize it only worked through SMB).

1 hour ago, AdmiralSpeedy said:

If you read my comment, you'll see I am using SMB with the share mounted in Windows and it doesn't work.

I only tried through the Unraid interface as a last resort (because at the time I didn't realize it only worked through SMB).

Is the share you are trying this on an exclusive share or a pool device?

3 minutes ago, dlandon said:

Is the share you are trying this on an exclusive share or a pool device?

I have an array with a single SSD as a cache pool. I thought it might have something do with that as well, but I did try deleting an old file that was on the array and not something I just created to test that would still be on the cache pool.