[Top] [All Lists]

Re: XFS and XEN

To: xfs@xxxxxxxxxxx
Subject: Re: XFS and XEN
From: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Sat, 21 Feb 2009 10:03:05 +0100
In-reply-to: <20090219193552.GB22736@xxxxxxxxxxxxx>
Organization: it-management http://it-management.at
References: <20090217091124.GA7118@xxxxxxxxxxxxx> <93532303b1bb223328b2aaf712e0022f@xxxxxxxxxxxxxx> <20090219193552.GB22736@xxxxxxxxxxxxx>
User-agent: KMail/1.10.3 (Linux/; KDE/4.1.3; x86_64; ; )
On Donnerstag 19 Februar 2009 Christoph Hellwig wrote:
> 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.

I have "nobarriers" for XFS, and a RAID controller with writeback cache. 
The "cache=off" seems to be for kvm only, so doesn't help me with XEN.

> 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.

Isn't that what "tap:aio" in XEN does?

I really want and need to find a secure way to run XEN clients. Is that 
data loss I had the fault of XFS, XEN or something else?

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: signature.asc
Description: This is a digitally signed message part.

<Prev in Thread] Current Thread [Next in Thread>