Re: A collection of btrfs lockup stack traces (4.14.107, kcompactd and two processes running __lock_page)

2019-03-27 Thread Zygo Blaxell
On Tue, Mar 26, 2019 at 10:37:06PM -0400, Zygo Blaxell wrote: > On Tue, Mar 19, 2019 at 11:39:59PM -0400, Zygo Blaxell wrote: > > I haven't been able to easily reproduce these in a test environment; > > however, they have been happening several times a year on servers in > > production. > > > > Ke

Re: A collection of btrfs lockup stack traces (4.14.106, no __sb_start_write)

2019-03-26 Thread Zygo Blaxell
On Tue, Mar 19, 2019 at 11:39:59PM -0400, Zygo Blaxell wrote: > I haven't been able to easily reproduce these in a test environment; > however, they have been happening several times a year on servers in > production. > > Kernel: most recent observation on 4.14.105 + cherry-picked deadlock > and

Re: A collection of btrfs lockup stack traces (4.20.13)

2019-03-19 Thread Zygo Blaxell
On Tue, Mar 19, 2019 at 11:39:59PM -0400, Zygo Blaxell wrote: > I haven't been able to easily reproduce these in a test environment; > however, they have been happening several times a year on servers in > production. > > Kernel: most recent observation on 4.14.105 + cherry-picked deadlock > and

Re: A collection of btrfs lockup stack traces

2019-03-19 Thread Zygo Blaxell
On Tue, Mar 19, 2019 at 11:39:59PM -0400, Zygo Blaxell wrote: > I haven't been able to easily reproduce these in a test environment; > however, they have been happening several times a year on servers in > production. > > Kernel: most recent observation on 4.14.105 + cherry-picked deadlock > and

A collection of btrfs lockup stack traces

2019-03-19 Thread Zygo Blaxell
I haven't been able to easily reproduce these in a test environment; however, they have been happening several times a year on servers in production. Kernel: most recent observation on 4.14.105 + cherry-picked deadlock and misc hang fixes: btrfs: wakeup cleaner thread when adding delayed