Date: Fri, 27 Jun 2003 17:43:46 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Brett Glass <brett@lariat.org> Cc: questions@freebsd.org Subject: Re: fsck! Message-ID: <20030628004346.GB55502@rot13.obsecurity.org> In-Reply-To: <4.3.2.7.2.20030627165224.03568100@localhost> References: <4.3.2.7.2.20030627165224.03568100@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 > shutdown, the system complains of inconsistencies on the disk. Yet, if > one runs the command "fsck -f" after it's rebooted, the fsck program > doesn't fix the problems it finds; instead, it says "NO WRITE" at the > beginning of each report. (It seems not to want to touch things unless > they're unmounted.) So, the system has to come down AGAIN. > > What's the best and fastest way of ensuring disk consistency on a system > that you're powering up after an abrupt outage? What about a system that > 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+/OTCWry0BWjoQKURAojJAJ9oz/WbwWt//0acT2MmvEuDNpS+XgCgs94x W6oOdrGUDy6aNHs6uvFqzmk= =wpeo -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030628004346.GB55502>