[DRBD-user] drbd+device mapper drbd didn't start.

Lars Ellenberg lars.ellenberg at linbit.com
Sat May 17 00:37:46 CEST 2014

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

On Thu, May 15, 2014 at 12:03:55PM +0900, kad76oglz0qh at yahoo.co.jp wrote:
> Dear Lars
> Thank you for your answer.
> I will build next configuration.
> Primary   Storage1 -FC- DRBD-tgt(iSCSI target Driver)- iSCSI -Winodows2008R2
>                          |
>                         LAN
>                          |
> Secondary Srorage2 -FC- DRBD

That's all nice and shiny.
Then you simply do not want to see those "partitions"
(relevant only to your initiator box)
on the target.

Try to tell multipath/udev/kpartx
to *not* "automagically" create those
device mapper "partition" mappings.

How to do that may be distribution specific.

You can manually remove those mappings using
kpartx -d /dev/mapper/mpatha

There should be some option in mutlipath conf
to disable kpartx invocation,
but I don't remember from the top of my head,
and it may not be supported on all platforms (yet).

If nothing else helps, chmod -x kpartx ;-)

> I created partitions from Windows2008R first.
> Windows2008R created MS data partition(mpathap2) with MS reserved partition(mpathap1).
> I hope to replicate MS data(mpathp2) by DRBD.

: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
please don't Cc me, but send to list   --   I'm subscribed

More information about the drbd-user mailing list