From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com, Michael Monnerie <michael.monnerie@is.it-management.at>
Subject: Re: zero size file after power failure with kernel 2.6.30.5
Date: Fri, 18 Sep 2009 22:05:56 +0200 [thread overview]
Message-ID: <200909182205.56647.Martin@lichtvoll.de> (raw)
In-Reply-To: <200908292102.21710@zmi.at>
[-- Attachment #1.1: Type: Text/Plain, Size: 1730 bytes --]
Am Samstag 29 August 2009 schrieb Michael Monnerie:
> I have /home mounted like this:
> /dev/sda3 on /disks/work1 type xfs
> (rw,noatime,logbufs=8,logbsize=256k,attr2,barrier,largeio,swalloc)
>
> Hardware: onboard SATA with a single WD VelociRaptor drive.
>
> My power supply melted and so I had a power fail and a sudden death
> crash.
> ( So please remember: even when you have a UPS, your power can fail ! )
[...]
> But almost is not good enough: Exactly my kmail config file was 0 sized
> - obviously: at least when I started kmail, it started fresh without
> any accounts or config, but once I exited kmail the config was created
> with the default values and about 12KB size, while my config has
> >200KB.
Most likely missing-fsync() issue that still could happen with XFS. Thats
a long discussion ;-).
Try
# KDE Sync
# http://oss.sgi.com/pipermail/xfs/2009-March/040628.html
export KDE_EXTRA_FSYNC=1
This environment variable didn't have any effect with KDE 3 but should work
with recent KDE versions. See also:
http://bugs.kde.org/187172
I switched to Ext4 for my work notebook in the meantime, but my Amarok
laptop is still using XFS. Ext4 skips delayed allocation for certain
cases, AFAIR truncates and renames, since kernel 2.6.30 as Linus and
others urged Theodore T'so to make Ext4 behave nicely with applications.
XFS only does so for truncates and there is a little race still, AFAIK.
In the meantime I tend to agree that the filesystem should play it safe -
POSIX semantics or not. But I did not completely made up my mind yet.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-09-18 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 19:02 zero size file after power failure with kernel 2.6.30.5 Michael Monnerie
2009-08-29 22:13 ` Eric Sandeen
2009-08-31 23:10 ` Peter Grandi
2009-09-01 7:18 ` Michael Monnerie
2009-09-01 10:32 ` Peter Grandi
2009-09-01 14:19 ` Emmanuel Florac
2009-09-01 22:52 ` Michael Monnerie
[not found] ` <alpine.DEB.2.00.0908291517350.24777@p34.internal.lan>
2009-08-30 8:39 ` Michael Monnerie
2009-09-18 20:05 ` Martin Steigerwald [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=200909182205.56647.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=michael.monnerie@is.it-management.at \
--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