Re: [bugreport] kernel 5.2 pblk bad header/extent: invalid extent entries

2019-05-28 Thread Theodore Ts'o
On Tue, May 28, 2019 at 10:58:03AM +0500, Mikhail Gavrilov wrote: > On Mon, 27 May 2019 at 21:16, Mikhail Gavrilov > 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

Re: [bugreport] kernel 5.2 pblk bad header/extent: invalid extent entries

2019-05-27 Thread Mikhail Gavrilov
On Mon, 27 May 2019 at 21:16, Mikhail Gavrilov 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

Re: [bugreport] kernel 5.2 pblk bad header/extent: invalid extent entries

2019-05-27 Thread Mikhail Gavrilov
On Sat, 18 May 2019 at 16:07, Mikhail Gavrilov 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 >

Re: [bugreport] kernel 5.2 pblk bad header/extent: invalid extent entries

2019-05-18 Thread Alex Xu (Hello71)
Excerpts from Mikhail Gavrilov's message of May 18, 2019 7:07 am: > On Sat, 18 May 2019 at 11:44, Mikhail Gavrilov > 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 -

[bugreport] kernel 5.2 pblk bad header/extent: invalid extent entries

2019-05-18 Thread Mikhail Gavrilov
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