From: christophe varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [dm-devel] raid10 ... (was: Re: ANNOUNCE: mdadm 1.7.0)
Date: Sat, 14 Aug 2004 11:51:41 +0200 [thread overview]
Message-ID: <1092477101.3576.3.camel@zezette> (raw)
In-Reply-To: <20040814041814.56d1e6c9.pegasus@nerv.eu.org>
That is what you get from a LVM2 setting with 1 VG containing all your
disks and mirrored LVs.
I didn't check lately, but PE allocators certainly need to be more
intelligent with regard to not allowing mirror members on the same spin.
regards,
cvaroqui
> Imagine having a pool of drives, where chunks of data are distributed evenly
> across all drives in a redundant manner. If one drive dies, the chunks that
> are not redundant anymore get their copies on the remaining drives, provided
> that there's enough space left; if one or more drives are added to the
> array, new chunks are written there until the balance is reached again.
>
> Disk space could be the first key for balancing across the drives, with
> transfer rate or seek time maybe added later. Maybe the pool could even
> adapt dinamically to the i/o patterns ...
>
> Am i dreaming (it's well over 4am here :) ? Or is something like this
> possible? Maybe not with a md personality, but by some daemon that would be
> taking care of a dm map?
>
next prev parent reply other threads:[~2004-08-14 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 2:29 ANNOUNCE: mdadm 1.7.0 - A tool for managing Soft RAID under Linux Neil Brown
2004-08-11 13:55 ` Jure Peèar
2004-08-11 23:04 ` Neil Brown
2004-08-14 2:18 ` raid10 ... (was: Re: ANNOUNCE: mdadm 1.7.0) Jure Peèar
2004-08-14 4:28 ` Guy
2004-08-14 9:51 ` christophe varoqui [this message]
2004-08-14 14:18 ` Mark Hahn
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=1092477101.3576.3.camel@zezette \
--to=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.com \
--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 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.