Hi folks.
Yesterday I updated kernel to 5.2 (git commit 7e9890a3500d)
I always leave computer working at night.
Today at morning I am found that computer are hanged.
I was connect via ssh and look at kernel log.
There I had seen strange records which I never seen before:
[28616.429757] EXT4-fs error (device nvme0n1p2): ext4_find_extent:908:
inode #8: comm jbd2/nvme0n1p2-: pblk 23101439 bad header/extent:
invalid extent entries - magic f30a, entries 8, max 340(340), depth
0(0)
[28616.430602] jbd2_journal_bmap: journal block not found at offset
4383 on nvme0n1p2-8
[28616.430610] Aborting journal on device nvme0n1p2-8.
[28616.432474] EXT4-fs error (device nvme0n1p2):
ext4_journal_check_start:61: Detected aborted journal
[28616.432489] EXT4-fs error (device nvme0n1p2):
ext4_journal_check_start:61: Detected aborted journal
[28616.432551] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
[28616.432690] EXT4-fs (nvme0n1p2): ext4_writepages: jbd2_start:
9223372036854775791 pages, ino 3285789; err -30
[28616.432692] EXT4-fs error (device nvme0n1p2):
ext4_journal_check_start:61: Detected aborted journal
After reboot computer and running fsck system looks like working.
But I am afraid that it could happens again and I may lost all my data.
How safe this error and what does it mean?
It a bug of kernel 5.2 or not?
--
Best Regards,
Mike Gavrilov.
Excerpts from Mikhail Gavrilov's message of May 18, 2019 7:07 am:
> On Sat, 18 May 2019 at 11:44, Mikhail Gavrilov
> <[email protected]> wrote:
>> [28616.429757] EXT4-fs error (device nvme0n1p2): ext4_find_extent:908:
>> inode #8: comm jbd2/nvme0n1p2-: pblk 23101439 bad header/extent:
>> invalid extent entries - magic f30a, entries 8, max 340(340), depth
>> 0(0)
I had a similar problem today:
EXT4-fs error (device dm-0): ext4_find_extent:908: inode #8: comm jbd2/dm-0-8: pblk 117997567 bad header/extent: invalid extent entries - magic f30a, entries 8, max 340(340), depth 0(0)
I am using dm-crypt on SATA disk.
On Sat, 18 May 2019 at 16:07, Mikhail Gavrilov
<[email protected]> wrote:
>
> It happens today again.
>
> [18018.969636] EXT4-fs error (device nvme0n1p2): ext4_find_extent:908:
> inode #8: comm jbd2/nvme0n1p2-: pblk 23101439 bad header/extent:
> invalid extent entries - magic f30a, entries 8, max 340(340), depth
> 0(0)
> [18018.970071] jbd2_journal_bmap: journal block not found at offset
> 4799 on nvme0n1p2-8
> [18018.970076] Aborting journal on device nvme0n1p2-8.
> [18018.970269] EXT4-fs error (device nvme0n1p2):
> ext4_journal_check_start:61: Detected aborted journal
> [18018.970316] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
>
I am bisected issue. I hope it help understand what is happened on my computer.
$ git bisect log
git bisect start
# good: [e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd] Linux 5.1
git bisect good e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd
# bad: [7e9890a3500d95c01511a4c45b7e7192dfa47ae2] Merge tag
'ovl-update-5.2' of
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs
git bisect bad 7e9890a3500d95c01511a4c45b7e7192dfa47ae2
# good: [80f232121b69cc69a31ccb2b38c1665d770b0710] Merge
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next
git bisect good 80f232121b69cc69a31ccb2b38c1665d770b0710
# good: [a2d635decbfa9c1e4ae15cb05b68b2559f7f827c] Merge tag
'drm-next-2019-05-09' of git://anongit.freedesktop.org/drm/drm
git bisect good a2d635decbfa9c1e4ae15cb05b68b2559f7f827c
# good: [ea5aee6d97fd2d4499b1eebc233861c1def70f06] Merge tag
'clk-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
git bisect good ea5aee6d97fd2d4499b1eebc233861c1def70f06
# good: [47782361aca21a32ad4198f1b72f1655a7c9f7e5] Merge tag
'tag-chrome-platform-for-v5.2' of
ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux
git bisect good 47782361aca21a32ad4198f1b72f1655a7c9f7e5
# bad: [55472bae5331f33582d9f0e8919fed8bebcda0da] Merge tag
'linux-watchdog-5.2-rc1' of
git://http://www.linux-watchdog.org/linux-watchdog
git bisect bad 55472bae5331f33582d9f0e8919fed8bebcda0da
# good: [4dbf09fea60d158e60a30c419e0cfa1ea138dd57] Merge tag
'mtd/for-5.2' of
ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/mtd/linux
git bisect good 4dbf09fea60d158e60a30c419e0cfa1ea138dd57
# good: [44affc086e6d5ea868c1184cdc5e1159e90ffb71] watchdog:
ts4800_wdt: Convert to use device managed functions and other
improvements
git bisect good 44affc086e6d5ea868c1184cdc5e1159e90ffb71
# good: [5c09980d9f9de2dc6b255f4f0229aeff0eb2c723] watchdog:
imx_sc_wdt: drop warning after calling watchdog_init_timeout
git bisect good 5c09980d9f9de2dc6b255f4f0229aeff0eb2c723
# good: [345f16251063bcef5828f17fe90aa7f7a5019aab] watchdog: Improve
Kconfig entry ordering and dependencies
git bisect good 345f16251063bcef5828f17fe90aa7f7a5019aab
# good: [988bec41318f3fa897e2f8af271bd456936d6caf] ubifs: orphan:
Handle xattrs like files
git bisect good 988bec41318f3fa897e2f8af271bd456936d6caf
# good: [a65d10f3ce657aa4542b5de78933053f6d1a9e97] ubifs: Drop
unnecessary setting of zbr->znode
git bisect good a65d10f3ce657aa4542b5de78933053f6d1a9e97
# good: [a9f0bda567e32a2b44165b067adfc4a4f56d1815] watchdog: Enforce
that at least one pretimeout governor is enabled
git bisect good a9f0bda567e32a2b44165b067adfc4a4f56d1815
# bad: [d7a02fa0a8f9ec1b81d57628ca9834563208ef33] Merge tag
'upstream-5.2-rc1' of
ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/rw/ubifs
git bisect bad d7a02fa0a8f9ec1b81d57628ca9834563208ef33
# good: [04d37e5a8b1fad2d625727af3d738c6fd9491720] ubi: wl: Fix
uninitialized variable
git bisect good 04d37e5a8b1fad2d625727af3d738c6fd9491720
# first bad commit: [d7a02fa0a8f9ec1b81d57628ca9834563208ef33] Merge
tag 'upstream-5.2-rc1' of
ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/rw/ubifs
--
Best Regards,
Mike Gavrilov.
On Mon, 27 May 2019 at 21:16, Mikhail Gavrilov
<[email protected]> wrote:
>
> I am bisected issue. I hope it help understand what is happened on my computer.
>
> $ git bisect log
> git bisect start
> # good: [e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd] Linux 5.1
> git bisect good e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd
> # bad: [7e9890a3500d95c01511a4c45b7e7192dfa47ae2] Merge tag
> 'ovl-update-5.2' of
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs
> git bisect bad 7e9890a3500d95c01511a4c45b7e7192dfa47ae2
> # good: [80f232121b69cc69a31ccb2b38c1665d770b0710] Merge
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next
> git bisect good 80f232121b69cc69a31ccb2b38c1665d770b0710
> # good: [a2d635decbfa9c1e4ae15cb05b68b2559f7f827c] Merge tag
> 'drm-next-2019-05-09' of git://anongit.freedesktop.org/drm/drm
> git bisect good a2d635decbfa9c1e4ae15cb05b68b2559f7f827c
> # good: [ea5aee6d97fd2d4499b1eebc233861c1def70f06] Merge tag
> 'clk-for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
> git bisect good ea5aee6d97fd2d4499b1eebc233861c1def70f06
> # good: [47782361aca21a32ad4198f1b72f1655a7c9f7e5] Merge tag
> 'tag-chrome-platform-for-v5.2' of
> ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux
> git bisect good 47782361aca21a32ad4198f1b72f1655a7c9f7e5
> # bad: [55472bae5331f33582d9f0e8919fed8bebcda0da] Merge tag
> 'linux-watchdog-5.2-rc1' of
> git://http://www.linux-watchdog.org/linux-watchdog
> git bisect bad 55472bae5331f33582d9f0e8919fed8bebcda0da
> # good: [4dbf09fea60d158e60a30c419e0cfa1ea138dd57] Merge tag
> 'mtd/for-5.2' of
> ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/mtd/linux
> git bisect good 4dbf09fea60d158e60a30c419e0cfa1ea138dd57
> # good: [44affc086e6d5ea868c1184cdc5e1159e90ffb71] watchdog:
> ts4800_wdt: Convert to use device managed functions and other
> improvements
> git bisect good 44affc086e6d5ea868c1184cdc5e1159e90ffb71
> # good: [5c09980d9f9de2dc6b255f4f0229aeff0eb2c723] watchdog:
> imx_sc_wdt: drop warning after calling watchdog_init_timeout
> git bisect good 5c09980d9f9de2dc6b255f4f0229aeff0eb2c723
> # good: [345f16251063bcef5828f17fe90aa7f7a5019aab] watchdog: Improve
> Kconfig entry ordering and dependencies
> git bisect good 345f16251063bcef5828f17fe90aa7f7a5019aab
> # good: [988bec41318f3fa897e2f8af271bd456936d6caf] ubifs: orphan:
> Handle xattrs like files
> git bisect good 988bec41318f3fa897e2f8af271bd456936d6caf
> # good: [a65d10f3ce657aa4542b5de78933053f6d1a9e97] ubifs: Drop
> unnecessary setting of zbr->znode
> git bisect good a65d10f3ce657aa4542b5de78933053f6d1a9e97
> # good: [a9f0bda567e32a2b44165b067adfc4a4f56d1815] watchdog: Enforce
> that at least one pretimeout governor is enabled
> git bisect good a9f0bda567e32a2b44165b067adfc4a4f56d1815
> # bad: [d7a02fa0a8f9ec1b81d57628ca9834563208ef33] Merge tag
> 'upstream-5.2-rc1' of
> ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/rw/ubifs
> git bisect bad d7a02fa0a8f9ec1b81d57628ca9834563208ef33
> # good: [04d37e5a8b1fad2d625727af3d738c6fd9491720] ubi: wl: Fix
> uninitialized variable
> git bisect good 04d37e5a8b1fad2d625727af3d738c6fd9491720
> # first bad commit: [d7a02fa0a8f9ec1b81d57628ca9834563208ef33] Merge
> tag 'upstream-5.2-rc1' of
> ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/rw/ubifs
>
Why no one answers?
Even if the problem is known and already fixed, I would be nice to
know that I spent 10 days for searching a problem commit not in vain
and someone reads my messages.
--
Best Regards,
Mike Gavrilov.
On Tue, May 28, 2019 at 10:58:03AM +0500, Mikhail Gavrilov wrote:
> On Mon, 27 May 2019 at 21:16, Mikhail Gavrilov
> <[email protected]> wrote:
> >
> > I am bisected issue. I hope it help understand what is happened on my computer.
> >
>
> Why no one answers?
> Even if the problem is known and already fixed, I would be nice to
> know that I spent 10 days for searching a problem commit not in vain
> and someone reads my messages.
Sorry, I didn't see your earlier messages; I'm not sure why. In any
case, yes, it's a known issue, and it's fixed in 5.2-rc2. This fix
was commit 0a944e8a6c66.
- Ted