[DRBD-user] drbd attach failure - (104) Can not open backing device

[Mateusz Kalisiak]

Hi,

thanks for replay. I tried to use LV as well (configuration shown below)
with the same effect.
What do you mean by "You may have blasted your LV signatures"? This is fresh
RHEL 5.6 installation,
the partition layout is almost default (I've just added a few logical
volumes).

# r0.res
global {
        usage-count yes;
}
common {
        protocol C;
}
resource r0 {
        on app1 {
                device      /dev/drbd0;
                disk        /dev/VolGroup00/LogVol02;
                address     192.168.1.106:7789

;
                meta-disk   internal;
        }
        on app2 {
                device      /dev/drbd0;
                disk        /dev/VolGroup00/LogVol02;
                address     192.168.1.107:7789

;
                meta-disk   internal;
        }
}

Best Regards,

Mateusz

2011/3/28 Felix Frank <ff at mpexnet.de>

> Hi,
>
> > Found LVM2 physical volume signature
> >      8257536 kB data area apparently used
> >      8281212 kB left usable by current configuration
> > ...
> >    Device Boot      Start         End      Blocks   Id  System
> > /dev/sda1   *           1          13      104391   83  Linux
> > /dev/sda2              14        1044     8281507+  8e  Linux LVM
>
> while this does not necessarily mean that sda2 is an LVM PV, the above
> message sure indicates that.
>
> You may have blasted your LV signatures? I'm not sure.
>
> I believe you either want to get rid of LVM here, or use an LV as a
> backing device (instead of sda2).
>
> HTH,
> Felix
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110328/32d7ef18/attachment.htm>