Date: Wed, 16 Mar 2022 18:39:40 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262580] fsck fails system startup if USB disk is not yet configured Message-ID: <bug-262580-227-sFm7RvAIzv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-262580-227@https.bugs.freebsd.org/bugzilla/> References: <bug-262580-227@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=3D262580 --- Comment #2 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3D2983ec0a87a18943564548c5c00c879c8= db83edf commit 2983ec0a87a18943564548c5c00c879c8db83edf Author: Kirk McKusick <mckusick@FreeBSD.org> AuthorDate: 2022-03-16 18:37:15 +0000 Commit: Kirk McKusick <mckusick@FreeBSD.org> CommitDate: 2022-03-16 18:37:15 +0000 Ensure that fsck(8) / fsck_ffs(8) produces the correct exit code for missing devices. The fsck_ffs(8) utility uses its internal function openfilesys() when opening a disk to be checked. This change avoids the use of pfatal() in openfilesys() which always exits with failure (exit value 8) so that the caller can choose the correct exit value. In the case of a non-existent device it should exit with value 3 which allows the startup system to wait for drives (such as those attached by USB) to come online. Reported by: karels Tested by: karels PR: 262580 MFC after: 3 days sbin/fsck_ffs/setup.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) --=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-262580-227-sFm7RvAIzv>