How to Manipulate File Sizes Using the truncate Command in Linux

When you are provisioning virtual machines or creating complex disk quotas on a Linux server, you frequently need to instantly generate massive, perfectly sized “dummy” files to test the system (e.g., verifying that a user is successfully blocked from exceeding a 10-Gigabyte storage limit). Instead of using chaotic commands like dd to physically write 10 Gigabytes of useless zeros to the hard drive (which wastes time and physically degrades SSD platters), you should use the truncate command to manipulate the file size instantly without actually writing data.

How the truncate Command Works

The truncate command allows you to explicitly command the Linux file system to assign a highly specific physical file size to a document. It interacts directly with the file allocation table, manipulating the metadata of the file rather than the contents.

To instantly generate a brand new, empty file that the operating system mathematically believes is exactly 5 Gigabytes in size, use the -s (size) flag:

truncate -s 5G test_quota_file.bin

The command executes in exactly zero milliseconds. It does not actually write 5 Gigabytes of zeros to the disk; it creates a “sparse file.” If you run ls -lh test_quota_file.bin, the system will report the file is 5.0G. This instantly triggers all necessary quota alerts, allowing you to test your infrastructure without burning IOPS.

Shrinking Massive Log Files

The truncate command is not just for creating fake files; it is a critical administrative tool for violently shrinking live log files.

Imagine your /var/log/syslog file has exploded to 50 Gigabytes and has completely filled the /var/ partition, crashing the server. If you use the standard rm command to delete the file, the active daemon currently writing to the log will hold the file handle open, meaning the disk space will not actually be freed until you restart the server.

Instead of deleting the file, you can instantly shrink it down to zero bytes while leaving the active file handle completely intact:

truncate -s 0 /var/log/syslog

The kernel instantly rips the 50 Gigabytes of data out from underneath the running application and permanently deletes it, instantly recovering the storage space without crashing the daemon.

Extending Existing Files

You can also use the + or - operators to adjust an existing file’s size relative to its current state.

If you have an existing 100MB file and you want to mathematically extend it by exactly 500 Megabytes, run:

truncate -s +500M existing_file.dat

The system instantly appends 500 Megabytes of empty void to the absolute end of the file, increasing its total footprint to 600MB.