Date: Wed, 06 Apr 2016 17:10:10 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 207667] Reproducable kernel panics whilst scrubbing a zvol pool... Message-ID: <bug-207667-3630-v4peXC8WnS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-207667-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-207667-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=3D207667 --- Comment #9 from Andriy Gapon <avg@FreeBSD.org> --- (In reply to Michelle Sullivan) Replying to multiple comments at once. Yes, taking a picture of a monitor is a fine last measure. A serial consol= e, real or emulated via, e.g., IPMI or AMT, is better, of course. The panic looks like a result of a well-known (among developers) and very h= ard to fix problem with interaction between GEOM and ZVOLs that arises from usi= ng ZFS pools on top of ZFS volumes. I can not offer you any fix although I ha= ve got some work-in-progress on this issue. I can suggest a work-around: create a FreeBSD VM using the volumes comprisi= ng the pool as the VM's disks and run the scrub within the VM. Besides zpool scrub commands like zpool reopen, zpool split, zpool online [= -e] can also trigger the same bug for pools on top of ZFS volumes. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-207667-3630-v4peXC8WnS>