The testresize.sh script repeatedly grows and shrinks (unmounted) filesystems
in small increments.  The amount that the filesystem is grown or shrunk is
random.  The maximum filesystem size is the device size, and the minimum size
is 4096 blocks (4MB for a 1k filesystem and 16MB for a 4k filesystem).

This is a good way to test that ext2resize and ext2online can properly resize
filesystems with a variety of pre and post sizes.  However, it is not 100%
assurance that there are no problems with resizing because there are many
cases that are not tested which depend on initial filesystem creation
parameters, maximum size, etc.

Use testresize.sh on TEST filesystems ONLY.  It should not do anything bad to
a filesystem (if no bugs exist in the code...) but it doesn't really do
anything useful for you other than verifying that the code is mostly working.

If you do encounter a bug with testresize.sh, please send the output from
e2fsck -fn <device> (in e2fsck.log), dumpe2fs <device> (dumpe2fs.log), and
any testresize.sh output (in testresize.log, from the previous few resizes
before the error, at least) to:

ext2resize-devel@lists.sourceforge.net

Usage of testresize.sh is fairly simple:

./testresize.sh <device> [optional max size]

Use at your own risk.

Cheers, Andreas
