From: Christoph Hellwig <hch@infradead.org>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: xfs@oss.sgi.com
Subject: Re: safe writing in applications (was: Re: massively truncated files with XFS with sudden power loss on 2.6.27 and 2.6.28)
Date: Mon, 29 Dec 2008 14:54:06 -0500 [thread overview]
Message-ID: <20081229195406.GA7613@infradead.org> (raw)
In-Reply-To: <200812292048.41193.Martin@lichtvoll.de>
On Mon, Dec 29, 2008 at 08:48:40PM +0100, Martin Steigerwald wrote:
> It might be wise however to file enhancement requests for the KDE
> applications where I observed this behavior if safer writing within the
> applications is possible. Any hints on what application developers should
> keep in mind when writing out config files?
Preferably use O_SYNC. Never truncate and then rewrite, in doubt write
a new file and rename it to the right place after it was fsync'ed (the
mailserver trick)
in the meantime a nice way to hack around this is do chattr +S for all
these files which forces synchronous writes. Doesn't help if they
actually use the rename trick above sometimes.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2008-12-29 19:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 18:20 massively truncated files with XFS with sudden power loss on 2.6.27 and 2.6.28 Martin Steigerwald
2008-12-29 19:03 ` Chris Wedgwood
2008-12-29 19:08 ` Eric Sandeen
2008-12-29 20:00 ` Martin Steigerwald
2008-12-30 0:14 ` Chris Wedgwood
2008-12-29 19:09 ` Russell Cattelan
2008-12-29 19:20 ` Christoph Hellwig
2008-12-29 19:29 ` Chris Wedgwood
2008-12-29 20:09 ` Russell Cattelan
2008-12-29 20:17 ` Chris Wedgwood
2008-12-29 21:25 ` Russell Cattelan
2008-12-29 21:56 ` Eric Sandeen
2008-12-29 19:48 ` safe writing in applications (was: Re: massively truncated files with XFS with sudden power loss on 2.6.27 and 2.6.28) Martin Steigerwald
2008-12-29 19:54 ` Christoph Hellwig [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=20081229195406.GA7613@infradead.org \
--to=hch@infradead.org \
--cc=Martin@lichtvoll.de \
--cc=xfs@oss.sgi.com \
/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