> -----Original Message----- > From: drbd-user-boun...@lists.linbit.com [mailto:drbd-user- > boun...@lists.linbit.com] On Behalf Of Robert Altnoeder > Sent: Thursday, July 26, 2018 5:12 AM > To: drbd-user@lists.linbit.com > Subject: Re: [DRBD-user] drbd+lvm no bueno > > On 07/26/2018 08:50 AM, Eric Robinson wrote: > > > > > > Failed Actions: > > > > * p_lv_on_drbd1_start_0 on ha16b 'not running' (7): call=68, > > status=complete, exitreason='LVM: vg_on_drbd1 did not activate > > correctly', > > > > last-rc-change='Wed Jul 25 22:36:37 2018', queued=0ms, exec=401ms > > > > > > > > The storage stack is: > > > > > > > > md4 -> drbd -> lvm -> filesystem > > > > This is most probably an LVM configuration error. Any LVM volume group on > top of DRBD must be deactivated/stopped whenever DRBD is Secondary and > must be started whenever DRBD is Primary, and LVM must be prevented from > finding and using the storage device that DRBD uses as its backend, which it > would normally do, because it can see the LVM physical volume signature not > only on the DRBD device, but also on the backing device that DRBD uses. >
Would there really be a PV signature on the backing device? I didn't turn md4 into a PV (did not run pvcreate /dev/md4), but I did turn the drbd disk into one (pvcreate /dev/drbd1). -Eric _______________________________________________ drbd-user mailing list drbd-user@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user