Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Thu, May 31, 2012 at 12:32:08PM +0200, Wiebe Cazemier wrote: > 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" <lars.ellenberg at linbit.com> > > To: drbd-user at lists.linbit.com > > 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. I see. Then that workaround does not work (anymore?). Still, the problem is not in DRBD, but in the xen block driver. Just add "-DRBD" to your googling, should make it easier to find and not be distracted... -- : 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