From: "Felix E. Klee" <felix.klee@inka.de>
To: Iustin Pop <iusty@k1024.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: Data safety horror stories?
Date: Mon, 11 Feb 2008 22:23:09 +0100 [thread overview]
Message-ID: <1202764989.11126.1236296081@webmail.messagingengine.com> (raw)
In-Reply-To: <20080211171209.GA7567@teal.hq.k1024.org>
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
> 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?
> Be sure the read the FAQ, especially the section about write cache on
> dekstop/consumer HDDs.
You are probably referring to the following entry. I now disabled the
write cache of the 2nd HDD in Windows (remember my configuration). I
wonder though: Wouldn't it be possible to design journaling in a way so
that the write cache does never cause problems? Could someone provide an
example which illustrates the write cache problem in simple terms?
http://oss.sgi.com/projects/xfs/faq.html#wcache
> Just my opinion as an XFS user, your mileage might vary.
Hopefully, it's not about opinions ...
- Felix
--
Dipl.-Phys. Felix E. Klee
Naunynstr. 2, 76530 Baden-Baden, Germany
Tel.: +49 7221 396961, Fax: +49 7221 396960, Mobile: +49 174 1386060
http://www.linkedin.com/in/feklee
next prev parent reply other threads:[~2008-02-11 21:23 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 [this message]
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=1202764989.11126.1236296081@webmail.messagingengine.com \
--to=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 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.