Public bug reported:
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
** Affects: e2fsprogs (Ubuntu)
Importance: Undecided
Status: New
--
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
