First, for reference, here's my VM config:
bootloader = '/usr/lib/xen-default/bin/pygrub'
vcpus = '2'
memory = '512'
root = '/dev/xvda2 ro'
disk = [
'phy:/dev/drbd3,xvda2,w',
'phy:/dev/universe/drbdvm-swap,xvda1,w',
]
name = 'drbdvm'
vif = [ 'ip=1.2.3.4,mac=00:16:3E:22:A8:A7' ]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
----- Original Message -----
> From: "Lars Ellenberg" <[email protected]>
> To: [email protected]
> Sent: Thursday, 31 May, 2012 12:13:41 PM
> Subject: Re: [DRBD-user] Xen DomU on DRBD device: barrier errors
>
> iirc,
> that's a problem with xen blktap (or what it is called),
> and supposedly fixed in later versions of that driver.
> Or maybe it resurfaced as a regression again.
> Workaround may be to use "phy".
I already use phy, as you can see.
An alternative would be drbd:resourcename, but that doesn't work with pygrub.
And, it doesn't change anything to the infrastructure.
>
> > [ 3.801652] lost page write due to I/O error on xvda2
> > [ 3.801755] Aborting journal on device xvda2.
>
> xvda2 has likely nothing to do with your DRBD setup,
> I assume that this is part of your system disk (maybe the root
> partition?).
>
> As soon as DRBD is used at all, it is made responsible for everything
> :-/
>
> At least in this case, it is not :-)
In my case, xvda2 is my DRBD backed device.
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
