xfs
[Top] [All Lists]

Re: zero size file after power failure with kernel 2.6.30.5

To: xfs@xxxxxxxxxxx
Subject: Re: zero size file after power failure with kernel 2.6.30.5
From: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 1 Sep 2009 09:18:30 +0200
In-reply-to: <19100.22644.149019.555685@xxxxxxxxxxxxxxxxxx>
Organization: it-management http://it-management.at
References: <200908292102.21710@xxxxxx> <4A99A80C.9010307@xxxxxxxxxxx> <19100.22644.149019.555685@xxxxxxxxxxxxxxxxxx>
User-agent: KMail/1.10.3 (Linux/2.6.30.5-ZMI; KDE/4.1.3; x86_64; ; )
On Dienstag 01 September 2009 Peter Grandi wrote:
> Then 'mount' with '-o sync'
[snip]

Yes. I could also simply switch back to reiserfs, where I never had this 
kind of issue, despite lots of crashes etc. I'm not here to blame the 
devs, just wanted to report that this kind of problem still exists, and 
maybe someone taps into the problem and can improve it.

There was a similar problem with the change from ext3 to ext4, with a 
big discussion. Ext4 has been improved, I don't know how good it is now.
And I know lots of discussions whether the app or the kernel is wrong, 
and whether you should fsync() after rename(). In ext4 they reorganized 
the way metaupdates are done, maybe that can help xfs too.

It seems kmail writes its config every 7 minutes, so it is vulnerable 
for 3 seconds then. I've set
vm.dirty_expire_centisecs = 1000
now to improve the situation a bit.

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4

Attachment: signature.asc
Description: This is a digitally signed message part.

<Prev in Thread] Current Thread [Next in Thread>