LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org
Subject: [bugreport] kernel 5.2 pblk bad header/extent: invalid extent entries
Date: Sat, 18 May 2019 11:44:28 +0500	[thread overview]
Message-ID: <CABXGCsNPMSQgBjnFarYaxuQEGpA1G=U4U9OHqT0E53pNL2BK8g@mail.gmail.com> (raw)

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.

             reply	other threads:[~2019-05-18  6:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-18  6:44 Mikhail Gavrilov [this message]
2019-05-18 11:07 ` Mikhail Gavrilov
2019-05-18 18:59   ` Alex Xu (Hello71)
2019-05-27 16:16   ` Mikhail Gavrilov
2019-05-28  5:58     ` Mikhail Gavrilov
2019-05-28 13:23       ` Theodore Ts'o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABXGCsNPMSQgBjnFarYaxuQEGpA1G=U4U9OHqT0E53pNL2BK8g@mail.gmail.com' \
    --to=mikhail.v.gavrilov@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [bugreport] kernel 5.2 pblk bad header/extent: invalid extent entries' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).