Date: Fri, 11 May 2001 00:46:01 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Kirk McKusick <mckusick@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc rc Message-ID: <20010511004601.A18194@xor.obsecurity.org> In-Reply-To: <200105110740.f4B7ee040787@freefall.freebsd.org>; from mckusick@FreeBSD.org on Fri, May 11, 2001 at 12:40:39AM -0700 References: <200105110740.f4B7ee040787@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 11, 2001 at 12:40:39AM -0700, Kirk McKusick wrote: > 6) What happens if a background fsck fails (i.e., fsck finds > errors that would normally require a manual fsck)? > =20 > Ans) The filesystem will be marked as needing a manual fsck. > At the next system reboot, the check will be done in > foreground and the usual actions taken (usually a failure > to go multi-user until fsck has been run by hand on the > affected filesystem). Is there any facility for informing the administrator that a foreground fsck is required (syslog at higher priority, e.g. LOG_EMERG?) This condition sounds like it could be fatal to the filesystem if it continues to operate without being addressed. Kris --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6+5i5Wry0BWjoQKURAp9IAKDAotuarU2Fu2NkQ5w9B+jLPTJ5jgCgrlHL YOH0gy6hpoJy4H+E/f8mqd8= =ok3Z -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010511004601.A18194>