All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: zero size file after power failure with kernel 2.6.30.5
Date: Sat, 29 Aug 2009 21:02:21 +0200	[thread overview]
Message-ID: <200908292102.21710@zmi.at> (raw)

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 ! )

After replacing the part, I had almost no isse with my KDE desktop. In 
earlier XFS releases, I constantly lost several config files all 
truncated to 0 length or at some point only contained NULLs on such 
occasions. So the situation improved a lot.

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.

Shouldn't it be that this doesn't happen anymore? I'd love to be in a 
position where I really can rely on a crash not trashing any of my files 
anymore. I used to have reiserfs previously, and never, not a single 
time despite many crashes, did I have such an issue. I'd really be 
pleased so see such stability in XFS. I'm using barriers - what else 
must I do?

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

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2009-08-29 19:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-29 19:02 Michael Monnerie [this message]
2009-08-29 22:13 ` zero size file after power failure with kernel 2.6.30.5 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

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=200908292102.21710@zmi.at \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.