From: Jamie Lokier <jamie@shareable.org>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: Christoph Hellwig <hch@lst.de>,
nikola.ciprich@linuxbox.cz, kopi@linuxbox.cz,
rusty@rustcorp.com.au, qemu-devel@nongnu.org,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: Notes on block I/O data integrity
Date: Wed, 26 Aug 2009 19:55:42 +0100 [thread overview]
Message-ID: <20090826185542.GE25726@shareable.org> (raw)
In-Reply-To: <20090825202508.GB4807@nik-comp.linuxbox.cz>
Nikola Ciprich wrote:
> clustered LVM SHOULD not have problems with it, as we're using just
> striped volumes,
Note that LVM does not implement barriers at all, except for simple
cases of a single backing device (I'm not sure if that includes
dm-crypt).
So your striped volumes may not offer this level of integrity.
-- Jamie
WARNING: multiple messages have this Message-ID (diff)
From: Jamie Lokier <jamie@shareable.org>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: kopi@linuxbox.cz, kvm@vger.kernel.org, rusty@rustcorp.com.au,
qemu-devel@nongnu.org, nikola.ciprich@linuxbox.cz,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] Re: Notes on block I/O data integrity
Date: Wed, 26 Aug 2009 19:55:42 +0100 [thread overview]
Message-ID: <20090826185542.GE25726@shareable.org> (raw)
In-Reply-To: <20090825202508.GB4807@nik-comp.linuxbox.cz>
Nikola Ciprich wrote:
> clustered LVM SHOULD not have problems with it, as we're using just
> striped volumes,
Note that LVM does not implement barriers at all, except for simple
cases of a single backing device (I'm not sure if that includes
dm-crypt).
So your striped volumes may not offer this level of integrity.
-- Jamie
next prev parent reply other threads:[~2009-08-26 18:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 18:11 Notes on block I/O data integrity Christoph Hellwig
2009-08-25 18:11 ` [Qemu-devel] " Christoph Hellwig
2009-08-25 19:33 ` Javier Guerra
2009-08-25 19:33 ` [Qemu-devel] " Javier Guerra
2009-08-25 19:36 ` Christoph Hellwig
2009-08-25 19:36 ` [Qemu-devel] " Christoph Hellwig
2009-08-26 18:57 ` Jamie Lokier
2009-08-26 18:57 ` Jamie Lokier
2009-08-26 22:17 ` Christoph Hellwig
2009-08-26 22:17 ` Christoph Hellwig
2009-08-27 9:00 ` Jamie Lokier
2009-08-25 20:25 ` Nikola Ciprich
2009-08-25 20:25 ` [Qemu-devel] " Nikola Ciprich
2009-08-26 18:55 ` Jamie Lokier [this message]
2009-08-26 18:55 ` Jamie Lokier
2009-08-27 0:15 ` Christoph Hellwig
2009-08-27 0:15 ` [Qemu-devel] " Christoph Hellwig
2009-08-27 10:51 ` Rusty Russell
2009-08-27 10:51 ` [Qemu-devel] " Rusty Russell
2009-08-27 13:42 ` Christoph Hellwig
2009-08-27 13:42 ` [Qemu-devel] " Christoph Hellwig
2009-08-28 2:03 ` Rusty Russell
2009-08-28 2:03 ` [Qemu-devel] " Rusty Russell
2009-08-27 14:09 ` [Qemu-devel] " Jamie Lokier
2009-08-27 14:09 ` Jamie Lokier
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=20090826185542.GE25726@shareable.org \
--to=jamie@shareable.org \
--cc=extmaillist@linuxbox.cz \
--cc=hch@lst.de \
--cc=kopi@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.