Date: Sun, 03 Feb 2019 13:57:47 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 235439] sync(8) hanged in D+ state after more swap space was added Message-ID: <bug-235439-227-4UqKCtyjJA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235439-227@https.bugs.freebsd.org/bugzilla/> References: <bug-235439-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235439 --- Comment #2 from Yuri Victorovich <yuri@freebsd.org> --- (In reply to Andriy Gapon from comment #1) > What was a filesystem for that swap file? The newly added swap file is on zfs. The previously existed swap file is on ufs. > $ procstat -kk 40832 > PID TID COMM TDNAME KSTACK=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 > 40832 101728 sync - mi_switch+0xe6 sleep= q_wait+0x2c _cv_wait+0x16e txg_wait_synced+0xa5 dmu_tx_assign+0x48 zil_comm= it_impl+0x8e zfs_sync+0xa6 sys_sync+0x116 amd64_syscall+0xa38 fast_syscall_= common+0x101=20 > $ procstat -kk 88582 > PID TID COMM TDNAME KSTACK=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 > 88582 103868 sync - mi_switch+0xe6 sleep= q_wait+0x2c _cv_wait+0x16e txg_wait_synced+0xa5 dmu_tx_assign+0x48 zil_comm= it_impl+0x8e zfs_sync+0xa6 sys_sync+0x116 amd64_syscall+0xa38 fast_syscall_= common+0x101 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235439-227-4UqKCtyjJA>