All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roy Butler <roy.butler@jpl.nasa.gov>
To: linux-kernel@vger.kernel.org
Subject: Re: kconfig's file handling (was: XFS: how to NOT null files on fsck?)
Date: Tue, 13 Jul 2004 23:27:50 -0700	[thread overview]
Message-ID: <40F4D266.4050006@jpl.nasa.gov> (raw)

On Tue, Jul 13, 2004 at 02:31:43PM +0200, Waldo Bastian wrote:
 >
 > The sentiment among filesystem developers seem to be that they don't 
care if
 > they trash files as long as the filesystem itself remains in a consistent
 > state. This kind of dataloss is the result of that attitude, either go
 > complain with them if it bothers you, or use a filesystem that does 
it right.
 >

Exactly.  Don't blame KDE.  Using XFS is equivalent to using 
non-battery-backed NVRAM on an external disk array.  Great if 
performance is _the_ metric and lost results can easily be regenerated 
(like in frame rendering).  By example, if you create a file, write to 
it, and then delete it fast enough, it will never hit the disk under XFS.


Roy Butler

             reply	other threads:[~2004-07-14  6:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14  6:27 Roy Butler [this message]
2004-07-14  6:44 ` kconfig's file handling (was: XFS: how to NOT null files on fsck?) Chris Wedgwood
2004-07-14 16:57   ` kconfig's file handling Roy Butler
     [not found] <20040713110520.GB8930@ugly.local>
2004-07-13 12:31 ` kconfig's file handling (was: XFS: how to NOT null files on fsck?) Waldo Bastian
2004-07-13 12:40   ` Tim Connors
2004-07-13 12:53   ` Oswald Buddenhagen
2004-07-13 21:02   ` Theodore Ts'o
2004-07-13 22:28   ` Chris Wedgwood

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=40F4D266.4050006@jpl.nasa.gov \
    --to=roy.butler@jpl.nasa.gov \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.