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.
