public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Waldo Bastian <bastian@kde.org>
To: kde-core-devel@kde.org
Cc: Tim Connors <tconnors@astro.swin.edu.au>, 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 14:31:43 +0200	[thread overview]
Message-ID: <200407131431.43478.bastian@kde.org> (raw)
In-Reply-To: <20040713110520.GB8930@ugly.local>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue July 13 2004 13:05, Oswald Buddenhagen wrote:
> heya,
>
> read the attachement first (put on your asbestos underwear first ;).
> not exactly news to me, but somehow i never got to fixing it ...

There is nothing to fix, we already use a tempfile + rename, it's in KSaveFile 
since 1999. Or just look with strace if you don't believe me. This Tim 
Connors guy shouldn't talk about things he obviously knows nothing about.

As far as I can see the problem is that the filesystem writes out the meta 
data before the actual file data hits the disk which creates a period of time 
in which the on-disk state of the filesystem contains trashed files. I 
believe ReiserFS actually has an option to do things in a sane order so that 
it doesn't trash recently used files on an unclean shutdown.

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.

Cheers,
Waldo
- -- 
bastian@kde.org  |   KDE Community World Summit 2004  |  bastian@suse.com
bastian@kde.org  | 21-29 August, Ludwigsburg, Germany |  bastian@suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFA89YvN4pvrENfboIRAptaAJ9YBv63UUL7Elcl3QsjYJPbGche7wCdEzKr
Y+I4Kyi+p+r/gPixNdXQphE=
=c3HD
-----END PGP SIGNATURE-----

       reply	other threads:[~2004-07-13 12:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040713110520.GB8930@ugly.local>
2004-07-13 12:31 ` Waldo Bastian [this message]
2004-07-13 12:40   ` kconfig's file handling (was: XFS: how to NOT null files on fsck?) Tim Connors
2004-07-13 12:53   ` Oswald Buddenhagen
2004-07-13 21:02   ` Theodore Ts'o
2004-07-13 22:28   ` Chris Wedgwood
2004-07-14  6:27 Roy Butler
2004-07-14  6:44 ` 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=200407131431.43478.bastian@kde.org \
    --to=bastian@kde.org \
    --cc=kde-core-devel@kde.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tconnors@astro.swin.edu.au \
    /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