Date: Sun, 13 May 2001 13:58:42 -0400 (EDT) From: Mikhail Teterin <mi@misha.privatelabs.com> To: Kris Kennaway <kris@obsecurity.org> Cc: Kirk McKusick <mckusick@mckusick.com>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, Ruslan Ermilov <ru@FreeBSD.org>, fs@FreeBSD.org Subject: Re: [kris@obsecurity.org: Re: cvs commit: src/etc rc] Message-ID: <200105131758.f4DHwgl09955@misha.privatelabs.com> In-Reply-To: <20010512023602.A40616@xor.obsecurity.org> "from Kris Kennaway at May 12, 2001 02:36:02 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> Working under the assumption that the only time fsck is likely to fail > in this manner is if there are FS errors which can't be resolved in > the background, and which may result in further FS damage if left > uncorrected, the best option seems to be to take some action which > prevents this damage. > > The best series of actions might be the following: > > 1) Downgrade the FS to readonly mode. Can't a foreground fsck be run at this moment? Having to reboot for anything is rather ugly... I'm sure there is a reason it can not, I'm just wondering, what that reason is. Thanks! -mi > 2) syslog(LOG_EMERG, "Unrecoverable error in background check of %s, > FS downgraded to readonly mode. Reboot in 60 seconds to attempt to > repair the error. Kill PID %d now to abort.", ...) > > 3) Reboot in 60 seconds 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?200105131758.f4DHwgl09955>