Felix, Thanks for the reply. Believe me, I tried all of the tricks in the hat without any luck. Finally, I decided to resize the partitions and instead of carving out space from the volume group, I created a new partition “sda3”. That did the trick. Other than one been an LVM and the other a regular partition, not sure why the first time it didn’t work.
[root@aus-ha1-srv ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 500M 0 part /boot ├─sda2 8:2 0 436G 0 part │ ├─vg1-lv_root (dm-0) 253:0 0 50.8G 0 lvm / │ ├─vg1-lv_swap (dm-1) 253:1 0 5.9G 0 lvm [SWAP] │ ├─vg1-lv_var (dm-2) 253:2 0 359.8G 0 lvm /var │ └─vg1-lv_home (dm-3) 253:3 0 19.5G 0 lvm /home └─sda3 8:3 0 29.3G 0 part Thanks, Jaime On 7/29/14, 3:48 AM, "Felix Frank" <[email protected]> wrote: >On 07/22/2014 09:47 PM, Colom, Jaime wrote: >> # mkfs.ext4 /dev/sda3 >> >> # drbdadm create-md clusterdb_res > >You are creating a filesystem on the backing device. There is literally >no reason to do that. Defer that step to after DRBD initialization. > >DRBD even spells out your options: > >On 07/22/2014 09:47 PM, Colom, Jaime wrote:> You need to either >> >> * use external meta data (recommended) >> >> * shrink that filesystem first >> >> * zero out the device (destroy the filesystem) > >You want to pick the latter. > >Regards, >Felix _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
