Recycle bin retention is not working volume is filling up
Posted: 25 Feb 2022, 20:36
The recycle bin doesn't seem to be deleting files past the retention period that is set. I have retention set between 10 and 30 days on respective shares and I see files in the recycle bin of all my shares that are far older than the retention limit. For example the backups share (containing all PC and server backups) has a retention of 30 days however I see files that are 90 days old in these recycle bin folders.
I can manually delete the files which clears up space on the volume but the whole point is to have the NAS manage that automatically. I created a Powershell script to run daily and delete files 30 days and older from Backups\#Recycle but this creates other problems as the script seems to break permissions on some of the folders and they become orphaned. I have to Putty into the TNAS and manually delete folders or use the management console to do it. It is very frustrating. Is there a service that controls this retention or something I can fix to get this to work?
I'm running the latest version of TOS. Terror Master support said in another thread that this issue would be resolved with the firmware released in July or August 2021 it clearly has not been resolved because it is still occurring on the most current firmware released in January 2022 I'm running with this configuration.
F4-210
TOS 4.2.28
4 drives RAID5 12TB
I can manually delete the files which clears up space on the volume but the whole point is to have the NAS manage that automatically. I created a Powershell script to run daily and delete files 30 days and older from Backups\#Recycle but this creates other problems as the script seems to break permissions on some of the folders and they become orphaned. I have to Putty into the TNAS and manually delete folders or use the management console to do it. It is very frustrating. Is there a service that controls this retention or something I can fix to get this to work?
I'm running the latest version of TOS. Terror Master support said in another thread that this issue would be resolved with the firmware released in July or August 2021 it clearly has not been resolved because it is still occurring on the most current firmware released in January 2022 I'm running with this configuration.
F4-210
TOS 4.2.28
4 drives RAID5 12TB