From owner-freebsd-fs Sat May 12 2:36:11 2001 Delivered-To: freebsd-fs@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-32.dsl.lsan03.pacbell.net [63.207.60.32]) by hub.freebsd.org (Postfix) with ESMTP id 4CE4C37B423; Sat, 12 May 2001 02:36:03 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 71D0B66C04; Sat, 12 May 2001 02:36:02 -0700 (PDT) Date: Sat, 12 May 2001 02:36:02 -0700 From: Kris Kennaway To: Kirk McKusick Cc: Kris Kennaway , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, Ruslan Ermilov , fs@FreeBSD.org Subject: Re: [kris@obsecurity.org: Re: cvs commit: src/etc rc] Message-ID: <20010512023602.A40616@xor.obsecurity.org> References: <20010511121020.B31232@sunbay.com> <200105111916.MAA16255@beastie.mckusick.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105111916.MAA16255@beastie.mckusick.com>; from mckusick@mckusick.com on Fri, May 11, 2001 at 12:16:18PM -0700 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 11, 2001 at 12:16:18PM -0700, Kirk McKusick wrote: > 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=20 > suggestions on how best to proceed. 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. 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 This option has a more drastic effect on the system in the short term, but allows the possibility for fsck to correct the error and continue once it comes back up, instead of continuing to operate in a degraded mode (with possible negative impact on the system) until manual operator intervention. Kris --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6/QQBWry0BWjoQKURAlwOAJ9LCCgfUlP6UcJWOSyi/npZKNKF/wCbBoOj +r8KRqCOvg/nU8RaBu+DvZg= =fygn -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message