So I could be wrong, but am trying to pinpoint the exact root cause here. I've been using Unraid for a couple years with no cache drive issues previously (and am currently on version 6.9.2), but I've noticed in the last week or so that my cache drive (a 500GB SSD) is staying "fuller" than usual. My theory is that the Data folder is not consistently being moved from the cache to array?

 

In looking at the shares I have set up, the cache ends up holding appdata (65GB), domains (11GB), system (44GB). And then Data will temporarily store itself on cache (in theory), before moving to the data drives once a day via the scheduler.

 

However, I currently see 384GB of it filled:

 

By doing some digging, I found that the Data folder on the cache drive is currently holding ~246GB of files (it's all >Downloads>completed from my various 'arr applications). That Data, plus all of my shares marked "Prefer:Cache" seems to add up to roughly the 384GB on drive space used.

 

However, when I total up all of the new files that have downloaded in the last day (i.e. what should be at most temporarily sitting in the cache drive's Data folder), it only adds up to ~5GB. And when I look at the cache drive's Data folder, I'm seeing torrent files that were downloaded ~9 days ago still in there.

 

I have the mover scheduled to run at 4:30am daily:

 

I've attached my diagnostics file. Would it be helpful for me to enable mover logging, and then post another diagnostics file in the morning after the 4:30am trigger occurs?

 

Any help is appreciated!

 

magic-diagnostics-20220810-1639.zip

Edited August 11, 20223 yr by Magic815

3 hours ago, Magic815 said:

And when I look at the cache drive's Data folder, I'm seeing torrent files that were downloaded ~9 days ago still in there.

If you're still seeding them the files will be open, and the mover can't move open files. Try stopping your torrent container and running the mover manually.

Edited August 11, 20223 yr by Kilrah

6 hours ago, Kilrah said:

If you're still seeding them the files will be open, and the mover can't move open files. Try stopping your torrent container and running the mover manually.

Does just the torrent container need to be stopped, or do I need to stop the entire docker service and VM service?

 

What's interesting through is that my 'Data' has always been filled with seeded torrents, and my cache drive utilization used to always drop in the morning after the mover run. One change I did make a few weeks back was switching from the 'delugevpn' docker to the 'qbittorrent-vpn'. (I had been previously running the deluge one for years.) Do people set up some of sort of script to stop the torrent container when the mover is running - and maybe that was something I set up with deluge years ago and forgot about?

 

For completeness, I've attached my latest diagnostics file with the mover logging enabled.

magic-diagnostics-20220811-0930.zip

Yeah log shows mover skipping all these files, they're probably open.

 

55 minutes ago, Magic815 said:

Does just the torrent container need to be stopped,

Just the containers accessing the files, so probably only the torrent one.

 

55 minutes ago, Magic815 said:

One change I did make a few weeks back was switching from the 'delugevpn' docker to the 'qbittorrent-vpn'. (I had been previously running the deluge one for years.)

Could be it, don't know how each manage their I/O. qB might keep files open even if not actually sending stuff while deluge doesn't...