Date: Thu, 14 Feb 2019 04:16:39 +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-cXVjg4JbVw@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 Eugene Grosbein <eugen@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eugen@freebsd.org --- Comment #8 from Eugene Grosbein <eugen@freebsd.org> --- (In reply to Andriy Gapon from comment #3) Inability to fix data file system consistency is a bug. Yes, UFS can panic = too in case of found inconsistency but it has fsck to get file system back to consistent state. ZFS should have means to fix consistency too, even at cos= t of some user data loss in case of non-redundant pool. --=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-cXVjg4JbVw>