nicopolous

Hi forum, hopefully there's a simple answer to this Say I have a pool (with pool file duplication x2), with a set of drives of sizes that mean I have some space that is "unusable for duplication" (I completely understand the reason for this, with a bunch of mismatched drive sizes). If I fill the pool so I have (e.g.) 85% full with duplicated files and the remaining 15% is unusable for duplication - what happens when I write to the drive? I am fairly sure it's smart enough to write the file, but since can't duplicate it I get some kind of warning that it's not fully duplicated. Or will it simply report the virtual pool disk is full? Extending this scenario slightly: Say I have a pool with 2x 1TB drives and 1x 2TB drive, with pool file duplication 2x and the pool is full. If one of the 1TB drives goes bad and I have to remove it, will the pool keep functioning, just reporting that I have 1TB of unduplicated files on the pool? Thanks v much :)

Thanks, you're right, those options would work - probably the SSD optimiser would be better. The problem with option (1) is that files will *sometimes* be on that drive and, more importantly, I will also need to change the balancing ratio trigger to something like 99-100%. All this combined will mean a lot of files moving around which I would like to avoid. Can someone please confirm whether the "drive usage limiter" should be real-time? The little red arrow on that drive suggests to me that it should be. Thanks again!

Hi. I have a pool with one drive with a limit via the "drive usage limiter" balancer to not place any un-duplicated files on it. However, un-duplicated files ARE being placed on it, then moved out during balancing runs. I thought that the limit was a real-time limit, so no files should be placed on it in the first place. I'm sure I'm missing something, any help would be appreciated! Thanks

I have a drive that's unreliable in my pool, so I've used the Drive Usage Limiter balancer to allow only duplicated files on that drive. I've got the balancers in the following order: 1) StableBit Scanner 2) Drive Usage Limiter 3) Duplication Space Optimizer 4) Prevent Drive Overfill The suspect drive is almost empty and the other drives have significant amounts of duplicate files on. I was expecting the balancing run to move a lot of duplicate files to the one marked for duplication only, so it frees up maximum free space on the pool and maximises the duplication space. However, it doesn't and leaves the suspect "duplication" drive almost empty. There isn't much space available on the remaining drives and so although I've got a reported 8TB of free space, if I try and copy a 1TB file to the pool, it reports I don't have enough free space (as there isn't enough free space on any of the individual drives - except the one for duplication only and I'm copying the 1TB file to a folder with no duplication on it, so can't copy to that drive). Screenshots attached that show what I'm talking about. Any help appreciated!