Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
You did resize the LV on both systems right?
James Doherty wrote:
> I've set up a pair of machines running Debian Sarge. These machines have
> DRBD 0.7.10 running on top of an LVM2 device. I'm using the 2.6.8-2
> debian kernel and the filesystems on top of my DRBD resources use XFS.
>
> I tested out online resizing just now and everything went smoothly.
> However, when I attempted to do this again, DRBD didn't recognise that I
> had increased the size of the LVM volume. Below is what happens when I
> try subsequent resizes (after I have already resized the LVM volume).
>
> --- Logical volume ---
> LV Name /dev/vg00/xfs
> VG Name vg00
> LV UUID d9CWwx-Dvzp-IHor-h9NC-KMVF-kjkn-FskHaq
> LV Write Access read/write
> LV Status available
> # open 2
> LV Size 3.00 GB
> Current LE 1024
> Segments 1
> Allocation inherit
> Read ahead sectors 0
> Block device 254:1
>
> As you can see, the LV size is 3gb. This has been increased from 2gb.
>
> When running "drbdadm resize r0", I get the following:
>
> drbd0: I am(P): 1:00000004:00000001:00000008:00000002:11
> drbd0: Peer(S): 1:00000004:00000001:00000008:00000002:01
> drbd0: drbd0_receiver [2157]: cstate Connected --> WFBitMapS
> drbd0: drbd0_receiver [2157]: cstate WFBitMapS --> SyncSource
> drbd0: Resync started as SyncSource (need to sync 0 KB [0 bits set]).
> drbd0: Resync done (total 1 sec; paused 0 sec; 0 K/sec)
> drbd0: drbd0_receiver [2157]: cstate SyncSource --> Connected
>
> When I resized initially, DRBD also showed the new size of the LVM
> volume. No resync takes place (nothing to sync).
>
> cisco:~# df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/hda1 1.8G 623M 1.1G 37% /
> tmpfs 62M 0 62M 0% /dev/shm
> /dev/drbd0 1.9G 17M 1.9G 1% /mnt/xfs
>
> The partition is still stuck at 2gb. Trying to grow the filesystem does
> nothing:
>
> cisco:~# xfs_growfs /mnt/xfs/
> meta-data=/mnt/xfs isize=256 agcount=18, agsize=28672
> blks
> = sectsz=512
> data = bsize=4096 blocks=491520, imaxpct=25
> = sunit=0 swidth=0 blks, unwritten=1
> naming =version 2 bsize=4096
> log =internal bsize=4096 blocks=1200, version=1
> = sectsz=512 sunit=0 blks
> realtime =none extsz=65536 blocks=0, rtextents=0
>
> cisco:~# df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/hda1 1.8G 623M 1.1G 37% /
> tmpfs 62M 0 62M 0% /dev/shm
> /dev/drbd0 1.9G 17M 1.9G 1% /mnt/xfs
>
> As you can see, the XFS filesystem is still only 2gb. I'm puzzled why
> this worked initially (resizing from 1gb filesystem -> 2gb filesystem)
> but now DRBD doesn't seem to realise that the logical volume has
> increased in size. I've restarted the machines just to make sure it
> wasn't some funky LVM thing, but this problem still exists. Any ideas?
>
> Thanks!
>
>
> ------------------------------------------------------------------------
>
> resource r0 {
>
> protocol C;
> incon-degr-cmd "echo '!DRBD! pri on incon-degr' | wall ; sleep 60 ; halt -f";
>
> startup {
> degr-wfc-timeout 120; # 2 minutes.
> }
>
> disk {
> on-io-error detach;
> }
>
> syncer {
> rate 100M;
> group 1;
> al-extents 257;
> }
>
> on cisco {
> device /dev/drbd0;
> disk /dev/vg00/xfs;
> address 10.0.0.1:7788;
> meta-disk internal;
>
> }
>
> on juniper {
> device /dev/drbd0;
> disk /dev/vg00/xfs;
> address 10.0.0.2:7788;
> meta-disk internal;
> }
> }
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
--
Michael Haverkamp