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

kad76oglz0qh at yahoo.co.jp kad76oglz0qh at yahoo.co.jp
Thu May 15 05:03:55 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.


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

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.

Please help me


--- On Wed, 2014/5/14, Lars Ellenberg <lars.ellenberg at linbit.com> wrote:

On Wed, May 14, 2014 at 02:07:21PM +0900, kad76oglz0qh at yahoo.co.jp wrote:
> Dear Lars
> 
> Thank you for your answer.
> 
> >Something already claimed mapatha.
> >Maybe you need to exclude kpartx from mapping internal partitions,
> >or adjust the lvm filter to exclude that device.
> 
> >What's supposed to be on that device?
> >File system? VM image? LVM PV?
> 
> I didn't use LVM.
> 
> device are /dev/sda and /dev/sdb.
> # df
> Filesystem           1K-ブロック    使用   使用可 使用% マウント位置
> /dev/sdc3             10079084   6286048   3281036  66% /
> tmpfs                  6158340        88   6158252   1% /dev/shm
> /dev/sdc1               198337     51717    136380  28% /boot
> /dev/sdc5            100125432  12501716  82537548  14% /home
> 
> # chkconfig --list multipathd
> multipathd      0:off   1:off   2:off   3:off   4:off   5:off   6:off
> 
> But I reboot system and I checked under /dev/mapper.
> #ls /dev/mapper
> controll mpatha mpathap1 mpathap2

That's your problem right there.

mpathap1 and p2 are device mapper targets created by kpartx
on top of the multipath target mpatha.
These claim mpatha (correctly),
thereby preventing DRBD from claiming them.

If that was not the case, you would have both
the partition mappings and DRBD accessing the lower level devices,
concurrently, but only DRBD would replicate,
the partition mappings would bypass DRBD,
and you'd become soon very very disappointed
(and likely would blame DRBD...).


Why did you think you want partitions there?

Did you mean to have DRBD use one of those partitions?

I suggest you either use one DRBD per "partition",
or you get rid of the partitions completely
and put DRBD on the whole device.

If you need "partitions" inside of one DRBD
I recommend to use DRBD as PV (physical volume)
for a LVM VG (volume group).

Hth,
    Lars

> I started drbd. Same error occured.
> 
> 
> 
> 
> --- On Tue, 2014/5/13, Lars Ellenberg <lars.ellenberg at linbit.com> wrote:
> 
> On Thu, May 08, 2014 at 06:43:58PM +0900, kad76oglz0qh at yahoo.co.jp wrote:
> > Hi everybody
> > 
> > I set up device-mapper under centOS6.3.
> > I started drbd but drbd didn't start.
> > 
> > #/etc/rc.d/init.d/drbd start
> > Starting DRBD resources: [
> >      create res: r0
> >    prepare disk: r0
> >     adjust disk: r0:failed(attach:10)
> >      adjust net: r0
> > ]....
> > 
> > multipath
> > # multipath -ll
> > mpatha dm-0 IFT,DS S16F-R1440
> > size=7.6T features='0' hwhandler='0' wp=rw
> > |-+- policy='round-robin 0' prio=1 status=active
> > | `- 5:0:0:0  sdb 8:16 active ready  running
> > `-+- policy='round-robin 0' prio=1 status=enabled
> >   `- 1:0:0:0  sda 8:0  active ready  running
> > 
> > /etc/multipath.conf
> > defaults {
> >         user_friendly_names yes
> > }devices {
> >        device {
> >                vendor                  "IFT    "
> >                product                 "DS S16F-R1440"
> >                path_grouping_policy    multibus
> >                #path_grouping_policy    failover
> >                getuid_callout          "/lib/udev/scsi_id --whitelisted --device
> > =/dev/%n"
> >                path_checker            readsector0
> >                path_selector           "round-robin 0"
> >                hardware_handler        "0"
> >                failback                15
> >                rr_weight               priorities
> >                no_path_retry           15
> >                #no_path_retry           queue
> >        }
> > }
> > blacklist{
> >          devnode "^drbd*"
> > #         devnode *
> >          device {
> >                 vendor "SEAGATE"
> >                 product "*"
> >                 }
> >          device {
> >                 vendor "Dell"
> >                 product "*"
> >                 }
> >          device {
> >                 vendor ""iDRAC
> >                 product "*"
> >                 }
> >          }
> > 
> > drbd Ver8.4.4
> > 
> > /etc/drbd.conf
> > 
> > # more /etc/drbd.conf
> > #
> > # please have a a look at the example configuration file in
> > # /usr/share/doc/drbd83/drbd.conf
> > #
> > common {
> >        disk {
> >             max-bio-bvecs 1;
> >             #on-io-error call-local-io-erro;
> >             }
> > }
> > 
> > resource r0 {
> >   protocol C;
> > 
> > 
> >  net {
> >    sndbuf-size 512K;
> >    ping-int 10;
> >    ping-timeout 10;
> >    connect-int 10;
> >    timeout 80;
> >    ko-count 0;
> >    max-buffers 8000;
> >    max-epoch-size 8000;
> >   }
> > 
> > syncer {
> >   rate 80M;
> >   verify-alg md5;
> >   al-extents 3833;
> > }
> > 
> >   on centos1 {
> >    device     /dev/drbd0;
> >    disk       /dev/mapper/mpatha;
> >    address    172.26.24.153:7790;
> >    flexible-meta-disk /dev/sdc6;
> >   }
> >   on centos2 {
> >    device     /dev/drbd0;
> >    disk       /dev/mapper/mpatha;
> >    address    172.26.24.155:7790;
> >    flexible-meta-disk /dev/sdc6;
> >   }
> > }
> > 
> > /var/log/messages
> > May  8 16:16:56 centos1 kernel: drbd: initialized. Version: 8.4.4 (api:1/proto:86-101)
> > May  8 16:16:56 centos1 kernel: drbd: GIT-hash: 74402fecf24da8e5438171ee8c19e28627e1c98a build by root at centos63, 2014-04-25 21:53:13
> > May  8 16:16:56 centos1 kernel: drbd: registered as block device major 147
> > May  8 16:16:56 centos1 kernel: drbd r0: Starting worker thread (from drbdsetup [5231])
> > May  8 16:16:56 centos1 kernel: block drbd0: open("/dev/mapper/mapatha") failed with -16
> 
> Something already claimed mapatha.
> Maybe you need to exclude kpartx from mapping internal partitions,
> or adjust the lvm filter to exclude that device.
> 
> What's supposed to be on that device?
> File system? VM image? LVM PV?
> 
> > May  8 16:16:56 centos631 kernel: block drbd0: drbd_bm_resize called with capacity == 0
> > May  8 16:16:56 centos631 kernel: drbd r0: Terminating drbd_w_r0
> > 
> > Please help me.
> > 
> > Regards
> > Masahiko Kawase
> 
> 
> -- 
> : 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
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user

> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user


-- 
: 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
_______________________________________________
drbd-user mailing list
drbd-user at lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20140515/dc14e3d6/attachment.htm>


More information about the drbd-user mailing list