July 25, 20187 yr I'm sure this has been brought up several times but I just cannot find the answer to solve this mystery. I have a user share called Videos that states it has 2.49TB free and I also see the same amount of space in Windows when mapped as a drive. However applications trying to write to that share fail saying insufficient space. All drives are allowed to be used for the share except disk 9. Share is set to Fill-Up with 0kb min. free space and automatic split level. unraid-diagnostics-20180725-1206.zip
July 25, 20187 yr Community Expert 1 minute ago, cleight said: with 0kb min. free space This is the problem, min free space should be set at twice the largest file you expect to copy.
July 25, 20187 yr Author 18 minutes ago, johnnie.black said: This is the problem, min free space should be set at twice the largest file you expect to copy. I had it set to 25GB and things stopped working, I read somewhere on the forums that someone set it to 0kb and things started working again. I just set it back to above 25GB and still not working.
July 25, 20187 yr Community Expert Everything else looks OK, there a few out of memory errors on your syslog, so reboot and try again, you should also take the opportunity to update to latest release. Also and unrelated, disk9 is failing and needs to be replaced ASAP.
July 25, 20187 yr Community Expert 2 hours ago, cleight said: I read somewhere on the forums that someone set it to 0kb 0 Minimum Free combined with Fill Up will always result in out of space. unRAID has no way to know how large a file will become when it chooses a disk to write it to. If a disk has more than Minimum Free space, it can choose the disk for writing the file, and if the file is larger than the free space you get an error.
July 25, 20187 yr 11 minutes ago, trurl said: unRAID has no way to know how large a file will become when it chooses a disk to write it to. Some copy programs will directly after having created a new file do a preallocation request. If unRAID could wait with creating the zero-sized file until it receives one of - file close - file data - preallocation request then unRAID could make a much better job figuring out a suitable disk for all the situations where a preallocation request is made. The purpose with the preallocation request is to avoid issues with fragmentation - and to let the copy program know that there will be room for all the file data. unRAID must obviously still perform the required access rights checking to make sure that the file open fails if the user would not have the right to create the file.
Archived
This topic is now archived and is closed to further replies.