id summary reporter owner description type status priority milestone component version severity resolution keywords cc 6750 gdalwarp falsely claims it doesn't have enough disk space (32 bit Linux) kwaters warmerdam "When running gdalwarp I get a message that there isn't enough space, but there is. Oddly, changing the destination file name changes the behavior. The failure looks like this (there are 3.2 Tb free on the disk): gdalwarp -of GTiff ./testdem_1_10_2_11.tif ./testdem_1_10_2_01.tif ./testdem_1_10_2_00.tif ./testdem_1_10_2_10.tif ./testdem_1_10.tif Creating output file that is 18923P x 14430L. ERROR 3: Free disk space available is 323878912 bytes, whereas 1092235560 are at least necessary. However, if I change the name of the output file slightly, it works, as in the following: gdalwarp -of GTiff ./testdem_1_10_2_11.tif ./testdem_1_10_2_01.tif ./testdem_1_10_2_00.tif ./testdem_1_10_2_10.tif ./testdem_1_10_nocomp.tif Those input files are floating point DEMs. A tarball of the files is at ftp://coast.noaa.gov/temp/kwaters/dems.tgz. Adding compression as a creation option gets me around this, but also makes the output file about 3 times bigger with LZW alone or 1.8 times bigger with PREDICTOR=3. Running this on a 32-bit RHEL machine." defect closed normal 2.1.3 Utilities 2.1.1 normal fixed gdalwarp