Date: Sun, 22 Jul 2018 10:08:51 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229614] ZFS lockup in zil_commit_impl Message-ID: <bug-229614-3630-etbA655j9T@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229614-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-229614-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=3D229614 --- Comment #9 from Andreas Sommer <andreas.sommer87@googlemail.com> --- Saw this again just now, after having reinstalled the whole instance on July 10th (12 days "incubation time" :P). Again, I could see the steady CPU usage (spinlock) in AWS CloudWatch monitoring graphs. Doing `procstat -kk` on the buildbot master process gave `procstat: sysctl: kern.proc.kstack: 67301: De= vice busy`, while `procstat -kka` made the system unavailable and rebooted. Thus= , no further info collected apart from the knowledge that this also happens for ashift=3D12 (originally I had an ashift=3D9 pool on the old instance which = had this problem every few days). Anything more we can do to debug/resolve this? --=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-229614-3630-etbA655j9T>