Date: Tue, 02 Feb 2021 14:21:16 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 253158] Panic: snapacct_ufs2: bad block - Non-suJ mksnap_ffs(8) crash Message-ID: <bug-253158-3630-Q4VeDsblun@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-253158-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-253158-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=3D253158 --- Comment #4 from Harald Schmalzbauer <bugzilla.freebsd@omnilan.de> --- (In reply to Kirk McKusick from comment #3) Happy to confirm that creating a snapshot with the "known-problematic" FFS mdimage(4) doesn't panic anymore with stable_13 and your patch applied (Fre= eBSD 13.0-ALPHA3 #0 stable/13-f19a4e97d-dirty). I can also confirm that the now successfully creatable snapshot seems to wo= rk as well as the already present snapshot of the problematic FFS image; at le= ast for ls(1) and fsck(1). No idea about the root cause and why this problem only appeared once out of dozend(s) new filesystems. Any hints highly appreciated, in case it's possible to explain in a few sentences to someone not familiar with FFS internals. Thank you very much! -harry --=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-253158-3630-Q4VeDsblun>