This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-API] Alternative to Vastsky?

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-API] Alternative to Vastsky?
From: Nomen Nescio <info@xxxxxxxxxxxx>
Date: Wed, 20 Apr 2011 11:05:43 +0000 (UTC)
Delivery-date: Wed, 20 Apr 2011 04:06:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DAEB9A8.9080107@xxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Reply-to: Nomen Nescio <info@xxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
> > Than you for reply about two iscsi target for same drbd... I have a
> > little doubts about data consistency due iscsi queue...
> I never had a problem, probably because it was setup for fail-over not 
> performance. I would be inclined to agree with you.

I can confirm this only works for failover and even there the caching on the 
initiator, especialling when handled by hardware HBA's, can leave you with 
filesystem corruption.
As a sidenote, when combining Xen with DRBD, I would strongly suggest disabling 
sendpage for DRBD if you like your kernels not to crash one after the other ;-)



xen-api mailing list