From owner-freebsd-questions@FreeBSD.ORG Thu Aug 23 08:12:51 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B26B16A419 for ; Thu, 23 Aug 2007 08:12:51 +0000 (UTC) (envelope-from karol.kwiat@gmail.com) Received: from hu-out-0506.google.com (hu-out-0506.google.com [72.14.214.236]) by mx1.freebsd.org (Postfix) with ESMTP id 8375413C4A6 for ; Thu, 23 Aug 2007 08:12:50 +0000 (UTC) (envelope-from karol.kwiat@gmail.com) Received: by hu-out-0506.google.com with SMTP id 28so45151hub for ; Thu, 23 Aug 2007 01:12:49 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:openpgp:content-type; b=M9PRibf3WAaq8/67PVF1X5xhBBJMtZpiRH6+hQMJGh7a0rDSQYKty6/6n5/vnLAz6I32AjQQGY37MN1jUrHOMDQArUQ91VvVP76gpHoBaesLyz/lFkt4FtEcehF9LWXL3gpPznzFWoR4B49XT7b2/2wMovFNwPW30xQe1xPG6G4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:openpgp:content-type; b=YlyUU4J4yWrWJ01KL9tmnwJt+QlYIAjProsBYPDC+KE6pH/oNPH9W9w53+mIeVRvM+yFhfQrLr7L5l4tdRosK0JtmNa48tfMJdbbHxTvaf1Kh7udpA4BWG/ZBj577dPOuNW6nL09p24Z9Kghjbzhw24F0p1ZCXPA4N6a0fFIAMY= Received: by 10.86.51.2 with SMTP id y2mr1180347fgy.1187856768779; Thu, 23 Aug 2007 01:12:48 -0700 (PDT) Received: from persephone.orchid.homeunix.org ( [84.10.173.180]) by mx.google.com with ESMTPS id d13sm3017339fka.2007.08.23.01.12.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 23 Aug 2007 01:12:48 -0700 (PDT) Message-ID: <46CD4173.1080000@gmail.com> Date: Thu, 23 Aug 2007 10:12:35 +0200 From: Karol Kwiatkowski User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: Ian Smith References: In-Reply-To: X-Enigmail-Version: 0.95.2 OpenPGP: id=06E09309; url=http://www.orchid.homeunix.org/carlos/gpg/0x06E09309.asc Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enigFB6AFBC894B3841F413A49B0" Cc: Chris , freebsd-questions@freebsd.org, Bill Moran Subject: Re: fsck strangeness X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: karol.kwiat@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 08:12:51 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFB6AFBC894B3841F413A49B0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ian Smith wrote: > On Wed, 22 Aug 2007, Chris wrote: > > If its bad to run fsck on a mounted read,write then why does > > background fsck do it? or you talking about foreground fsck only? >=20 > Well I was referring to foreground fsck, and I still don't know why > running it on a mounted fs is 'bad' when fsck runs in 'NO WRITE' mode > anyway when it finds a fs is mounted, hence my query above. Here's my understanding: Mounted fs (rw) isn't in stable state, there may be some writes to it - daemons, buffers flushes, etc. In this condition fsck can report inconsistency. And fsck running in 'NO WRITE' won't help anyway :) Cheers, Karol --=20 Karol Kwiatkowski OpenPGP 0x06E09309 --------------enigFB6AFBC894B3841F413A49B0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRs1BeghgT0HIecD5AQj2Iwf9GInoAXPjuVZon97DxntXSQISzHg1+wQj dGtwqbryJ4PiiRfcDDzU7jkHpEP1GS+5EzNKp4Mj0+2c0bkVNUBkeC2JRBgJOD9U Qi8/xYfj3KP/2Ubh6naRJE1a0ddlrc8j4rIgmczvoaZw32blLX/uURSgBKDC5+de fdahbEUfuIHDrumt+1GbqbSsDGvsoWj+X0dE0iX5DjfWbYCZHzFL5X6lYicJNPjc a04AU9s5WCDUFRnqvlLSREIRRUanQCjgae7zmmFz06Dph5aiMLKEzJuiJ0+yPEqq ROpAW1vU1rB6YlmLrmzq7RJ6aC3hFdopt6ZRvEJUbigLwiJP10qaPw== =H1Mu -----END PGP SIGNATURE----- --------------enigFB6AFBC894B3841F413A49B0--