Comment 1 for bug 1637779

after failure fsck shows this:

fsck from util-linux 2.28.2
e2fsck 1.43.3 (04-Sep-2016)
/dev/sdb5: recovering journal
Superblock last mount time is in the future.
 (by less than a day, probably due to the hardware clock being incorrectly set)
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 131127 was part of the orphaned inode list. FIXED.
Deleted inode 143474 has zero dtime. Fix<y>? yes
Inode 792889 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 787060 ref count is 1, should be 2. Fix<y>? yes
Pass 5: Checking group summary information
Block bitmap differences: -(104256--104319) -(1258816--1259263) -(1802240--1802548) -(3430933--3430934)
Fix<y>? yes
Free blocks count wrong for group #3 (13156, counted=13220).
Fix<y>? yes
Free blocks count wrong for group #38 (12870, counted=13318).
Fix<y>? yes
Free blocks count wrong for group #55 (29651, counted=29960).
Fix<y>? yes
Free blocks count wrong for group #104 (19316, counted=19318).
Fix<y>? yes
Free blocks count wrong (2230417, counted=2231421).
Fix<y>? yes
Inode bitmap differences: -131127 -143474 -792889
Fix ('a' enables 'yes' to all) <y>? yes to all
Free inodes count wrong (763160, counted=763233).
Fix? yes

/dev/sdb5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb5: ***** REBOOT SYSTEM *****
/dev/sdb5: 219807/983040 files (0.1% non-contiguous), 1700739/3932160 blocks