Date: Fri, 03 May 2019 18:31:57 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 237636] bhyve guest ZFS filesystem freezes in zcw->zcw_cv state Message-ID: <bug-237636-227-CeVQPq8RG5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237636-227@https.bugs.freebsd.org/bugzilla/> References: <bug-237636-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=3D237636 --- Comment #3 from Morgan Davis <freebsd-bugs@morgandavis.net> --- The aftereffects of the issue affecting my development bhyve system sound v= ery similar to those in bug #236220, and maybe they are related. However, this issue doesn't affect 9 other FreeBSD servers w/ ZFS that I run with a similarly outfitted FreeBSD 12.0-RELEASE-p3, and many are far more heavily burdened with work in smaller RAM space. The only key difference is that this deadlock occurs only my very lightly loaded bhyve guest server. By comparison, my other systems are far more abused. One is a 2GB instance = at DigitalOcean that acts as a data backup repository. It runs MySQL as a replication server and also the endpoint for lots of rsync pushes. It's constantly churning disk I/O with 13% swap in use (due to MySQL). In additi= on, it has a cron job that regularly cycles ZFS snapshots across 33 datasets for historical archiving. Never once has it, or any others I manage, froze up l= ike my bhyve guest. The only time I need to reboot it is for FreeBSD revision updates or reconfigurations that I want to test to make sure a restart occu= rs properly. Right now, it has 28 days uptime. Given this success everywhere else except for this one bhyve guest instance, I'm not sure my issue is related to the same one affecting those in bug #23= 6220 which=20 I will try to issue the procstat command the next time this happens, but I = have found that trying to run any command from an open bash prompt usually just stalls as well. I'll omit the pipe to grep to eliminate another possible deadlock trigger. --=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-237636-227-CeVQPq8RG5>