Date: Mon, 08 Mar 2021 19:42:21 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 244048] mksnap_ffs hangs machine (12.1 regression over 11.3) Message-ID: <bug-244048-3630-U2IR19TrRo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-244048-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-244048-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=3D244048 --- Comment #20 from ml@netfence.it --- (In reply to Kirk McKusick from comment #19) I guess so. If data is gone and filenames too (including in snapshots), there should be nothing private remaining. Right? Meanwhile I made another test: I reverted back to 11.x and saw that it's now giving the same troubles as 12.x and 13.0 do. So my conclusion is that snapshotting/deleting snapshots on 12.x has already messed the disk in a way that fsck doesn't even detect, but hangs the machi= ne on some operations. Probably this is less useful than I hoped: while it would be nice to have a= way to fix this image, this cannot be used to reproduce the corruption on deman= d, since it's already ruined. Maybe seeing what the trouble is can give some h= int? IOW I hoped to have pinpointed the situation when the trouble starts, but i= t's not immediately evident and I'm already past it :( --=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-244048-3630-U2IR19TrRo>