From: Michael Tokarev <mjt@tls.msk.ru>
To: Andi Kleen <andi@firstfloor.org>
Cc: Mark Lord <lkml@rtr.ca>,
Anton Ertl <anton@mips.complang.tuwien.ac.at>,
linux-kernel@vger.kernel.org
Subject: Re: Out-of-order writing by disk drives
Date: Tue, 14 Apr 2009 22:09:48 +0400 [thread overview]
Message-ID: <49E4D16C.7030809@msgid.tls.msk.ru> (raw)
In-Reply-To: <20090414175433.GY14687@one.firstfloor.org>
Andi Kleen wrote:
[]
> Where I see it as a problem is with virtualization; LVM seems to be the
> most sane way to manage file systems for lots of VMs and you likely
> want barriers there too.
Virtualisation is the best fit for partitionable raid1 arrays.
It is, in fact, what we have here -- I tested LVM but rejected
it because of this very issue - it does not support barriers.
And used partitions inside RAID1 arrays instead. It is not
that easy as with lvm (requires some work with numbers instead
of names, but that's again not that problematic if you think
about /dev/disk/by-name/...), and does not support resizing,
but again, this is not really a very necessary feature here
(easy to copy data to a new, larger place).
And by the way, here, extlinux comes very very handy. Inside
guests I don't use partitions but "whole disks", including
boot disk (/dev/vda for kvm). ext3fs on it, and extlinux to
boot it (works flawlessly on a partition-less device)
/mjt
next prev parent reply other threads:[~2009-04-14 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 20:04 Out-of-order writing by disk drives Anton Ertl
2009-04-14 14:10 ` Andi Kleen
2009-04-14 16:33 ` Anton Ertl
2009-04-14 17:24 ` Andi Kleen
2009-04-14 17:40 ` Mark Lord
2009-04-14 17:48 ` Michael Tokarev
2009-04-14 17:54 ` Andi Kleen
2009-04-14 18:09 ` Michael Tokarev [this message]
2009-04-14 18:50 ` Andi Kleen
2009-04-14 19:27 ` Chris Mason
2009-04-15 12:46 ` Jens Axboe
2009-04-17 19:46 ` Folkert van Heusden
2009-04-17 20:29 ` Andi Kleen
2009-04-17 21:07 ` Folkert van Heusden
2009-04-18 9:06 ` Anton Ertl
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=49E4D16C.7030809@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=andi@firstfloor.org \
--cc=anton@mips.complang.tuwien.ac.at \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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