All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Felix E. Klee" <felix.klee@inka.de>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Data safety horror stories?
Date: Mon, 11 Feb 2008 17:46:29 +0100	[thread overview]
Message-ID: <1202748389.28320.1236240801@webmail.messagingengine.com> (raw)

I heard that, in case of a power failure, XFS may lose data, even data
that was already existing on the disk. For example, I heard horror
stories of files being overwritten with zeros.

Are those stories true?

If so:

* Do you recommend not using XFS on devices that may frequently fail due
  to power failure?

* Is it possible to find out what files have been damaged? If not,
  will only files be affected that have been changed during the last
  couple of hours?

* Are there options to increase data safety? Should one run a regular
  "sync" in a cron job?

* Is it unsafe to use XFS in a virtual machine which may sometimes be
  terminated without proper shutdown? Suppose the virtual machine is
  running under Windows, and Windows may sometimes be terminated without
  proper shutdown.

I currently am using XFS under Ubuntu 7.10 (Kernel 2.6.22), running in a
virtual machine (VMware) under Windows.  The XFS file system is in a
native partition on a second HDD.

-- 
Felix E. Klee
Jabber/Google Talk: feklee@jabber.org, SIP: 9779619@sipgate.de
ICQ: 158124695, Yahoo!: feklee, AIM: felix.klee@inka.de
Gizmo: felixklee, Skype: felix.klee

             reply	other threads:[~2008-02-11 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 16:46 Felix E. Klee [this message]
2008-02-11 17:12 ` Data safety horror stories? Iustin Pop
2008-02-11 21:23   ` Felix E. Klee
2008-02-18 21:28     ` Martin Steigerwald
2008-02-18 21:41       ` Felix E. Klee
2008-02-18 21:49         ` Martin Steigerwald
2008-02-18 22:50     ` David Chinner
2008-02-11 22:03 ` David Chinner

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=1202748389.28320.1236240801@webmail.messagingengine.com \
    --to=felix.klee@inka.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 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.