https://bugzilla.kernel.org/show_bug.cgi?id=207053 --- Comment #1 from Dave Chinner (david@xxxxxxxxxxxxx) --- On Wed, Apr 01, 2020 at 07:02:57PM +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > When we upgraded from kernel 4.14.146 to kernel 4.19.75, we began to > experience > frequent deadlocks from our cronjobs that freeze the filesystem for > snapshotting. Probably commit d6b636ebb1c9 ("xfs: halt auto-reclamation activities while rebuilding rmap") in 4.18, but that fixes a bug that allowed reaping functions to attempt to modify the filesystem while it was frozen... > The fsfreeze stack shows: > # cat /proc/33256/stack > [<0>] __flush_work+0x177/0x1b0 > [<0>] __cancel_work_timer+0x12b/0x1b0 > [<0>] xfs_stop_block_reaping+0x15/0x30 [xfs] > [<0>] xfs_fs_freeze+0x15/0x40 [xfs] > [<0>] freeze_super+0xc8/0x190 > [<0>] do_vfs_ioctl+0x510/0x630 > [<0>] ksys_ioctl+0x70/0x80 > [<0>] __x64_sys_ioctl+0x16/0x20 > [<0>] do_syscall_64+0x4e/0x100 > [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 This indicates that the reaping worker is still busy doing work. It needs to finish before the freeze will continue to make progress. So either the system is still doing work, or the kworker has blocked somewhere. What is the dmesg output of 'echo w > /prox/sysrq-trigger'? Cheers, Dave. -- You are receiving this mail because: You are watching the assignee of the bug.
