Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

2016-09-25 Thread Michael Biebl
Am 25.09.2016 um 18:58 schrieb Julien Cristau: > On Sun, Sep 25, 2016 at 17:06:56 +0200, Michael Biebl wrote: >> Does this affect 4.7.2-1 as well, i.e. the current version in testing? > > The current version in testing is 4.6.4-1. Indeed. Somehow I was fooled by

Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

2016-09-25 Thread Julien Cristau
On Sun, Sep 25, 2016 at 17:06:56 +0200, Michael Biebl wrote: > On Thu, 22 Sep 2016 07:51:36 +0200 Stefan Fritsch wrote: > > Package: src:linux > > Version: 4.7.4-2 > > Severity: grave > > Justification: renders package unusable > > > > When booting with

Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

2016-09-25 Thread Michael Biebl
On Thu, 22 Sep 2016 07:51:36 +0200 Stefan Fritsch wrote: > Package: src:linux > Version: 4.7.4-2 > Severity: grave > Justification: renders package unusable > > When booting with linux-image-4.7.0-1-amd64 4.7.4-2, one of my > filesystems fails to mount with: > >

Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

2016-09-21 Thread Stefan Fritsch
Package: src:linux Version: 4.7.4-2 Severity: grave Justification: renders package unusable When booting with linux-image-4.7.0-1-amd64 4.7.4-2, one of my filesystems fails to mount with: ext4_iget:4476: inode #8: comm mount: checksum invalid A fsck does not find any errors, though, and the