Date: Fri, 16 Mar 2007 08:42:20 +1000 From: David Cecil <david.cecil@nokia.com> To: ext Kris Kennaway <kris@obsecurity.org> Cc: freebsd-fs@FreeBSD.org, ext Pawel Jakub Dawidek <pjd@FreeBSD.org> Subject: Re: FFS writes to read-only mount Message-ID: <45F9CBCC.7050006@nokia.com> In-Reply-To: <20070315223641.GA89923@xor.obsecurity.org> 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> <20070315223641.GA89923@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> It may be that snapshots are used, but not explicitly. The startup >> scripts attempt to run fsck in the background, which would normally >> 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? > Yeah, I was wondering the same thing Kris. In fact, that was one of my first suspects when I started looking at this problem. I had eliminated it because fstat (and ps in ddb) doesn't show fsck running, or the raw device open for writing. Maybe fsck had already closed the descriptor and exited but the write to disk (GEOM mirror) is still outstanding in the buffer cache? Dave -- Software Engineer Secure and Mobile Connectivity Nokia Enterprise Solutions +61 7 5553 8307 (office) +61 412 728 222 (cell)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45F9CBCC.7050006>