Date: Tue, 1 Jul 2008 11:10:48 +0200 From: Ruben de Groot <mail25@bzerk.org> To: Jim <stapleton.41@gmail.com> Cc: Roland Smith <rsmith@xs4all.nl>, freebsd-questions@freebsd.org Subject: Re: filesystem information Message-ID: <20080701091048.GA31499@ei.bzerk.org> In-Reply-To: <80f4f2b20806301212n1bf6137bq75f40464212c2304@mail.gmail.com> References: <80f4f2b20806300401x71483882x8e9a6cf919f1ff9@mail.gmail.com> <20080630073059.be11304d.wmoran@potentialtech.com> <80f4f2b20806300930p67ca1fd5xf9ad59d16889df36@mail.gmail.com> <20080630170400.GB65282@slackbox.xs4all.nl> <80f4f2b20806301212n1bf6137bq75f40464212c2304@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 30, 2008 at 03:12:59PM -0400, Jim typed: > > I'm aware of nothing but a UPS can completely protect me from an > outage. I was just wondering why that ONE file system was misbehaving, > and the rest are prefectly fine - which seemed odd. Additionally, why > were files that are read, but not written, being lost? I can > understand losing files that are being written, but if there's a file > that has bene written several restarts ago, not written to thereafter, > and has been fine ever since, why is it being lost now? Just a thought, but in normal circumstances files *are* written to, even when they are just being read: the access time is updated (unless you mount the fs with the noatime flag). Ruben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080701091048.GA31499>