public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: XFS and XEN
Date: Thu, 19 Feb 2009 14:35:52 -0500	[thread overview]
Message-ID: <20090219193552.GB22736@infradead.org> (raw)
In-Reply-To: <93532303b1bb223328b2aaf712e0022f@webmail.zmi.at>

On Tue, Feb 17, 2009 at 03:00:39PM +0100, Michael Monnerie wrote:
> "Christoph Hellwig" <hch@infradead.org> schrieb:
> > I'm not even sure the Xen driver implements barriers.  I haven't done
> > much with Xen, but with the default kvm/qemu config I can completely
> > wreck ext3 and XFS filesystems.  If using these virtualization solutions
> > make sure you do not cache the virtual block device in the host
> > pagecache, and that in doubt the write cache of the disk is turned off
> > as barriers most likely won't work through the virtualization stack.
> 
> How can I do that?

Barriers are disabled using hdparm.  To make sure qemu/kvm doesn't
cache your image file specify cache=off on the command line specifying
that virtual disk.

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

  reply	other threads:[~2009-02-19 19:36 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 [this message]
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

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=20090219193552.GB22736@infradead.org \
    --to=hch@infradead.org \
    --cc=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