From owner-freebsd-questions@FreeBSD.ORG Fri Jun 27 17:43:47 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6A8F37B40F for ; Fri, 27 Jun 2003 17:43:47 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-104-32.dsl.lsan03.pacbell.net [64.169.104.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BDF643FEC for ; Fri, 27 Jun 2003 17:43:47 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id D851466BE5; Fri, 27 Jun 2003 17:43:46 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id D1372BB9; Fri, 27 Jun 2003 17:43:46 -0700 (PDT) Date: Fri, 27 Jun 2003 17:43:46 -0700 From: Kris Kennaway To: Brett Glass Message-ID: <20030628004346.GB55502@rot13.obsecurity.org> References: <4.3.2.7.2.20030627165224.03568100@localhost> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CUfgB8w4ZwR/yMy5" Content-Disposition: inline In-Reply-To: <4.3.2.7.2.20030627165224.03568100@localhost> User-Agent: Mutt/1.4.1i cc: questions@freebsd.org Subject: Re: fsck! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2003 00:43:48 -0000 --CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 27, 2003 at 04:55:45PM -0600, Brett Glass wrote: > Often, after a FreeBSD 4.x system has been powered down without a proper= =20 > shutdown, the system complains of inconsistencies on the disk. Yet, if=20 > one runs the command "fsck -f" after it's rebooted, the fsck program=20 > doesn't fix the problems it finds; instead, it says "NO WRITE" at the=20 > beginning of each report. (It seems not to want to touch things unless=20 > they're unmounted.) So, the system has to come down AGAIN. >=20 > What's the best and fastest way of ensuring disk consistency on a system= =20 > that you're powering up after an abrupt outage? What about a system that= =20 > powered up again before you arrived to nurse it through a reboot? You're supposed to boot into single-user mode to repair the filesystems before attempting to bring it up to multiuser state. Kris --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+/OTCWry0BWjoQKURAojJAJ9oz/WbwWt//0acT2MmvEuDNpS+XgCgs94x W6oOdrGUDy6aNHs6uvFqzmk= =wpeo -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5--