Index: programs/fsck-tests/small-disk/fsck.ocfs2.13.stdout
===================================================================
--- programs/fsck-tests/small-disk/fsck.ocfs2.13.stdout	(revision 182)
+++ programs/fsck-tests/small-disk/fsck.ocfs2.13.stdout	(working copy)
@@ -12,16 +12,20 @@ Pass 0a: Checking cluster allocation cha
 Pass 0b: Checking inode allocation chains
 Pass 0c: Checking extent block allocation chains
 Pass 1: Checking inodes and blocks.
-[EB_BLKNO] An extent block at 19345 in inode 16883 claims to be located at block 19346.  Update the extent block's location? y
-[EB_GEN] An extent block at 19347 in inode 16884 has a generation of 1234 which doesn't match the volume's generation of ebcd726c.  Consider this extent block invalid? y
-[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16884 refers to an invalid extent block at 19347.  Clear the reference to this invalid block? y
+[EB_BLKNO] An extent block at 19348 in inode 16883 claims to be located at block 19349.  Update the extent block's location? y
+[INODE_SIZE] Inode 16883 has a size of 0 but has 408 blocks of actual data. Correct the file size? y
+[EB_GEN] An extent block at 19350 in inode 16884 has a generation of 1234 which doesn't match the volume's generation of 11a8ef45.  Consider this extent block invalid? y
+[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16884 refers to an invalid extent block at 19350.  Clear the reference to this invalid block? y
 [EXTENT_BLKNO_RANGE] Extent record 0 in inode 16884 refers to a block that is out of range.  Remove this record from the extent list? y
-[EB_GEN] An extent block at 19349 in inode 16885 has a generation of 1234 which doesn't match the volume's generation of ebcd726c.  Consider this extent block invalid? y
-[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16885 refers to an invalid extent block at 19349.  Clear the reference to this invalid block? y
+[INODE_SIZE] Inode 16884 has a size of 0 but has 408 blocks of actual data. Correct the file size? y
+[EB_GEN] An extent block at 19352 in inode 16885 has a generation of 1234 which doesn't match the volume's generation of 11a8ef45.  Consider this extent block invalid? y
+[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16885 refers to an invalid extent block at 19352.  Clear the reference to this invalid block? y
 [EXTENT_BLKNO_RANGE] Extent record 0 in inode 16885 refers to a block that is out of range.  Remove this record from the extent list? y
-[EB_GEN] An extent block at 19351 in inode 16886 has a generation of 1234 which doesn't match the volume's generation of ebcd726c.  Consider this extent block invalid? y
-[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16886 refers to an invalid extent block at 19351.  Clear the reference to this invalid block? y
+[INODE_SIZE] Inode 16885 has a size of 0 but has 408 blocks of actual data. Correct the file size? y
+[EB_GEN] An extent block at 19354 in inode 16886 has a generation of 1234 which doesn't match the volume's generation of 11a8ef45.  Consider this extent block invalid? y
+[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16886 refers to an invalid extent block at 19354.  Clear the reference to this invalid block? y
 [EXTENT_BLKNO_RANGE] Extent record 0 in inode 16886 refers to a block that is out of range.  Remove this record from the extent list? y
+[INODE_SIZE] Inode 16886 has a size of 0 but has 408 blocks of actual data. Correct the file size? y
 [CLUSTER_ALLOC_BIT] Cluster 5390 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 5391 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 5392 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
Index: programs/fsck-tests/small-disk/fsck.ocfs2.23.stdout
===================================================================
--- programs/fsck-tests/small-disk/fsck.ocfs2.23.stdout	(revision 182)
+++ programs/fsck-tests/small-disk/fsck.ocfs2.23.stdout	(working copy)
@@ -1,24 +1,15 @@
 Checking OCFS2 filesystem in @DEVICE@:
   label:              <NONE>
   uuid:               bf f2 14 d7 c1 06 41 04 88 30 72 b1 a5 a8 ad 1b 
-  number of blocks:   185344
+  number of blocks:   262144
   bytes per block:    1024
-  number of clusters: 46336
+  number of clusters: 65536
   bytes per cluster:  4096
   max slots:          4
 
 @DEVICE@ was run with -f, check forced.
 Pass 0a: Checking cluster allocation chains
-[CHAIN_HEAD_LINK_RANGE] Chain 7 in allocator inode 15 contains an initial block reference to 215040 which is out of range.  Clear this reference? y
-[CHAIN_HEAD_LINK_RANGE] Chain 8 in allocator inode 15 contains an initial block reference to 245760 which is out of range.  Clear this reference? y
-[CHAIN_BITS] Chain 7 in allocator inode 15 has 7679 bits marked free out of 7680 total bits but the block groups in the chain have 0 free out of 0 total.  Fix this by updating the chain record? y
-[CHAIN_EMPTY] Chain 7 in allocator inode 15 is empty.  Remove it from the chain record array in the inode and shift further chains into its place? y
-[CHAIN_BITS] Chain 7 in allocator inode 15 has 4095 bits marked free out of 4096 total bits but the block groups in the chain have 0 free out of 0 total.  Fix this by updating the chain record? y
-[CHAIN_EMPTY] Chain 7 in allocator inode 15 is empty.  Remove it from the chain record array in the inode and shift further chains into its place? y
-[CHAIN_GROUP_BITS] Allocator inode 15 has 4741 bits marked used out of 65536 total bits but the chains have 4739 used out of 53760 total.  Fix this by updating the inode counts? y
-[CHAIN_I_CLUSTERS] Allocator inode 15 has 53760 clusters represented in its allocator chains but has an i_clusters value of 65536. Fix this by updating i_clusters? y
-[CHAIN_I_SIZE] Allocator inode 15 has 53760 clusters represented in its allocator chain which accounts for 220200960 total bytes, but its i_size is 268435456. Fix this by updating i_size? y
-[SUPERBLOCK_CLUSTERS] Superblock has clusters set to 46336 instead of 53760. Fix? y
+[SUPERBLOCK_CLUSTERS] Superblock has clusters set to 46336 instead of 65536 recorded in global_bitmap, it may be caused by an unsuccessful resize. Trust global_bitmap? y
 Pass 0b: Checking inode allocation chains
 Pass 0c: Checking extent block allocation chains
 Pass 1: Checking inodes and blocks.
Index: programs/fsck-tests/small-disk/fsck.ocfs2.15.stdout
===================================================================
--- programs/fsck-tests/small-disk/fsck.ocfs2.15.stdout	(revision 182)
+++ programs/fsck-tests/small-disk/fsck.ocfs2.15.stdout	(working copy)
@@ -13,8 +13,10 @@ Pass 0b: Checking inode allocation chain
 Pass 0c: Checking extent block allocation chains
 Pass 1: Checking inodes and blocks.
 [EXTENT_BLKNO_UNALIGNED] The extent record for cluster offset 0 in inode 16883 refers to block 18937 which isn't aligned with the start of a cluster.  Point the extent record at block 18936 which starts this cluster? y
+[INODE_SIZE] Inode 16883 has a size of 0 but has 4 blocks of actual data. Correct the file size? y
 [EXTENT_BLKNO_RANGE] Extent record 0 in inode 16884 refers to a block that is out of range.  Remove this record from the extent list? y
-[EXTENT_CLUSTERS_OVERRUN] The extent record for cluster offset 0 in inode 16885 refers to an extent that goes beyond the end of the volume.  Truncate the extent by 65536 clusters to fit it in the volume? y
+[EXTENT_CLUSTERS_OVERRUN] The extent record for cluster offset 0 in inode 16885 refers to an extent that goes beyond the end of the volume.  Truncate the extent by 1 clusters to fit it in the volume? y
+[INODE_SIZE] Inode 16885 has a size of 0 but has 4 blocks of actual data. Correct the file size? y
 [CLUSTER_ALLOC_BIT] Cluster 4735 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 4736 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 65535 is in use but isn't set in the global cluster bitmap. Set its bit in the bitmap? y
Index: programs/fsck-tests/small-disk/fsck.ocfs2.27.stdout
===================================================================
--- programs/fsck-tests/small-disk/fsck.ocfs2.27.stdout	(revision 182)
+++ programs/fsck-tests/small-disk/fsck.ocfs2.27.stdout	(working copy)
@@ -16,11 +16,11 @@ Pass 1: Checking inodes and blocks.
 [INODE_BLKNO] Inode read from block 16885 has i_blkno set to 16985.  Set the inode's i_blkno value to reflect its location on disk? y
 [INODE_NZ_DTIME] Inode 16886 is in use but has a non-zero dtime. Reset the dtime to 0? y
 [INODE_SUBALLOC] Inode 16887 indicates that it was allocated from slot 10 but slot 0's chain allocator covers the inode.  Fix the inode's record of where it is allocated? y
-[INODE_SIZE] Inode 16888 has a size of 100 but has 0 bytes of actual data. Correct the file size? y
-[INODE_CLUSTERS] Inode 16889 has 0 clusters but its blocks fit in 10 clusters.  Correct the number of clusters? y
+[INODE_SIZE] Inode 16889 has a size of 0 but has 40 blocks of actual data. Correct the file size? y
+[INODE_CLUSTERS] Inode 16889 has 0 clusters but its blocks fit in 10 clusters. Correct the number of clusters? y
 Pass 2: Checking directory entries.
-[DIRENT_INODE_FREE] Directory entry 'test5ZeqRh' refers to inode number 16883 which isn't allocated, clear the entry? y
-[DIRENT_INODE_FREE] Directory entry 'testZcUGa4' refers to inode number 16884 which isn't allocated, clear the entry? y
+[DIRENT_INODE_FREE] Directory entry 'testLZbWGi' refers to inode number 16883 which isn't allocated, clear the entry? y
+[DIRENT_INODE_FREE] Directory entry 'testMwFzlJ' refers to inode number 16884 which isn't allocated, clear the entry? y
 Pass 3: Checking directory connectivity.
 Pass 4a: checking for orphaned inodes
 Pass 4b: Checking inodes link counts.
Index: programs/fsck-tests/small-disk/fsck.ocfs2.22.stdout
===================================================================
--- programs/fsck-tests/small-disk/fsck.ocfs2.22.stdout	(revision 182)
+++ programs/fsck-tests/small-disk/fsck.ocfs2.22.stdout	(working copy)
@@ -1,18 +1,15 @@
 Checking OCFS2 filesystem in @DEVICE@:
   label:              <NONE>
   uuid:               bf f2 14 d7 c1 06 41 04 88 30 72 b1 a5 a8 ad 1b 
-  number of blocks:   338944
+  number of blocks:   262144
   bytes per block:    1024
-  number of clusters: 84736
+  number of clusters: 65536
   bytes per cluster:  4096
   max slots:          4
 
 @DEVICE@ was run with -f, check forced.
 Pass 0a: Checking cluster allocation chains
-[GROUP_EXPECTED_DESC] Block 276480 should be a group descriptor for the bitmap chain allocator but it wasn't found in any chains.  Reinitialize it as a group desc and link it into the bitmap allocator? y
-[GROUP_EXPECTED_DESC] Block 307200 should be a group descriptor for the bitmap chain allocator but it wasn't found in any chains.  Reinitialize it as a group desc and link it into the bitmap allocator? y
-[GROUP_EXPECTED_DESC] Block 337920 should be a group descriptor for the bitmap chain allocator but it wasn't found in any chains.  Reinitialize it as a group desc and link it into the bitmap allocator? y
-[SUPERBLOCK_CLUSTERS] Superblock has clusters set to 84736 instead of 81152. Fix? y
+[SUPERBLOCK_CLUSTERS] Superblock has clusters set to 84736 instead of 65536 recorded in global_bitmap, it may be caused by an unsuccessful resize. Trust global_bitmap? y
 Pass 0b: Checking inode allocation chains
 Pass 0c: Checking extent block allocation chains
 Pass 1: Checking inodes and blocks.
Index: programs/fsck-tests/small-disk/fsck.ocfs2.14.stdout
===================================================================
--- programs/fsck-tests/small-disk/fsck.ocfs2.14.stdout	(revision 182)
+++ programs/fsck-tests/small-disk/fsck.ocfs2.14.stdout	(working copy)
@@ -13,8 +13,11 @@ Pass 0b: Checking inode allocation chain
 Pass 0c: Checking extent block allocation chains
 Pass 1: Checking inodes and blocks.
 [EXTENT_LIST_DEPTH] Extent list in inode 16883 is recorded as being at depth 1 but we expect it to be at depth 0. update the list? y
+[INODE_SIZE] Inode 16883 has a size of 0 but has 408 blocks of actual data. Correct the file size? y
 [EXTENT_LIST_COUNT] Extent list in inode 16884 claims to have 120 records, but the maximum is 60. Fix the list's count? y
+[INODE_SIZE] Inode 16884 has a size of 0 but has 408 blocks of actual data. Correct the file size? y
 [EXTENT_LIST_FREE] Extent list in inode 16885 claims 120 as the next free chain record, but fsck believes the largest valid value is 60.  Clamp the next record value? y
+[INODE_SIZE] Inode 16885 has a size of 0 but has 408 blocks of actual data. Correct the file size? y
 Pass 2: Checking directory entries.
 Pass 3: Checking directory connectivity.
 Pass 4a: checking for orphaned inodes
Index: programs/fsck-tests/small-disk/fsck.ocfs2.36.stdout
===================================================================
--- programs/fsck-tests/small-disk/fsck.ocfs2.36.stdout	(revision 182)
+++ programs/fsck-tests/small-disk/fsck.ocfs2.36.stdout	(working copy)
@@ -15,7 +15,7 @@ Pass 1: Checking inodes and blocks.
 [LINK_NULLTERM] The target of symlink inode 16884 isn't null terminated.  Clear the inode? y
 [INODE_ALLOC_REPAIR] Inode 16884 is marked as invalid but its position in the inode allocator is marked as in use.  Fix the allocation of this and all future inodes? y
 [LINK_SIZE] The target of symlink inode 16885 is 16 bytes long on disk, but i_size is 26 bytes long.  Update i_size to reflect the length on disk? y
-[INODE_CLUSTERS] Inode 16886 has 1 clusters but its blocks fit in 2 clusters.  Correct the number of clusters? y
+[INODE_CLUSTERS] Inode 16886 has 1 clusters but its blocks fit in 2 clusters. Correct the number of clusters? y
 [CLUSTER_ALLOC_BIT] Cluster 4734 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 4735 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 4738 is in use but isn't set in the global cluster bitmap. Set its bit in the bitmap? y
Index: programs/fsck-tests/medium-disk/fsck.ocfs2.13.stdout
===================================================================
--- programs/fsck-tests/medium-disk/fsck.ocfs2.13.stdout	(revision 182)
+++ programs/fsck-tests/medium-disk/fsck.ocfs2.13.stdout	(working copy)
@@ -12,16 +12,20 @@ Pass 0a: Checking cluster allocation cha
 Pass 0b: Checking inode allocation chains
 Pass 0c: Checking extent block allocation chains
 Pass 1: Checking inodes and blocks.
-[EB_BLKNO] An extent block at 18367 in inode 16857 claims to be located at block 18368.  Update the extent block's location? y
-[EB_GEN] An extent block at 18369 in inode 16858 has a generation of 1234 which doesn't match the volume's generation of ebc02395.  Consider this extent block invalid? y
-[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16858 refers to an invalid extent block at 18369.  Clear the reference to this invalid block? y
+[EB_BLKNO] An extent block at 18370 in inode 16857 claims to be located at block 18371.  Update the extent block's location? y
+[INODE_SIZE] Inode 16857 has a size of 0 but has 486 blocks of actual data. Correct the file size? y
+[EB_GEN] An extent block at 18372 in inode 16858 has a generation of 1234 which doesn't match the volume's generation of 8ff99d46.  Consider this extent block invalid? y
+[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16858 refers to an invalid extent block at 18372.  Clear the reference to this invalid block? y
 [EXTENT_BLKNO_RANGE] Extent record 0 in inode 16858 refers to a block that is out of range.  Remove this record from the extent list? y
-[EB_GEN] An extent block at 18371 in inode 16859 has a generation of 1234 which doesn't match the volume's generation of ebc02395.  Consider this extent block invalid? y
-[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16859 refers to an invalid extent block at 18371.  Clear the reference to this invalid block? y
+[INODE_SIZE] Inode 16858 has a size of 0 but has 486 blocks of actual data. Correct the file size? y
+[EB_GEN] An extent block at 18374 in inode 16859 has a generation of 1234 which doesn't match the volume's generation of 8ff99d46.  Consider this extent block invalid? y
+[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16859 refers to an invalid extent block at 18374.  Clear the reference to this invalid block? y
 [EXTENT_BLKNO_RANGE] Extent record 0 in inode 16859 refers to a block that is out of range.  Remove this record from the extent list? y
-[EB_GEN] An extent block at 18373 in inode 16860 has a generation of 1234 which doesn't match the volume's generation of ebc02395.  Consider this extent block invalid? y
-[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16860 refers to an invalid extent block at 18373.  Clear the reference to this invalid block? y
+[INODE_SIZE] Inode 16859 has a size of 0 but has 486 blocks of actual data. Correct the file size? y
+[EB_GEN] An extent block at 18376 in inode 16860 has a generation of 1234 which doesn't match the volume's generation of 8ff99d46.  Consider this extent block invalid? y
+[EXTENT_EB_INVALID] The extent record for cluster offset 0 in inode 16860 refers to an invalid extent block at 18376.  Clear the reference to this invalid block? y
 [EXTENT_BLKNO_RANGE] Extent record 0 in inode 16860 refers to a block that is out of range.  Remove this record from the extent list? y
+[INODE_SIZE] Inode 16860 has a size of 0 but has 486 blocks of actual data. Correct the file size? y
 [CLUSTER_ALLOC_BIT] Cluster 19624 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 19625 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 19626 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
Index: programs/fsck-tests/medium-disk/fsck.ocfs2.23.stdout
===================================================================
--- programs/fsck-tests/medium-disk/fsck.ocfs2.23.stdout	(revision 182)
+++ programs/fsck-tests/medium-disk/fsck.ocfs2.23.stdout	(working copy)
@@ -1,24 +1,15 @@
 Checking OCFS2 filesystem in @DEVICE@:
   label:              <NONE>
   uuid:               bf f2 14 d7 c1 06 41 04 88 30 72 b1 a5 a8 ad 1b
-  number of blocks:   967936
+  number of blocks:   1048576
   bytes per block:    4096
-  number of clusters: 967936
+  number of clusters: 1048576
   bytes per cluster:  4096
   max slots:          4
 
 @DEVICE@ was run with -f, check forced.
 Pass 0a: Checking cluster allocation chains
-[CHAIN_HEAD_LINK_RANGE] Chain 31 in allocator inode 11 contains an initial block reference to 999936 which is out of range.  Clear this reference? y
-[CHAIN_HEAD_LINK_RANGE] Chain 32 in allocator inode 11 contains an initial block reference to 1032192 which is out of range.  Clear this reference? y
-[CHAIN_BITS] Chain 31 in allocator inode 11 has 32255 bits marked free out of 32256 total bits but the block groups in the chain have 0 free out of 0 total.  Fix this by updating the chain record? y
-[CHAIN_EMPTY] Chain 31 in allocator inode 11 is empty.  Remove it from the chain record array in the inode and shift further chains into its place? y
-[CHAIN_BITS] Chain 31 in allocator inode 11 has 16383 bits marked free out of 16384 total bits but the block groups in the chain have 0 free out of 0 total.  Fix this by updating the chain record? y
-[CHAIN_EMPTY] Chain 31 in allocator inode 11 is empty.  Remove it from the chain record array in the inode and shift further chains into its place? y
-[CHAIN_GROUP_BITS] Allocator inode 11 has 17911 bits marked used out of 1048576 total bits but the chains have 17909 used out of 999936 total.  Fix this by updating the inode counts? y
-[CHAIN_I_CLUSTERS] Allocator inode 11 has 999936 clusters represented in its allocator chains but has an i_clusters value of 1048576. Fix this by updating i_clusters? y
-[CHAIN_I_SIZE] Allocator inode 11 has 999936 clusters represented in its allocator chain which accounts for 4095737856 total bytes, but its i_size is 4294967296. Fix this by updating i_size? y
-[SUPERBLOCK_CLUSTERS] Superblock has clusters set to 967936 instead of 999936. Fix? y
+[SUPERBLOCK_CLUSTERS] Superblock has clusters set to 967936 instead of 1048576 recorded in global_bitmap, it may be caused by an unsuccessful resize. Trust global_bitmap? y
 Pass 0b: Checking inode allocation chains
 Pass 0c: Checking extent block allocation chains
 Pass 1: Checking inodes and blocks.
Index: programs/fsck-tests/medium-disk/fsck.ocfs2.15.stdout
===================================================================
--- programs/fsck-tests/medium-disk/fsck.ocfs2.15.stdout	(revision 182)
+++ programs/fsck-tests/medium-disk/fsck.ocfs2.15.stdout	(working copy)
@@ -12,8 +12,10 @@ Pass 0a: Checking cluster allocation cha
 Pass 0b: Checking inode allocation chains
 Pass 0c: Checking extent block allocation chains
 Pass 1: Checking inodes and blocks.
+[INODE_SIZE] Inode 16857 has a size of 0 but has 1 blocks of actual data. Correct the file size? y
 [EXTENT_BLKNO_RANGE] Extent record 0 in inode 16858 refers to a block that is out of range.  Remove this record from the extent list? y
-[EXTENT_CLUSTERS_OVERRUN] The extent record for cluster offset 0 in inode 16859 refers to an extent that goes beyond the end of the volume.  Truncate the extent by 1048576 clusters to fit it in the volume? y
+[EXTENT_CLUSTERS_OVERRUN] The extent record for cluster offset 0 in inode 16859 refers to an extent that goes beyond the end of the volume.  Truncate the extent by 1 clusters to fit it in the volume? y
+[INODE_SIZE] Inode 16859 has a size of 0 but has 1 blocks of actual data. Correct the file size? y
 [CLUSTER_ALLOC_BIT] Cluster 17880 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 17882 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 1048575 is in use but isn't set in the global cluster bitmap. Set its bit in the bitmap? y
Index: programs/fsck-tests/medium-disk/fsck.ocfs2.27.stdout
===================================================================
--- programs/fsck-tests/medium-disk/fsck.ocfs2.27.stdout	(revision 182)
+++ programs/fsck-tests/medium-disk/fsck.ocfs2.27.stdout	(working copy)
@@ -16,11 +16,11 @@ Pass 1: Checking inodes and blocks.
 [INODE_BLKNO] Inode read from block 16859 has i_blkno set to 16959.  Set the inode's i_blkno value to reflect its location on disk? y
 [INODE_NZ_DTIME] Inode 16860 is in use but has a non-zero dtime. Reset the dtime to 0? y
 [INODE_SUBALLOC] Inode 16861 indicates that it was allocated from slot 10 but slot 0's chain allocator covers the inode.  Fix the inode's record of where it is allocated? y
-[INODE_SIZE] Inode 16862 has a size of 100 but has 0 bytes of actual data. Correct the file size? y
-[INODE_CLUSTERS] Inode 16863 has 0 clusters but its blocks fit in 10 clusters.  Correct the number of clusters? y
+[INODE_SIZE] Inode 16863 has a size of 0 but has 10 blocks of actual data. Correct the file size? y
+[INODE_CLUSTERS] Inode 16863 has 0 clusters but its blocks fit in 10 clusters. Correct the number of clusters? y
 Pass 2: Checking directory entries.
-[DIRENT_INODE_FREE] Directory entry 'testYJ7LXp' refers to inode number 16857 which isn't allocated, clear the entry? y
-[DIRENT_INODE_FREE] Directory entry 'testEWPHr7' refers to inode number 16858 which isn't allocated, clear the entry? y
+[DIRENT_INODE_FREE] Directory entry 'test8OegdF' refers to inode number 16857 which isn't allocated, clear the entry? y
+[DIRENT_INODE_FREE] Directory entry 'testNswzDu' refers to inode number 16858 which isn't allocated, clear the entry? y
 Pass 3: Checking directory connectivity.
 Pass 4a: checking for orphaned inodes
 Pass 4b: Checking inodes link counts.
Index: programs/fsck-tests/medium-disk/fsck.ocfs2.22.stdout
===================================================================
--- programs/fsck-tests/medium-disk/fsck.ocfs2.22.stdout	(revision 182)
+++ programs/fsck-tests/medium-disk/fsck.ocfs2.22.stdout	(working copy)
@@ -1,18 +1,15 @@
 Checking OCFS2 filesystem in @DEVICE@:
   label:              <NONE>
   uuid:               bf f2 14 d7 c1 06 41 04 88 30 72 b1 a5 a8 ad 1b
-  number of blocks:   1129216
+  number of blocks:   1048576
   bytes per block:    4096
-  number of clusters: 1129216
+  number of clusters: 1048576
   bytes per cluster:  4096
   max slots:          4
 
 @DEVICE@ was run with -f, check forced.
 Pass 0a: Checking cluster allocation chains
-[GROUP_EXPECTED_DESC] Block 1064448 should be a group descriptor for the bitmap chain allocator but it wasn't found in any chains.  Reinitialize it as a group desc and link it into the bitmap allocator? y
-[GROUP_EXPECTED_DESC] Block 1096704 should be a group descriptor for the bitmap chain allocator but it wasn't found in any chains.  Reinitialize it as a group desc and link it into the bitmap allocator? y
-[GROUP_EXPECTED_DESC] Block 1128960 should be a group descriptor for the bitmap chain allocator but it wasn't found in any chains.  Reinitialize it as a group desc and link it into the bitmap allocator? y
-[SUPERBLOCK_CLUSTERS] Superblock has clusters set to 1129216 instead of 1113344. Fix? y
+[SUPERBLOCK_CLUSTERS] Superblock has clusters set to 1129216 instead of 1048576 recorded in global_bitmap, it may be caused by an unsuccessful resize. Trust global_bitmap? y
 Pass 0b: Checking inode allocation chains
 Pass 0c: Checking extent block allocation chains
 Pass 1: Checking inodes and blocks.
Index: programs/fsck-tests/medium-disk/fsck.ocfs2.14.stdout
===================================================================
--- programs/fsck-tests/medium-disk/fsck.ocfs2.14.stdout	(revision 182)
+++ programs/fsck-tests/medium-disk/fsck.ocfs2.14.stdout	(working copy)
@@ -13,8 +13,11 @@ Pass 0b: Checking inode allocation chain
 Pass 0c: Checking extent block allocation chains
 Pass 1: Checking inodes and blocks.
 [EXTENT_LIST_DEPTH] Extent list in inode 16857 is recorded as being at depth 1 but we expect it to be at depth 0. update the list? y
+[INODE_SIZE] Inode 16857 has a size of 0 but has 486 blocks of actual data. Correct the file size? y
 [EXTENT_LIST_COUNT] Extent list in inode 16858 claims to have 504 records, but the maximum is 252. Fix the list's count? y
+[INODE_SIZE] Inode 16858 has a size of 0 but has 486 blocks of actual data. Correct the file size? y
 [EXTENT_LIST_FREE] Extent list in inode 16859 claims 504 as the next free chain record, but fsck believes the largest valid value is 252.  Clamp the next record value? y
+[INODE_SIZE] Inode 16859 has a size of 0 but has 486 blocks of actual data. Correct the file size? y
 Pass 2: Checking directory entries.
 Pass 3: Checking directory connectivity.
 Pass 4a: checking for orphaned inodes
Index: programs/fsck-tests/medium-disk/fsck.ocfs2.36.stdout
===================================================================
--- programs/fsck-tests/medium-disk/fsck.ocfs2.36.stdout	(revision 182)
+++ programs/fsck-tests/medium-disk/fsck.ocfs2.36.stdout	(working copy)
@@ -15,7 +15,7 @@ Pass 1: Checking inodes and blocks.
 [LINK_NULLTERM] The target of symlink inode 16858 isn't null terminated.  Clear the inode? y
 [INODE_ALLOC_REPAIR] Inode 16858 is marked as invalid but its position in the inode allocator is marked as in use.  Fix the allocation of this and all future inodes? y
 [LINK_SIZE] The target of symlink inode 16859 is 16 bytes long on disk, but i_size is 26 bytes long.  Update i_size to reflect the length on disk? y
-[INODE_CLUSTERS] Inode 16860 has 1 clusters but its blocks fit in 2 clusters.  Correct the number of clusters? y
+[INODE_CLUSTERS] Inode 16860 has 1 clusters but its blocks fit in 2 clusters. Correct the number of clusters? y
 [CLUSTER_ALLOC_BIT] Cluster 17880 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 17881 is marked in the global cluster bitmap but it isn't in use.  Clear its bit in the bitmap? y
 [CLUSTER_ALLOC_BIT] Cluster 17884 is in use but isn't set in the global cluster bitmap. Set its bit in the bitmap? y
Index: programs/fsck-tests/fsck-test.sh
===================================================================
--- programs/fsck-tests/fsck-test.sh	(revision 182)
+++ programs/fsck-tests/fsck-test.sh	(working copy)
@@ -415,12 +415,21 @@ function corrupt_test()
 		<"$BASE_DIR/workfiles/fsck-test/${disk_size}-disk/fsck.ocfs2.$corrupt.stdout" \
 		>"$TMP_DIR/fsck.ocfs2.$corrupt.expect.stdout" 2>/dev/null
 
+	if [ $corrupt = 22 -o $corrupt = 23 ]; then
+	diff -u -I "  uuid:              \( [0-9a-f][0-9a-f]\)\{16\}" \
+		-I "  number of blocks:   [0-9]\+" \
+	        -I "  number of clusters: [0-9]\+" \
+		"$TMP_DIR/fsck.ocfs2.$corrupt.expect.stdout" \
+		"$TMP_DIR/fsck.ocfs2.$corrupt.actual.stdout" \
+		>"$STDOUT" &>"$STDOUT"
+	else
 	diff -u -I "  uuid:              \( [0-9a-f][0-9a-f]\)\{16\}" \
 		-I "\[DIRENT_INODE_FREE\] Directory entry 'test[0-9A-Za-z]\{6\}' refers to inode number [0-9]\+ which isn't allocated, clear the entry? y" \
-		-I "\[EB_GEN\] An extent block at [0-9]\+ in inode [0-9]\+ has a generation of 1234 which doesn't match the volume's generation of [0-9a-f]\{8}.  Consider this extent block invalid? y" \
+		-I "\[EB_GEN\] An extent block at [0-9]\+ in inode [0-9]\+ has a generation of 1234 which doesn't match the volume's generation of [0-9a-f]\{8\}.  Consider this extent block invalid? y" \
 		"$TMP_DIR/fsck.ocfs2.$corrupt.expect.stdout" \
 		"$TMP_DIR/fsck.ocfs2.$corrupt.actual.stdout" \
 		>"$STDOUT" &>"$STDOUT"
+	fi
 	test_fail_if_bad "$?" "fsck output differ with the expect one" || return
 
 	test_info "verifying"
