Date: Thu, 15 Mar 2007 18:36:41 -0400 From: Kris Kennaway <kris@obsecurity.org> To: David Cecil <david.cecil@nokia.com> Cc: freebsd-fs@FreeBSD.org, ext Pawel Jakub Dawidek <pjd@FreeBSD.org> Subject: Re: FFS writes to read-only mount Message-ID: <20070315223641.GA89923@xor.obsecurity.org> In-Reply-To: <45F9C9B4.4030508@nokia.com> References: <45F776AE.8090702@nokia.com> <20070314161041.GI7847@garage.freebsd.pl> <45F8EE27.6070208@nokia.com> <20070315090031.GB80993@deviant.kiev.zoral.com.ua> <20070315092659.GA14080@garage.freebsd.pl> <45F9C9B4.4030508@nokia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 16, 2007 at 08:33:24AM +1000, David Cecil wrote: > It may be that snapshots are used, but not explicitly. The startup=20 > scripts attempt to run fsck in the background, which would normally=20 > require a snapshot, but shouldn't for a read-only mount, right? What happens if the filesystem is marked dirty, background fsck is enabled, but the filesystem is mounted read-only? Kris --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF+cp4Wry0BWjoQKURAgDIAJ0Sd8EDr3FSlRCGSxWV0xNRttRahgCfeRrw /IYw2/JCNWSaPmNTN6R3sFw= =d40C -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070315223641.GA89923>