Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
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; } }