You are not logged in.
I cannot seem to remove the reserved GDT blocks from my root partition. I used the following command:
# tune2fs -O ^resize_inode /dev/sda2and `tune2fs -l /dev/sda3` shows:
Filesystem volume name: ROOT
Last mounted on: /
Filesystem UUID: 3257b590-798b-4a2f-a17c-43d3e2c42dbe
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr dir_index filetype needs_recovery extent 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: 294912
Block count: 1179392
Reserved block count: 0
Free blocks: 681743
Free inodes: 232461
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 287
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Wed Apr 25 01:31:07 2012
Last mount time: Mon May 21 17:27:34 2012
Last write time: Thu May 17 17:55:49 2012
Mount count: 208
Maximum mount count: -1
Last checked: Wed Apr 25 01:31:07 2012
Check interval: 0 (<none>)
Lifetime writes: 15 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 7def6bd7-8328-4cb5-82d6-9ac30c4ea89e
Journal backup: inode blocksAs you can see, resize_inode is no longer a filesystem feature, but the reserved GDT blocks are still 287, same as before I removed the resize_inode feature. On the other hand, the same command on my home partition removed the reserved GDT blocks immediately, with no issues. For comparison, here is the information on my home partition:
Filesystem volume name: HOME
Last mounted on: /home
Filesystem UUID: 74aa6e15-11b9-4634-926c-7b2c7a1bd4f5
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr dir_index filetype needs_recovery extent 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: 7004160
Block count: 27994225
Reserved block count: 0
Free blocks: 10860999
Free inodes: 6990555
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Wed Apr 25 01:31:14 2012
Last mount time: Mon May 21 17:27:34 2012
Last write time: Mon May 21 17:27:34 2012
Mount count: 27
Maximum mount count: -1
Last checked: Thu May 17 17:37:00 2012
Check interval: 0 (<none>)
Lifetime writes: 147 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: f4a7a378-a974-4e11-98f8-35739bc79ac4
Journal backup: inode blocksThese are my only partitions by the way, besides my UEFISYS partition. I would really appreciate it if someone could offer some advice. Thanks in advance.
Last edited by Sara (2012-05-22 03:35:13)
Registed Linux User 483618
Offline