Comment 9 for bug 455024

Resize2fs needs to keep track of which blocks need to be relocated, and which inode its associated with (so it can update the block reference after we copy the block from the portion of the file system that is going to be gone after we finish with the shrink operation).

I am sure that e2fsprogs still has room to improve. However, I'm not going to accept patches which make things worse for the most common configurations, which are typically (a) small amounts of memory, and small amounts of storage (i.e., a Android device with 512MB to 4GB of memory, and generally 8-32GB of flash; Linode or Amazon EC3 VM's will be roughly the same, but they will have much slower emulated HDD's instead of flash), or (b) an enterprise server with 8GB to 64GB with 4-12TB of disks. Patches which make things better for your configuration, but do not make things worse for these much more common configuration (and which don't break e2fsprogs's built in regression test suite) will be gratefully accepted.