From: "Bryn M. Reeves" <bmr@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: partitioning multipath device
Date: Mon, 25 Jan 2010 12:32:25 +0000 [thread overview]
Message-ID: <1264422745.8461.5559.camel@localhost> (raw)
In-Reply-To: <20100122192935.GC31538@mtholyoke.edu>
On Fri, 2010-01-22 at 14:29 -0500, Ron Peterson wrote:
> The multipath-tools FAQ has the following to say about partitioning
> multipath devices.
>
> >From http://christophe.varoqui.free.fr/faq.html
>
> > 6. How do I partition my multipathed devices
> > Partition a constituant path instead. And reload the map through multipath(8)
>
> I take this to mean, for example, that one should partition /dev/sdX,
> rather than the corresponding coalesced /dev/mapper/... device, correct?
>
> My question is: why? Paritioning the /dev/mapper device appears to
> work. Is there an operational difference? I've always done this
> exactly as advised, but I know someone who didn't, and we're wondering
> if it matters.
It doesn't actually matter too much. If you're partitioning before
assembling maps then you may as well do it on a path. The common
partitioning tools should do the right thing if you point them at the
multipath device too though (although you may need to arrange for kpartx
to get run again, or run it manually to refresh).
Regards,
Bryn.
prev parent reply other threads:[~2010-01-25 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 19:29 partitioning multipath device Ron Peterson
2010-01-22 19:53 ` Christophe Varoqui
2010-01-25 12:32 ` Bryn M. Reeves [this message]
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=1264422745.8461.5559.camel@localhost \
--to=bmr@redhat.com \
--cc=dm-devel@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 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.