Date: Mon, 01 Apr 2019 14:01:04 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 236220] ZFS vnode deadlock on zfs_mknode Message-ID: <bug-236220-3630-h8rtgzsYUq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236220-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-236220-3630@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=3D236220 Julien Cigar <julien@perdition.city> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |julien@perdition.city --- Comment #14 from Julien Cigar <julien@perdition.city> --- I'm also experimenting something similar on 12.0-RELEASE + ZFS, also running PostgreSQL 11 (in jail, with nullfs mounts). I've seen this on two machines. The first one is a small HPE Proliant Microserver Gen 8 with 16GB RAM. It started when I upgraded from 10.3 to 12.0, so I don't know if 11.x is affec= ted too. As OP, sometimes I can remote SSH, sometimes not, and a simple ls almo= st always hangs. A shutdown -r now hangs too after syncing buffers. For some unknow reason the problem didn't occured again (3 months now) since I forced ARC_MAX to 8GB (vfs.zfs.arc_max=3D8589934592). The second one is an HPE Proliant DL160Gen9 with 64GB of RAM (freshly insta= lled 12.0-RELEASE). Symptoms are the same as above, with ARC_MAX set to 24GB (vfs.zfs.arc_max=3D25769803776). (I'll try to procstat -kk -a next time) --=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-236220-3630-h8rtgzsYUq>