public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: XFS and XEN
Date: Tue, 24 Feb 2009 16:04:24 +0100	[thread overview]
Message-ID: <200902241604.29566@zmi.at> (raw)
In-Reply-To: <200902170959.55077@zmi.at>


[-- Attachment #1.1: Type: text/plain, Size: 2165 bytes --]

On Dienstag 17 Februar 2009 Michael Monnerie wrote:
> Now I'm sure that the following configuration can destroy a
> PostgreSQL 8.3.5 database:
>
> * Linux host with XEN, XFS filesystem with "nobarrier", RAID
> controller with battery backed cache.
> * XEN vm with XFS filesystem with "nobarrier" with postgresql
> * your daughter with 3.5 years switching off the power supply of the
> server

I got this answer on the XEN list. It looks like XFS in not very secure. 
Do you share that opinion? I am still searching for a way to make sure 
the above never happens again. Should I use ext3/reiserfs/ocfs2 within a 
XEN domU, or is it not the fault of XFS my database got destroyed? Don't 
want to blame anyone, but I need a secure environment for the machines 
that should be in production soon, don't have time to recover databases 
or whatever just because of a crash.

from XEN list:
********************************************
if you don't have highly reliable hardware, with redundant channels and 
battery backed caches, etc. stay away from XFS.

it's a pity, but XFS is only as reliable as the hardware you give it.  
in other words: you can be really sure that a software issue won't trash 
your XFS filesystem; but also that a hardware failure definitely will.

ext3, OTOH, might not have such an impressive record of correctness; but 
it's designed with redundancy in mind.  almost all vital structures are 
either replicated or reconstructable from other hints.  that makes fsck 
slow but effective, and in most cases, the journal analysis done when 
remounting after an unclean shutdown is enough to put it back on track.

i sure wish i could use XFS in more circumstances, but the needed 
hardware is prohibitive.
********************************************

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4


[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2009-02-24 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17  8:59 XFS and XEN Michael Monnerie
2009-02-17  9:11 ` Christoph Hellwig
2009-02-17 14:00   ` Michael Monnerie
2009-02-19 19:35     ` Christoph Hellwig
2009-02-21  9:03       ` Michael Monnerie
2009-02-24 15:04 ` Michael Monnerie [this message]
2009-02-24 16:38   ` Christoph Hellwig
2009-02-25  6:40     ` Michael Monnerie
2009-03-05  6:44       ` Michael Monnerie
2009-03-03 20:56     ` Michael Monnerie
2009-03-04  2:42     ` Michael Monnerie

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=200902241604.29566@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --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