From: Roy Butler <roy.butler@jpl.nasa.gov>
To: linux-kernel@vger.kernel.org
Cc: Chris Wedgwood <cw@f00f.org>
Subject: Re: kconfig's file handling
Date: Wed, 14 Jul 2004 09:57:23 -0700 [thread overview]
Message-ID: <40F565F3.3080103@jpl.nasa.gov> (raw)
In-Reply-To: <20040714064400.GA9721@taniwha.stupidest.org>
Chris,
Chris Wedgwood wrote:
> On Tue, Jul 13, 2004 at 11:27:50PM -0700, Roy Butler wrote:
>
>
>>By example, if you create a file, write to it, and then delete it
>>fast enough, it will never hit the disk under XFS.
>
>
> Nor will it under some other filesystems... and in the above scenario
> I'm not sure that matters, why must a temporary file hit the disk at
> all?
>
>
> --cw
>
Suppose you want to do something with the file's contents before you
delete it, but the system goes down before you have the chance. Wasn't
that the impetus for this thread? With XFS, the potential for data loss
is greater; that was my point. I believe that everyone who pays extra
for batter-backed I/O caches would agree. :) Sure, different
filesystems have their options, but this liability is ingrained in XFS.
Roy
prev parent reply other threads:[~2004-07-14 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 6:27 kconfig's file handling (was: XFS: how to NOT null files on fsck?) Roy Butler
2004-07-14 6:44 ` Chris Wedgwood
2004-07-14 16:57 ` Roy Butler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40F565F3.3080103@jpl.nasa.gov \
--to=roy.butler@jpl.nasa.gov \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox