Date: Fri, 11 May 2001 09:01:25 -0700 From: Doug Barton <DougB@DougBarton.net> To: Kris Kennaway <kris@obsecurity.org> Cc: Kirk McKusick <mckusick@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc rc Message-ID: <3AFC0CD5.FB3B2E8B@DougBarton.net> References: <200105110740.f4B7ee040787@freefall.freebsd.org> <20010511004601.A18194@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > > 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)? > > > > 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. This'd definitely be good to have. While I reboot my -current workstation systems often, this'd be easy to miss on a server system in production (keeping in mind that today's -current will be [-]stable someday). Doug 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?3AFC0CD5.FB3B2E8B>