| To: | Martin Steigerwald <Martin@xxxxxxxxxxxx> |
|---|---|
| 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) |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 29 Dec 2008 14:54:06 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <200812292048.41193.Martin@xxxxxxxxxxxx> |
| References: | <200812291920.34123.Martin@xxxxxxxxxxxx> <200812292048.41193.Martin@xxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
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. |
| Previous by Date: | 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 |
|---|---|
| Next by Date: | Re: massively truncated files with XFS with sudden power loss on 2.6.27 and 2.6.28, Martin Steigerwald |
| Previous by Thread: | 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 |
| Next by Thread: | Re: massively truncated files with XFS with sudden power loss on 2.6.27 and 2.6.28, Chris Wedgwood |
| Indexes: | [Date] [Thread] [Top] [All Lists] |