From: John Robinson <john.robinson@anonymous.org.uk>
To: Alexander Schreiber <als@thangorodrim.de>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: raid over ethernet
Date: Sat, 29 Jan 2011 21:54:55 +0000 [thread overview]
Message-ID: <4D448CAF.6020409@anonymous.org.uk> (raw)
In-Reply-To: <20110129210815.GC15784@mordor.angband.thangorodrim.de>
On 29/01/2011 21:08, Alexander Schreiber wrote:
> On Sat, Jan 29, 2011 at 12:23:14PM -0200, Denis wrote:
>> 2011/1/29 Alexander Schreiber<als@thangorodrim.de>
>>
>>>
>>> plain disk performance for writes, while reads should be reasonably
>>> close to the plain disk performance - drbd optimizes reads by just reading
>>> from the local disk if it can.
>>>
>>>
>> However, I have not used it with active-active fashion. Have you? if yes,
>> what is your overall experience?
>
> We are using drbd to provide mirrored disks for virtual machines running
> under Xen. 99% of the time, the drbd devices run in primary/secondary
> mode (aka active/passive), but they are switched to primary/primary
> (aka active/active) for live migrations of domains, as that needs the
> disks to be available on both nodes. From our experience, if the drbd
> device is healthy, this is very reliable. No experience with running
> drbd in primary/primary config for any extended period of time, though
> (the live migrations are usually over after a few seconds to a minute at
> most, then the drbd devices go back to primary/secondary).
Now that is interesting, to me at least. More as a thought experiment
for now, I was wondering how one would go about setting up a small
cluster of commodity servers (maybe 8 machines) running Xen (or perhaps
now KVM) VMs, such that if one (or potentially two) of the machines
died, the VMs could be picked up by the other machines in the cluster,
and only using locally-attached SATA/SAS discs in each machine.
I guess I'm talking about RAIN or RAIS rather than RAID so maybe I'd
better start reading the Wikipedia pages on those and not talk about it
on this list...
Cheers,
John.
next prev parent reply other threads:[~2011-01-29 21:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 1:58 raid over ethernet Roberto Spadim
2011-01-29 5:41 ` Jérôme Poulin
2011-01-29 6:42 ` Roberto Spadim
2011-01-29 13:29 ` Alexander Schreiber
2011-01-29 6:42 ` Mikael Abrahamsson
2011-01-29 6:44 ` Roberto Spadim
2011-01-29 6:48 ` Roberto Spadim
[not found] ` <AANLkTikdahgMoJjGr2otTS70LSM77GNpW_vAkZf15Kph@mail.gmail.com>
2011-01-29 11:47 ` Roberto Spadim
2011-01-29 13:34 ` Alexander Schreiber
[not found] ` <AANLkTi=6ridRPnHpfdOC=f2_ESndSARmQRkvT_shYO3s@mail.gmail.com>
2011-01-29 14:25 ` Denis
2011-01-29 21:08 ` Alexander Schreiber
2011-01-29 21:54 ` John Robinson [this message]
2011-01-29 23:04 ` Stan Hoeppner
2011-01-29 23:06 ` Miles Fidelman
2011-01-30 1:43 ` Alexander Schreiber
2011-01-31 8:42 ` Denis
2011-01-31 13:03 ` Alexander Schreiber
2011-01-31 14:45 ` Roberto Spadim
2011-01-31 16:15 ` Alexander Schreiber
2011-01-31 17:37 ` Roberto Spadim
2011-01-29 15:30 ` Spelic
2011-01-29 18:34 ` David Brown
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=4D448CAF.6020409@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=als@thangorodrim.de \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).