Date: Mon, 21 Jun 2021 12:29:02 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: =?UTF-8?B?W0J1ZyAyNTY3MTJdIFVGUzoga2VybmVsIHBhbmljOiBmZnNfYmxr?= =?UTF-8?B?ZnJlZV9jZzogZnJlZWluZyBmcmVlIGZyYWcg4oCTIGluIHJlc3BvbnNlIHRv?= =?UTF-8?B?IHBrZy1kZWxldGUoOCkgc29vbiBhZnRlciBsb2dpbg==?= Message-ID: <bug-256712-3630-xvJ6p1NUar@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256712-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-256712-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=3D256712 --- Comment #16 from Kirk McKusick <mckusick@FreeBSD.org> --- (In reply to andrew from comment #7) There are three cases here: 1) failure to properly clean up the filesystem when using journal 2) failure to properly clean up when running in background 3) failure to properly clean up when running synchronous fsck -p during startup. I would like to analyse each of these in turn so as to determine which method(s) are having problems. First I want to test (3); if it fails then t= he bug is in fsck_ffs itself. If the problem fails to manifest in (3), then ne= xt is to test (1); if it fails then the bug is in the journaling subsystem. Finally is to test (2); if it fails then the bug is in the background check= ing. So, useful to make forward progress is to test in each of the above ways in= the order (3), (1), then (2). --=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-256712-3630-xvJ6p1NUar>