Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi,
If you extend /dev/mapper/vg_foo-bar, then nothing changes, as you have to
resize the DRBD which could be done online if in connected state.
If you have LVM on top you have to extend the PV with the pvresize command,
and after this you may resize the filesystem on top.
If you have a normal Filesystem on top, you should resize this.
Best regards,
T. Baumann
tiri GmbH
Lauenburger Str. 31a
21493 Schwarzenbek
Tel. 04151 8674995
Fax. 04151 8674996
Net. http://www.tiri.li
Geschäftsführer: Anja Baumann, Thomas Baumann Sitz Schwarzenbek, Amtsgericht
Lübeck, HRB 8837 HL
-----Ursprüngliche Nachricht-----
Von: drbd-user-bounces at lists.linbit.com
[mailto:drbd-user-bounces at lists.linbit.com] Im Auftrag von Sam Przyswa
Gesendet: Mittwoch, 27. Oktober 2010 14:36
An: Mark Watts
Cc: drbd-user at lists.linbit.com
Betreff: Re: [DRBD-user] Before swap to DRBD
Le 27/10/2010 11:12, Mark Watts a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
>> Thanks a lot for your reply, but what you mean by "Using an LVM
>> volume for DRBD backing store" I'm very interested !
>>
> For example:
>
> resource r0 {
> on alice {
> device /dev/drbd1;
> disk /dev/mapper/vg_foo-bar;
> address 10.1.1.31:7789;
> meta-disk internal;
> }
> on bob {
> device /dev/drbd1;
> disk /dev/mapper/vg_foo-bar;
> address 10.1.1.32:7789;
> meta-disk internal;
> }
> }
>
> Where /dev/mapper/vg_foo-bar is an LVM Logical Volume.
>
> This is in contrast to using /drv/drbd1 as the basis for an LVM
> Physical Volume (ie: doing "pvcreate /dev/drbd1").
>
Yes, thanks !
Now I understand the difference but in this case what about if I extend the
size of the LVM logical volume "disk /dev/mapper/vg_foo_bar" ?
Sam.
_______________________________________________
drbd-user mailing list
drbd-user at lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user