henk1122 Posted February 20, 2021 Share Posted February 20, 2021 (edited) Hi, Currently my cache disk is full and my docker containers are failing due that.. Unraid doesn't seem to be moving files to the array when a share is set to "preferred". I've 4 shares which should be always on the cache drive; those are set to only. (Docker, system and VM stuff). Those use little data. I have set my torrent seedbox to the cache, but on preferred. I would assume if my cache disk reaches a full level, it will move those preferred files to the array (I mean, yes is higher priority then preferred, right?). Currently the files are stuck and nothing is being moved. I tried invoking the mover with no luck. I hope someone could determine the bug. It's really annoying because all docker images begin failing and losed data due that. The temporary fix for now was to stop the seedbox and delete torrents to manually make space on the cache drive. This is of course a temporary solution because it's gonna fail soon . -- I've read a bit into it; it also seems that Unraid writes new files to the array if the cache disk is full. But apparently this doesn't work for torrent files (I guess because it could start with an almost empty file). However, this behavior is wrong and not wanted anyway. New files SHOULD be written to the cache because the cache is faster in general then the array. Old files should be moved away then from the cache drive to the array (if it's set to preferred). Edited February 20, 2021 by henk1122 Quote Link to comment
theruck Posted February 20, 2021 Share Posted February 20, 2021 preferred means the data is always on the cache - this confused me too you need to set it to "yes" then the mover will move the files Quote Link to comment
henk1122 Posted February 20, 2021 Author Share Posted February 20, 2021 (edited) "Yes" is not what I want for my torrent box. Then it will always move the files to the array if the mover is invoked. It should be in cache as long as possible (Don't want to waste the cache drive with being empty of course..). But if it runs full, it should move the files (from oldest preferred which seems most logical to me) . I can't find a setting for this. I'm unable to set this "full" limit and leave some headroom for new files (say 100gb). Edited February 20, 2021 by henk1122 Quote Link to comment
theruck Posted February 21, 2021 Share Posted February 21, 2021 it does not work the way you want it to work Quote Link to comment
henk1122 Posted February 21, 2021 Author Share Posted February 21, 2021 Which other option do you suggest? If I put it on "yes" it will move 400GB of the cache drive to the array, which basically waste 400GB of cache. As temp workaround for the bug I added a "minimum free space" of 50GB which at least will leave some headroom now. That still goes terrible wrong if a torrent is larger then 50gb when the file grows. Quote Link to comment
theruck Posted February 21, 2021 Share Posted February 21, 2021 you can keep it on cache or move it with mover or never store to cache. thats it. there is no other option. there is no problem with holding large files on HDDs. SSD cache is good for small files or databases where you need higher IOPS Quote Link to comment
henk1122 Posted February 21, 2021 Author Share Posted February 21, 2021 torrents can also be high IOPS, thats why I want them on cache. Other then that, the bug still exist. If you create a file which fits on the cache on creation time, but then grows, the cache can run out of space. That's not good. Quote Link to comment
JonathanM Posted February 21, 2021 Share Posted February 21, 2021 12 minutes ago, henk1122 said: If you create a file which fits on the cache on creation time, but then grows, the cache can run out of space. That's not good. How do you think this situation should be handled? Quote Link to comment
henk1122 Posted February 27, 2021 Author Share Posted February 27, 2021 (edited) On 2/21/2021 at 9:03 PM, jonathanm said: How do you think this situation should be handled? Say I've this configuration: share1 - cache type: "only" - 50GB share2 - cache type "yes" - 100GB share3 - cache type "prefer" - 400GB If share3 is writing a file, and it grows near the limit to the disk, I would expect Unraid is going to move files from share2 cache to the array. Why? Because it has lower priority then "prefer". If share2 files are moved, and the cache still hits the limits, then I would guess the oldest files from share3 would be moved from cache to the array. At this moment the cache is kinda useless; it's about use as little as possible and let your SSD space be wasted. Given you have not a lot of data on your "only" cache shares. Edited February 27, 2021 by henk1122 Quote Link to comment
JonathanM Posted February 27, 2021 Share Posted February 27, 2021 3 hours ago, henk1122 said: Say I've this configuration: share1 - cache type: "only" - 50GB share2 - cache type "yes" - 100GB share3 - cache type "prefer" - 400GB If share3 is writing a file, and it grows near the limit to the disk, I would expect Unraid is going to move files from share2 cache to the array. Why? Because it has lower priority then "prefer". If share2 files are moved, and the cache still hits the limits, then I would guess the oldest files from share3 would be moved from cache to the array. The mover tuning plugin can be set to do what you ask. 3 hours ago, henk1122 said: At this moment the cache is kinda useless; it's about use as little as possible and let your SSD space be wasted. Many people are using lower grade SSD drives that wear out quickly when kept full and constantly active. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.