From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: NeilBrown <neilb@suse.de>, Mike Snitzer <snitzer@redhat.com>,
linux-raid@vger.kernel.org, agk@redhat.com
Subject: Re: [dm-devel] [PATCH v3 0/8] dm-raid (raid456) target
Date: Thu, 06 Jan 2011 10:56:07 -0500 [thread overview]
Message-ID: <4D25E617.70509@cfl.rr.com> (raw)
In-Reply-To: <20110106214645.2bd321f4@notabene.brown>
On 1/6/2011 5:46 AM, NeilBrown wrote:
> 3: <#raid_devs> <meta_dev1> <dev1> .. <meta_devN> <devN>
Let me get this straight. You specify a separate device to hold the
metadata and write intent bitmap for each data device? So for a 3 disk
raid 5, lvm will need to create two logical volumes on each of the 3
physical volumes, one of which will only be a single physical extent,
and will hold the raid metadata and write intent bitmap?
Why not just store the metadata on the main device like mdadm does today?
next prev parent reply other threads:[~2011-01-06 15:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 2:37 [PATCH v3 0/8] dm-raid (raid456) target Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 1/8] md/bitmap: revert dm-dirty-log preparation Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 2/8] md/bitmap: use DIV_ROUND_UP in bitmap_init_from_disk Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 3/8] md/raid5: use sysfs_notify_dirent_safe to avoid NULL pointer Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 4/8] dm raid: skeleton raid456 target support Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 5/8] dm: introduce target callbacks and congestion callback Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 6/8] dm: per-target unplug callback support Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 7/8] dm raid: add iterate_devices and io_hints functions Mike Snitzer
2010-12-21 2:37 ` [PATCH v3 8/8] dm raid: add suspend and resume functions Mike Snitzer
2010-12-21 3:14 ` [PATCH v3 0/8] dm-raid (raid456) target Neil Brown
2011-01-05 22:36 ` Mike Snitzer
2011-01-06 10:46 ` NeilBrown
2011-01-06 14:43 ` Jonathan Brassow
2011-01-10 0:37 ` NeilBrown
2011-01-10 20:14 ` Jonathan Brassow
2011-01-06 15:56 ` Phillip Susi [this message]
2011-01-06 20:59 ` [dm-devel] " Jonathan Brassow
2011-01-06 21:01 ` Jonathan Brassow
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=4D25E617.70509@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=snitzer@redhat.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;
as well as URLs for NNTP newsgroup(s).