Date: Sun, 28 Apr 2019 19:35:52 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 236220] ZFS vnode deadlock on zfs_mknode Message-ID: <bug-236220-3630-zHq3rICdbz@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 Dennis Noordsij <dennis.noordsij@alumni.helsinki.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dennis.noordsij@alumni.hels | |inki.fi --- Comment #20 from Dennis Noordsij <dennis.noordsij@alumni.helsinki.fi> -= -- As an extra datapoint, I've noticed this exact same problem after upgrading= to 12.0-RELEASE in combination with PostgreSQL 11.2 At first I blamed AWS EBS volume hiccups for the stuck-on-access symptoms, = but now outside of AWS (KVM based VPS with NAS) I am running into the same prob= lem. Basic system, a UFS boot partition and a ZFS pool with a root dataset and a database dataset. Dedicated to running PostgreSQL, no other apps running ap= art from SSH, no jails, etc. Not hitting memory/CPU limits. Database has recordsize=3D8k and compression=3Dlz4 It has so far always happened on a sunday/monday, one or twee weeks apart (coincidentally on saturday night a basebackup and an SQL backup are taken which would create some disk/postgresql activity). Obviously very inconvenient. I can't reproduce it on a dev system (which ha= s a similar hw/sw config but of course not a real usage pattern). Would appreciate any workarounds or suggestions. --=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-zHq3rICdbz>