Well in the 1st run it does warn you that something odd happened:
WARNING: PROGRAMMING BUG IN E2FSCK!
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[23300069] is 2, inode.i_links_count is 1. They should be the same!
Inode 23300069 ref count is 1, should be 1. Fix? yes
so I think after that warning all bets are off - and I can see from your df -h that your /dev/sdg1 isn't mounted,
so it does look like an e2fsck bug it got to that point.
Can I ask what did you do to your fs to get it into this state where the fsck started off with those
errors and can you describe the hardware.
Well in the 1st run it does warn you that something odd happened:
WARNING: PROGRAMMING BUG IN E2FSCK! info[23300069] is 2, inode.i_links_count is 1. They should be the same!
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_
Inode 23300069 ref count is 1, should be 1. Fix? yes
so I think after that warning all bets are off - and I can see from your df -h that your /dev/sdg1 isn't mounted,
so it does look like an e2fsck bug it got to that point.
Can I ask what did you do to your fs to get it into this state where the fsck started off with those
errors and can you describe the hardware.
Dave