When an application creates a file, there is no indication of the pending size of the file (well there are times when an application can pre-allocate a size, but this is not common). The problem here is that Drive Bender can only create a file on a single drive, it cannot split files across multiple drives. When not using a landing zone, Drive Bender picks the target drive based on free space, so generally the drive with the most free space is used (it is a little more complicated than that, but generally this is how it works). With an landing zone, the size of the file will always be limited to the free space on the landing zone drive.
Articles in this section
- How can I view the log files generated by Drive Bender?
- One of my pooled drives is flagged as RAW in Disk Manager, why?
- How do I update the Drive Bender service?
- Uninstalling Drive Bender fails with an error, how do I uninstall?
- What should I check before removing a drive from a pool?
- Why do I get a storage full error when using a landing zone and coping large files to the pool?
- What is CRC validation, and should I be using it?
- Windows has write protected my pool, how can I fix this?
- How do I send large files to support?
- How can I fix a drive marked as "Read Only"?