Date: Mon, 14 May 2001 17:45:52 -0400 (EDT) From: mi@aldan.algebra.com To: mckusick@mckusick.com Cc: kris@obsecurity.org, ru@FreeBSD.org, fs@FreeBSD.org Subject: Re: [kris@obsecurity.org: Re: cvs commit: src/etc rc] Message-ID: <200105142145.f4ELjrq13574@misha.privatelabs.com> In-Reply-To: <200105132342.QAA21879@beastie.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 May, Kirk McKusick wrote: >> > 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! > 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. So, Kris' proposition to keep rebooting is not really good either... Perhaps, fsck needs to be modified to do the logging by itself -- on different levels and priorities instead of relying on the logger? -mi 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?200105142145.f4ELjrq13574>