Date: Sat, 15 Jan 2022 16:56:10 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 261181] 13-STABLE hang: swap_pager: indefinite wait buffer Message-ID: <bug-261181-227-vDXv6DR7FS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261181-227@https.bugs.freebsd.org/bugzilla/> References: <bug-261181-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=3D261181 --- Comment #14 from ldoujin <lnx.doujin@gmail.com> --- (In reply to tech-lists from comment #12) /tmp is on the same geli-encrypted array as the rest of the OS. A few more data points: - Cloning new tree from https =3D no bug - Cloning new tree from ssh =3D no bug - Updating tree from ssh =3D bug The ports directory is mounted with zstd compression, while /tmp is mounted with no compression. I tried switching the ports directory to lz4 and no compression, but the bug still happened with git pull in both cases. As I understand it, ZFS may still actually be using the previous compression for reading existing files, so "disabling" it might not have fully disabled= it. Either way, the compression is probably worth mentioning. I don't want to delete the problematic tree yet because then the bug may not get found and fixed. Something is still broken that's provably not broken i= n a kernel from September. (In reply to Andriy Gapon from comment #13) I'm not familiar with vmstat, but here is its -z output on a fresh boot: https://pastebin.com/raw/6xRwdmbw And during the rapid wired memory inflation: https://pastebin.com/raw/x0KiiP2A --=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-261181-227-vDXv6DR7FS>