From: David Chinner <dgc@sgi.com>
To: "Felix E. Klee" <felix.klee@inka.de>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: Data safety horror stories?
Date: Tue, 12 Feb 2008 09:03:39 +1100 [thread overview]
Message-ID: <20080211220339.GZ155407@sgi.com> (raw)
In-Reply-To: <1202748389.28320.1236240801@webmail.messagingengine.com>
On Mon, Feb 11, 2008 at 05:46:29PM +0100, Felix E. Klee wrote:
> 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?
Depends on how much you care about your system and data.
I use XFS on write-cache enabled SATA drives without barriers with
no UPS (yes, it's unsafe!) and I lose power at least once a week. I
haven't had a data loss or corruption in over two years and tens of
power failures....
> * Is it possible to find out what files have been damaged?
Not easily.
> If not,
> will only files be affected that have been changed during the last
> couple of hours?
Last few seconds before the power fail, actually.
> * Are there options to increase data safety? Should one run a regular
> "sync" in a cron job?
If you are truly paranoid - turn off drive caching and mount with
the 'wsync' option.
> * Is it unsafe to use XFS in a virtual machine which may sometimes be
> terminated without proper shutdown?
I do that all the time, too. Corruption is rare and usually
as a result of some bug in the code I'm testing ;)
> 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.
Should be just fine. If you are really concerned - test it.
Cheers,
Dave.
>
> --
> 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
>
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2008-02-11 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 16:46 Data safety horror stories? Felix E. Klee
2008-02-11 17:12 ` 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 [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=20080211220339.GZ155407@sgi.com \
--to=dgc@sgi.com \
--cc=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.