Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Sep 08, 2010 at 04:25:03PM +0200, Eric Deschamps wrote:
> sorry...
;)
> >> The initial sync works like a charm, but if I stop a VM on host 1 and
> >> start it on host2, it looks like the system is a snapshot from the
> >> initial sync.
> >>
> >> Anyway, /proc/drbd on both nodes prints UpToDate/UpToDate as well as
> >> drbdadm.
> >>
> >> What could cause this problem ? What am i doing wrong ?
> >
> > Could you post the output of
> >
> > for vm in $(virsh list --all | awk 'NR > 2 { print $2 }') ; do
> > printf "\n%s\n" $vm;
> > virsh dumpxml $vm | sed -e '/<disk/,/<\/disk/!d';
> > done
> >
>
> Of course :
>
> On the first host :
> actes2
> <disk type='block' device='disk'>
> <source dev='/dev/rootvol/actes'/>
> ltsp
> <disk type='file' device='disk'>
> <source file='/dev/mapper/rootvol-ltsp'/>
> samba
> <disk type='block' device='disk'>
> <source dev='/dev/rootvol/samba'/>
> patients
> <disk type='file' device='disk'>
> <source file='/dev/mapper/rootvol-patients'/>
> intranet
> <disk type='file' device='disk'>
> <source file='/dev/mapper/rootvol-intranet'/>
See how not one of them references DRBD,
but all directly use the lower level LVs directly?
If you bybass DRBD, you cannot expect it to magically know
about, and sync, your changes.
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
__
please don't Cc me, but send to list -- I'm subscribed