From: Alasdair G Kergon <agk@redhat.com>
To: Eli Malul <eli.malul@kaminario.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: mirrored device with thousand of mapping tableentries
Date: Mon, 28 Feb 2011 12:11:49 +0000 [thread overview]
Message-ID: <20110228121149.GA3626@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <E04C10E329E0CD40816C9C17AE53BBD3018639CE@kit001.kaminario.local>
On Mon, Feb 28, 2011 at 01:59:16PM +0200, Eli Malul wrote:
> The first few lines of the table I am loading:
> [root@vpc09 ~]# vi /tmp/mirror_table.txt
> 0 12 km_mirror core 2 8 nosync 2 /dev/loop0 0 /dev/loop1 0
> 12 12 km_mirror core 2 8 nosync 2 /dev/loop0 12 /dev/loop1 12
> 24 12 km_mirror core 2 8 nosync 2 /dev/loop0 24 /dev/loop1 24
> 36 12 km_mirror core 2 8 nosync 2 /dev/loop0 36 /dev/loop1 36
> 48 12 km_mirror core 2 8 nosync 2 /dev/loop0 48 /dev/loop1 48
> 60 12 km_mirror core 2 8 nosync 2 /dev/loop0 60 /dev/loop1 60
> 72 12 km_mirror core 2 8 nosync 2 /dev/loop0 72 /dev/loop1 72
> 84 12 km_mirror core 2 8 nosync 2 /dev/loop0 84 /dev/loop1 84
> 96 12 km_mirror core 2 8 nosync 2 /dev/loop0 96 /dev/loop1 96
> 108 12 km_mirror core 2 8 nosync 2 /dev/loop0 108 /dev/loop1 108
Why do you need this, rather than one mirror target covering the
whole device? (And if, unlike that example, your extents are not contiguous,
create two new devices that join them together, and mirror those. That's
what LVM does.)
Alasdair
next prev parent reply other threads:[~2011-02-28 12:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 11:21 mirrored device with thousand of mapping table entries Eli Malul
2011-02-28 11:48 ` Alasdair G Kergon
2011-02-28 11:59 ` mirrored device with thousand of mapping tableentries Eli Malul
2011-02-28 12:11 ` Alasdair G Kergon [this message]
2011-02-28 12:17 ` mirrored device with thousand of mappingtableentries Eli Malul
2011-02-28 13:10 ` Alasdair G Kergon
2011-02-28 13:13 ` Eli Malul
2011-02-28 13:29 ` Alasdair G Kergon
2011-02-28 13:42 ` Eli Malul
2011-02-28 16:25 ` Eli Malul
2011-02-28 13:38 ` Zdenek Kabelac
2011-02-28 15:01 ` Martin K. Petersen
2011-03-06 20:39 ` Zdenek Kabelac
2011-03-07 2:59 ` Martin K. Petersen
2011-03-07 14:24 ` Zdenek Kabelac
2011-03-07 16:09 ` Mike Snitzer
2011-03-08 6:51 ` Martin K. Petersen
2011-03-08 17:13 ` Mike Snitzer
2011-03-10 16:11 ` Martin K. Petersen
2011-03-11 16:53 ` [PATCH] block: Require subsystems to explicitly allocate bio_set integrity mempool (was: Re: mirrored device with thousand of mappingtableentries) Mike Snitzer
2011-03-11 17:11 ` [PATCH] block: Require subsystems to explicitly allocate bio_set integrity mempool Martin K. Petersen
2011-03-07 20:10 ` mirrored device with thousand of mappingtableentries Mike Snitzer
2011-03-07 20:22 ` Martin K. Petersen
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=20110228121149.GA3626@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=eli.malul@kaminario.com \
/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