Deaddy

I came back full of GB! I tried to disable the plugin Ordered File Placement and moving a 700GB file, I have no error, is automatically written to the hard disk with enough space.

Yes, a 970GB file image to another hd. To be honest I was expecting this approach to DP plugin: 970GB to write > check free space on disc 2 > is not enough > write the file on hd 3. Otherwise a nearly full disk with any file size happens the same error (eg: set limiter to 50 GB free, missing 55GB to fill, I try to write a 60GB file, disk full error). But I realize they are special circumstances, I only wanted to see if I had configured incorrectly something or was it a "problem" of DP.

Unfortunately, the disk that contained the file from 970GB left me forever , for now it is impossible to repeat the event. But then I tried to lower the limiter and copy a 54GB file and has done without errors, DP ignoring the limiter because there was enough space on the disk. Once finished it correctly set the limiter of disk E: to 0% and lifted the new limiter of disk F: At this point it seems that the limits are considered only when reached, but DP is not able to prevent in advance that are exceeded. When will I receive the new disk I recreate the 970GB file and submit the log.

For the workaround I had thought but I wanted to find a definitive solution in case it happens again in the future. DP so it is not able to read the size of the file to write and evaluate the free space of the disks for a correct placement? I hope it's just a problem of the plugin and can be fixed!

Hi all, first of all an overview of my situation: Win 2012 R2, folders in the pool shared on the local network and I don't have enabled file duplication because using Snapraid. My problem: if I try to copy a 970GB file in any folder of the pool Windows says is not enough space, but showing 2.45TB free! Drivepool should not automatically move the file to VOL03 (F:\) since it is empty? Sorry for my BAD English