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: Wed, 4 Mar 2009 03:42:53 +0100	[thread overview]
Message-ID: <200903040342.53587@zmi.at> (raw)
In-Reply-To: <20090224163823.GA19811@infradead.org>

I just got this info at XEN:
> LVM does not honor write-barriers.

Then I searched and found a thread were Eric also talked:
http://lkml.org/lkml/2008/5/16/390
http://hightechsorcery.com/2008/06/linux-write-barriers-write-caching-
lvm-and-filesystems

If I understand correctly, turning off disk cache write cache should be 
enough to be save, even when using LVM. Is it really XEN that messed the 
disk, or something else? Could the Areca controller driver do something 
wrong? I'd really love to get a stable and data-secure system, as you 
might understand.

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

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

      parent reply	other threads:[~2009-03-04  2:43 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
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 [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=200903040342.53587@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