Date: Fri, 11 May 2001 12:16:18 -0700 From: Kirk McKusick <mckusick@mckusick.com> To: Kris Kennaway <kris@obsecurity.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, Ruslan Ermilov <ru@FreeBSD.org> Subject: Re: [kris@obsecurity.org: Re: cvs commit: src/etc rc] Message-ID: <200105111916.MAA16255@beastie.mckusick.com> In-Reply-To: Your message of "Fri, 11 May 2001 12:10:20 %2B0300." <20010511121020.B31232@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Date: Fri, 11 May 2001 12:10:20 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: Kirk McKusick <mckusick@mckusick.com> Subject: [kris@obsecurity.org: Re: cvs commit: src/etc rc] ----- Forwarded message from Kris Kennaway <kris@obsecurity.org> ----- 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 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. Kris ----- End forwarded message ----- At the moment there is no provision for notifying the system administrator since the output of fsck is simply being sent to the `logger' program (which by default will put the messages into /var/log/messages). It would be possible to add a syslog (or wall) call to the fsck program itself. Another alternative would be to have fsck forcibly downgrade the offending filesystem to read-only mode. However, if it were say the /var filesystem, the system would fall apart pretty quickly. I am open to suggestions on how best to proceed. Kirk McKusick 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?200105111916.MAA16255>