public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: "Felix E. Klee" <felix.klee@inka.de>
Cc: Iustin Pop <iusty@k1024.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Data safety horror stories?
Date: Tue, 19 Feb 2008 09:50:43 +1100	[thread overview]
Message-ID: <20080218225043.GQ155407@sgi.com> (raw)
In-Reply-To: <1202764989.11126.1236296081@webmail.messagingengine.com>

On Mon, Feb 11, 2008 at 10:23:09PM +0100, Felix E. Klee wrote:
> Hi Justin,
> 
> thanks for the info!
> 
> On Mon, 11 Feb 2008 18:12:09 +0100, "Iustin Pop" <iusty@k1024.org> said:
> > No, XFS will not lose any data that the application has committed to
> > the disk.
> 
> OK, but just to make sure: The following FAQ entry refers only to
> *newly* created files - right?
> 
> http://oss.sgi.com/projects/xfs/faq.html#nulls

No - it can affect an file where the write is extending the file.
The NULLs problem should be very rare now - we've fixed the common
causes of this problem....

> > Improperly written applications and/or improperly configured systems
> > might have issues with recently written files losing data.
> 
> Again, just to make sure that I understood you correctly: Could you name
> an example?

I suggest watching the video of this talk from the 2007 linux.conf.au:

http://lca2007.linux.org.au/talk/278.html

It's all about how applications do stupid stuff that can lose data.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  parent reply	other threads:[~2008-02-18 22:50 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 [this message]
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=20080218225043.GQ155407@sgi.com \
    --to=dgc@sgi.com \
    --cc=felix.klee@inka.de \
    --cc=iusty@k1024.org \
    --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