Sparse files are simple enough. A file can report a large logical size while using very little physical disk space until data gets written into it. I use them for large placeholders, test images, or emergency swap when I do not want to burn disk up front. They separate apparent size from actual usage, which is handy and dangerous in equal measure.
Under the hood, a sparse file contains holes. The filesystem keeps track of ranges that have not been written and does not allocate blocks for them. You see the difference straight away when you compare ls and du. ls -lh big.img shows the apparent size, while du -h big.img shows the space actually used. To make a sparse file on Linux, use truncate -s 10G big.img or dd if=/dev/zero of=big.img bs=1 count=0 seek=10G.
For a swap file, a sparse placeholder works like this:
truncate -s 4G /swapfile && chmod 600 /swapfile && mkswap /swapfile && swapon /swapfileOnce the kernel has mapped the swap file, you cannot grow it live after swapon without disabling it and recreating it.
I use sparse files for VM disk images when I expect little initial write activity, for test suites that need a large file without the storage cost, and as a temporary emergency swap image when disk is tight. They also help with thin provisioning for local experiments and with staging large backups that will be filled later.
Be careful when moving files between filesystems or across protocols. Some copy operations expand holes into real blocks. Use cp --sparse=always or rsync -S to preserve sparsity; use tar --sparse for archives. If you send a sparse file over NFS or to a filesystem that does not support holes, expect it to use the full apparent size on the destination.
There are a few gotchas. If a sparse file fills up while it is live, the host can run out of disk space with very little warning. Monitor actual usage with du. When you need guaranteed allocation, use a real preallocated file instead. Some tools behave differently: fallocate often reserves blocks rather than creating holes, while truncate creates holes without touching blocks. If you are unsure whether a file has holes, check stat --format='%n %b %B' file to compare allocated blocks to file size, or use filefrag -v file to inspect extents.
If you use sparse files, keep the rules simple. Create them with truncate or dd when you want holes. Check ls and du before and after writing. Preserve sparsity with cp --sparse=always, rsync -S or tar --sparse. Do not put critical data on a sparse file where allocation guarantees matter. For swap files, treat the sparse approach as temporary or emergency use and be ready to recreate the file if you need to change its size while it is active.
