Date: Wed, 13 Feb 2019 09:51:20 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 235683] [zfs] Panic during data access or scrub on 12.0-STABLE r343904 (blkptr at <addr> DVA 0 has invalid OFFSET) Message-ID: <bug-235683-3630-oQJFlwnNAP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235683-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-235683-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=3D235683 --- Comment #3 from Andriy Gapon <avg@FreeBSD.org> --- (In reply to Sergey Anokhin from comment #0) I think that your best bet is finding the directory that triggers the panic= and then moving your data excluding that directory to a new pool. You can try = to find the directory name in a debugger (e.g. pokinmg around frame 36) or empirically. Unfortunately, you have an on-disk data corruption and there is no easy way= to fix it (a hard way would be to learn ZFS on-disk format, to find the bad bi= ts and to somehow fix or clear them using a disk/hex editor). There is no obvious software bug, as far as I can tell, so this report is n= ot actionable. --=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-235683-3630-oQJFlwnNAP>