Date: Sun, 13 May 2001 16:42:55 -0700 From: Kirk McKusick <mckusick@mckusick.com> To: Mikhail Teterin <mi@misha.privatelabs.com> Cc: Kris Kennaway <kris@obsecurity.org>, 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: <200105132342.QAA21879@beastie.mckusick.com> In-Reply-To: Your message of "Sun, 13 May 2001 13:58:42 EDT." <200105131758.f4DHwgl09955@misha.privatelabs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: Mikhail Teterin <mi@misha.privatelabs.com> > Subject: Re: [kris@obsecurity.org: Re: cvs commit: src/etc rc] > In-Reply-To: <20010512023602.A40616@xor.obsecurity.org> "from Kris Kennaway at > May 12, 2001 02:36:02 am" > To: Kris Kennaway <kris@obsecurity.org> > Date: Sun, 13 May 2001 13:58:42 -0400 (EDT) > CC: Kirk McKusick <mckusick@mckusick.com>, cvs-committers@FreeBSD.org, > cvs-all@FreeBSD.org, Ruslan Ermilov <ru@FreeBSD.org>, fs@FreeBSD.org > > > 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 Indeed, a foreground fsck can be run once the downgrade to read-only has happened. However, doing so automatically is unlikely to be useful since nearly every error that would get us to this point will also cause an `fsck -p' to fail. So, at this point a system administrator is going to have to intervene to do a manual fsck. Once the downgrade to read-only has happened, no further filesystem damage can occur, so there is not a great rush to run the manual fsck. However, if the affected filesystem is something crucial like /var, the system may not run at all well until the problem is fixed. Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105132342.QAA21879>