e2fsprogs/tests/m_mkfs_overhead/script

DESCRIPTION="test bg overhead calculation"
FS_SIZE=1024
MKE2FS_OPTS="-b 1024 -m 0 -g 256 -N 3745"
. $cmd_dir/run_mke2fs
Properly calculate overhead in ext2fs_initialize() For some odd geometries, mkfs will try to allocate inode tables off the end of the block group and fail, rather than warning that too many inodes have been requested. This is because when ext2fs_initialize calculates metadata overhead, it is only adding in group descriptor blocks and the superblock if the last* bg contains them - but the first bg also has all of the various metadata bits taking up space. We need to calculate the overhead both for the first block group and the last block groups separately, since the two different tests need to know what the overheads are for those two cases, which may be different. *for example "mke2fs -b 1024 -m 0 -g 256 -N 3745 fsfile 1024" (Note, the test here is a little funky; the expected output is actually a mkfs failure - but a proper failure instead of the allocator catching the problem at the last minute) Addresses-Red-Hat-Bugzilla: #241767 Signed-off-by: Eric Sandeen <sandeen@redhat.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 2007-07-22 23:07:13 +04:00			`DESCRIPTION="test bg overhead calculation"`
			`FS_SIZE=1024`
			`MKE2FS_OPTS="-b 1024 -m 0 -g 256 -N 3745"`
			`. $cmd_dir/run_mke2fs`