1.42-WIP (02-Jul-2011)
Pass 1: Checking inodes, blocks, and sizes
Error allocating block bitmap (4): Memory allocation failed
fsck is some kind of messy with memory. Increasing the memory to 8 GB did it. While running fsck i noticed a memory consumption of up to 3.4 GB! So large file systems require a lot of memory for fscking. It requires even more memory with more inodes!
resize2fs
After fscking my file system i tried to resize it:
[root@localhost sbin]# lvresize -l +7199 /dev/iscsi/test
Extending logical volume test to 50.00 TB
Logical volume test successfully resized
[root@localhost sbin]# resize2fs /dev/iscsi/test
resize2fs 1.42-WIP (02-Jul-2011)
resize2fs: New size too large to be expressed in 32 bits
As you can see resizing the file system is not yet supported/implemented. So it would be wise to create the file system with the final size from start since growing is NOT possible!
tune2fs
tune2fs seems to work – at least it dumps the suberblock contents:
[root@localhost sbin]# tune2fs -l /dev/iscsi/test
tune2fs 1.42-WIP (02-Jul-2011)
Filesystem volume name: <none>
Last mounted on: /mnt/mnt
Filesystem UUID: a754e947-8b89-415d-909d-000e6c95c44a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 6550000
Block count: 13414400000
Reserved block count: 670720000
Free blocks: 13394134177
Free inodes: 1484526
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1024
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16
Inode blocks per group: 1
Flex block group size: 16
Filesystem created: Wed Oct 19 17:09:06 2011
Last mount time: