Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
> Le 2016-01-22 à 16:34, Ricardo Branco <ricardo at wenn.com> a écrit :
>
> Give vgdisplay and pvdisplay.
[root at db1 ~]# vgdisplay
--- Volume group ---
VG Name mysqldata0
System ID
Format lvm2
Metadata Areas 3
Metadata Sequence No 6
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 3
Act PV 3
VG Size 119,98 GiB
PE Size 4,00 MiB
Total PE 30716
Alloc PE / Size 30461 / 118,99 GiB
Free PE / Size 255 / 1020,00 MiB
VG UUID vBpnT5-BYr7-5YnX-WhmK-MSSn-H1e1-K8jKJp
[root at db1 ~]# pvdisplay
--- Physical volume ---
PV Name /dev/xvdb
VG Name mysqldata0
PV Size 20,00 GiB / not usable 4,00 MiB
Allocatable yes
PE Size 4,00 MiB
Total PE 5119
Free PE 255
Allocated PE 4864
PV UUID tpi7HM-DWpk-ghjH-7X02-tnEd-e9zL-TZKllc
--- Physical volume ---
PV Name /dev/xvdc1
VG Name mysqldata0
PV Size 19,99 GiB / not usable 1,43 MiB
Allocatable yes (but full)
PE Size 4,00 MiB
Total PE 5118
Free PE 0
Allocated PE 5118
PV UUID kgXx4D-Awq0-6LBa-gsGe-IxM7-GL00-lq8BcH
--- Physical volume ---
PV Name /dev/xvde1
VG Name mysqldata0
PV Size 80,00 GiB / not usable 1,35 MiB
Allocatable yes (but full)
PE Size 4,00 MiB
Total PE 20479
Free PE 0
Allocated PE 20479
PV UUID NSILm6-a9LT-JxxP-JF7r-8mZo-EiRB-YktHwH
--- Physical volume ---
PV Name /dev/xvda2
VG Name VG
PV Size 29,51 GiB / not usable 11,00 MiB
Allocatable yes (but full)
PE Size 32,00 MiB
Total PE 944
Free PE 0
Allocated PE 944
PV UUID clH3oy-w3Jt-96H1-A1Jd-OydP-dDAl-jyGyxZ
> Did you add additional disk to your VG then expand the LV before you did drbd resize?
Yep.
>
> Sent from my BlackBerry 10 smartphone.
> Original Message
> From: Pascal Robert
> Sent: Friday, 22 January 2016 21:30
> To: drbd-user at lists.linbit.com
> Subject: [DRBD-user] Can't grow my DRBD device
>
> Hi,
>
> I’m running DRBD on both of a LVM volume. Disk space was lacking, so I added a (virtual) disk, grow the LVM but calling « drbdadmin resize mysqldata » don’t do anything. And yes, the LVM was augmented on both nodes. Any steps missing (according to my googling, growing the LVM and calling "drbdadm resize mysqldata" should be enough)?
>
> [root at db1 ~]# lvdisplay
> --- Logical volume ---
> LV Path /dev/mysqldata0/drbd-main
> LV Name drbd-main
> VG Name mysqldata0
> LV UUID QeQP4s-mrLT-5DBi-qkyK-Km30-lvIY-J2Xl7M
> LV Write Access read/write
> LV Creation host, time localhost.localdomain, 2015-06-19 10:43:29 -0400
> LV Status available
> # open 2
> LV Size 118,99 GiB
> Current LE 30461
> Segments 3
> Allocation inherit
> Read ahead sectors auto
> - currently set to 256
> Block device 253:2
>
> [root at db1 ~]# drbd-overview
> 0:mysqldata/0 Connected Primary/Secondary UpToDate/UpToDate /data/mysql ext4 39G 2.0G 35G 6%
>
> [root at db1 ~]# drbdadm resize mysqldata
>
> [root at db1 ~]# cat /proc/drbd
> version: 8.4.6 (api:1/proto:86-101)
> GIT-hash: 833d830e0152d1e457fa7856e71e11248ccf3f70 build by phil at Build64R6, 2015-04-09 14:35:00
> 0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r-----
> ns:97670132 nr:0 dw:36839300 dr:102839901 al:8282 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:f oos:0
>
> [root at db1 ~]# cat /etc/drbd.d/mysqldata.res
> resource mysqldata {
> options {
> on-no-data-accessible suspend-io;
> }
> net {
> cram-hmac-alg "sha1";
> shared-secret "XXXXXXXX";
> protocol C;
> }
>
> on db1.druide {
> address 10.6.79.20:7788;
> device /dev/drbd0;
> disk /dev/mysqldata0/drbd-main;
> meta-disk internal;
> }
> on db2.druide {
> address 10.6.79.21:7788;
> device /dev/drbd0;
> disk /dev/mysqldata0/drbd-main;
> meta-disk internal;
> }
> }
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>