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
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1637779
Title:
ext4 filesystem fails randomly with checksum error
Status in e2fsprogs package in Ubuntu:
New
Bug description:
Description: Ubuntu 16.10
Release: 16.10
package version:
linux-image-4.8.0-26-generic:
Installed: 4.8.0-26.28
Candidate: 4.8.0-26.28
Version table:
*** 4.8.0-26.28 500
500 http://sk.archive.ubuntu.com/ubuntu yakkety-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu yakkety-security/main amd64
Packages
100 /var/lib/dpkg/status
fresh installation of Ubunut 16.10, all updates included
While I am working with system after few minutes root filesystem /dev/sdb5
switches into readonly mode
in dmesg is this:
[ 304.921552] EXT4-fs error (device sdb5): ext4_iget:4476: inode #24577:
comm updatedb.mlocat: checksum invalid
[ 304.925565] Aborting journal on device sdb5-8.
[ 304.926507] EXT4-fs (sdb5): Remounting filesystem read-only
[ 304.927416] EXT4-fs error (device sdb5): ext4_journal_check_start:56:
Detected aborted journal
[ 304.943408] EXT4-fs error (device sda1): ext4_iget:4476: inode #12: comm
updatedb.mlocat: checksum invalid
when it happens I must do fsck f /dev/sdb1 once, second time it says
everything is fine. after reboot when I start dto do something it soon
happens again
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
