| Main Archive Page > Month Archives > drbd-user archives |
Re: [DRBD-user] drbd on lvm - resize pv (lvextend drbd)
From: ap <bitte_at_nospam>Date: Mon Oct 25 2010 - 19:18:58 GMT
To: Florian Haas <florian.haas@linbit.com>
Hello Florian,
in my special case it seems not to work.
I have the nested LVM like this.
# pvs
PV VG Fmt Attr PSize PFree
/dev/drbd1 replicated lvm2 a- 100,00G 56,05G
/dev/md1 localvg lvm2 a- 1,81T 1,67T
# lvs localvg
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
meta localvg -wi-a- 500,00M
r1 localvg -wi-ao 140,00G
(I changed the size of r1 from 100G to 140G)
# pvs /dev/drbd1
PV VG Fmt Attr PSize PFree
/dev/drbd1 replicated lvm2 a- 100,00G 56,05G
But the drbd1 does not change its size!!
So /dev/drbd1 is on disk /dev/localvg/r1
That means the undelying disk changed its size.
But a pvsresize /dev/drbd1 does not work - PSize remains 100G,
however, when using setphsicalvolumesize it does work.
# pvresize -v -d --setphysicalvolumesize 120G /dev/drbd1
Using physical volume(s) on command line
Archiving volume group "replicated" metadata (seqno 23).
WARNING: /dev/drbd1: Overriding real size. You could lose data.
/dev/drbd1: Pretending size is 251658240 not 209708344 sectors.
Resizing physical volume /dev/drbd1 from 25599 to 30719 extents.
Resizing volume "/dev/drbd1" to 251657856 sectors.
Updating physical volume "/dev/drbd1"
Creating volume group backup "/etc/lvm/backup/replicated" (seqno
24).
Physical volume "/dev/drbd1" changed
1 physical volume(s) resized / 0 physical volume(s) not resized
# pvs
/dev/drbd0: open failed: Falscher Medien-Typ
PV VG Fmt Attr PSize PFree
/dev/drbd1 replicated lvm2 a- 120,00G 76,05G
/dev/md1 localvg lvm2 a- 1,81T 1,67T
But when setting it to 140G it tells me, " Pretending size is 293601280
not 251657856 sectors."
That means my PV is bigger than the underlying LVM.
But even when setting the PSize to 120G, drbd does not recognize this:
# pvresize -v -d --setphysicalvolumesize 120G /dev/drbd1
Using physical volume(s) on command line
Archiving volume group "replicated" metadata (seqno 25).
WARNING: /dev/drbd1: Overriding real size. You could lose data.
/dev/drbd1: Pretending size is 251658240 not 293600896 sectors.
Resizing physical volume /dev/drbd1 from 35839 to 30719 extents.
Resizing volume "/dev/drbd1" to 251657856 sectors.
Updating physical volume "/dev/drbd1"
Creating volume group backup "/etc/lvm/backup/replicated" (seqno
26).
Physical volume "/dev/drbd1" changed
1 physical volume(s) resized / 0 physical volume(s) not resized
# drbdadm -- resize drbd.drbd1
# cat /proc/drbd
version: 8.3.7 (api:88/proto:86-91)
GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by
phil@fat-tyre, 2010-01-13 17:17:27
0: cs:Unconfigured
1: cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown C r----
ns:0 nr:0 dw:312 dr:4876 al:2 bm:1 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b
oos:104854364
As you see - still 100G (oos) :-(
Offline is not possible as the nested LVM is in use.
# drbdadm down drbd.drbd1
1: State change failed: (-12) Device is held open by someone
Command 'drbdsetup 1 down' terminated with exit code 11
Do you have any hint for me, how to solve this?
Thanks,
ap.
On Mon, 25 Oct 2010 16:50:47 +0200, Florian Haas
<florian.haas@linbit.com> wrote:
> On 2010-10-25 16:17, ap wrote:
>>
>> Hello list,
>>
>> according to <http://www.drbd.org/users-guide/s-nested-lvm.html> I
>> created a nested drbd/lvm resource.
>> But - how can the drbd device extended?
>
> http://lmgtfy.com/?q=resize+drbd&l=1
>
> It's right at the top.
>
> Florian
_______________________________________________
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user