Date: Wed, 29 Jan 2025 19:55:22 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 284437] zdb -y somepool fails Message-ID: <bug-284437-227-zotL6MExTw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-284437-227@https.bugs.freebsd.org/bugzilla/> References: <bug-284437-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=3D284437 Rob Norris <robn@despairlabs.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robn@despairlabs.com --- Comment #2 from Rob Norris <robn@despairlabs.com> --- I've been explaining to people all morning that by itself, zdb crashing is meaningless. It's not a general purpose tool. It's a parallel implementatio= n of the ZFS core, in userspace, that runs against the block devices directly, "under" the kernel implementation (if it exists). The most common reason fo= r it crashing against an active pool is that the on-disk data changed out from u= nder it, and it got confused. This is not rare. I'm not saying there's not some people with broken pools as reported upstre= am. I am saying that if the _only_ data point is "zdb crashed", then there is almost certainly no issue. --=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-284437-227-zotL6MExTw>