public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Geir A. Myrestrand" <geir.myrestrand@falconstor.com>
To: xfs@oss.sgi.com
Subject: Re: Questions about XFS
Date: Thu, 15 Mar 2007 10:41:37 -0400	[thread overview]
Message-ID: <45F95B21.9040603@falconstor.com> (raw)
In-Reply-To: <200703151007.32630.clflush@chello.be>

clflush wrote:
> On the one hand you have the old Ext3 FS which doesn't perform very well in 
> many areas but IMO is a lot safer to work on (doesn't loose data that easily 
> compared to XFS - and I'm talking from experience here because I use both 
> file systems and I lost much more on the XFS system than on the Ext3 one) and 
> on the other hand you have this excellent XFS file system with its clean 
> layout and awesome performance + fancy features like GRIO, extents, allocate 
> on flush, real time volumes, etc *but* is not "safe" enough to work with if 
> you have unreliable hardware and/or a lot of power outage issues  - I've 
> never lost data on Ext3 during a power outage but already lost 2 times data 
> on XFS

You *always* use a UPS when you use XFS.
XFS does not prevent power outages [yet]...

> Just my $0.02

Save them for a UPS. ;-)

-- 

Geir A. Myrestrand

  reply	other threads:[~2007-03-15 14:59 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-13 13:40 Questions about XFS clflush
2007-03-13 15:36 ` Klaus Strebel
2007-03-13 15:53 ` Stein M. Hugubakken
2007-03-13 15:55 ` Eric Sandeen
2007-03-14 16:33 ` Stewart Smith
2007-03-15  4:26   ` Taisuke Yamada
2007-03-15  9:07     ` clflush
2007-03-15 14:41       ` Geir A. Myrestrand [this message]
2007-03-16 10:36       ` Martin Steigerwald
2007-03-17  0:47         ` Jason White
2007-03-29 15:07           ` cache flush support in SATA drives (was: Re: Questions about XFS) Martin Steigerwald
  -- strict thread matches above, loose matches on Subject: below --
2013-06-11  9:56 Questions about XFS Steve Bergman
2013-06-11 13:10 ` Emmanuel Florac
2013-06-11 13:35 ` Stefan Ring
2013-06-11 13:52 ` Ric Wheeler
2013-06-11 13:59 ` Ric Wheeler
2013-06-11 16:12   ` Steve Bergman
2013-06-11 17:19     ` Ric Wheeler
2013-06-11 17:27       ` Stefan Ring
2013-06-11 17:31         ` Ric Wheeler
2013-06-11 17:41           ` Stefan Ring
2013-06-11 18:03             ` Eric Sandeen
2013-06-11 19:30           ` Steve Bergman
2013-06-11 21:03             ` Dave Chinner
2013-06-11 21:43               ` Steve Bergman
2013-06-11 17:59         ` Ben Myers
2013-06-11 17:28     ` Eric Sandeen
2013-06-11 19:17       ` Steve Bergman
2013-06-11 21:47         ` Dave Chinner
2013-07-22 14:59       ` Steve Bergman
2013-07-22 15:16         ` Steve Bergman
2013-06-12  8:26     ` Roger Oberholtzer
2013-06-12 10:34       ` Ric Wheeler
2013-06-12 13:52         ` Roger Oberholtzer
2013-06-12 12:12       ` Stan Hoeppner
2013-06-12 13:48         ` Roger Oberholtzer
2013-06-13  0:48       ` Dave Chinner
2013-06-11 19:35 ` Ben Myers
2013-06-11 19:55   ` Steve Bergman
2013-06-11 20:08     ` Ben Myers
2013-06-11 21:57     ` Matthias Schniedermeyer
2013-06-11 22:18       ` Steve Bergman
2013-10-25 14:28 harryxiyou
2013-10-25 14:42 ` Emmanuel Florac
2013-10-25 14:57   ` Eric Sandeen
2013-10-25 16:24     ` harryxiyou
2013-10-25 16:44     ` harryxiyou
2013-10-26 10:41     ` Stan Hoeppner
2013-10-27  3:29       ` Eric Sandeen
2013-10-25 16:13   ` harryxiyou
2013-10-25 16:16     ` Eric Sandeen

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=45F95B21.9040603@falconstor.com \
    --to=geir.myrestrand@falconstor.com \
    --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