[Xen-API] Re: xcp storage repositories

To:	Daniel Sintaj <daniel.sintaj@xxxxxxxxxxxx>
Subject:	[Xen-API] Re: xcp storage repositories
From:	George Shuklin <george.shuklin@xxxxxxxxx>
Date:	Fri, 24 Dec 2010 05:26:19 +0300
Cc:	xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Thu, 23 Dec 2010 18:25:51 -0800
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=ubCFm6vDgfpimJv5slsi3gNR3VUWiPKZtrr+CmQK+YU=; b=r4HrO28gfRHh//LOJHNo0llkKV5C/7ygeiOMqhyzFPfDWap8JqjEi0q6V7N2LJPB/3 TGZpGYbo2FJQPxfNsj5u7rMKrZ2uMSdjmfLMQyVDMaN27YpfDrmWciFa2JZGTZF6hewh Vo6LxJngCWtV9uhH7aQsfBDsxgi2H1JyZl/I8=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=Z0dUh+mSSL9in/qRVQzf4jO1m2mistxSyQEACPFE2NNsq1tNhM0Ziyf6uEifT/i31w fQfEXXSNHmf83RFmeJFEFvfyGab1ilY6lsfuouQSwuhrcnFpIxs8UeuqdJlmKQwxOawd K3k+mLorEcYYLtG2f2T05kFyxkyl1M+OcGak8=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<4D13F0F8.8020000@xxxxxxxxxxxx>
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>
References:	<4D13F0F8.8020000@xxxxxxxxxxxx>
Sender:	xen-api-bounces@xxxxxxxxxxxxxxxxxxx

Well... There is two solution:

1) do not upgrade lvm2 package and forbid it upgrade in yum
configuration.

2) there is dirty hack to solve problem: do sr-create (it will fail),
and than do sr-introduce. sr-create will create required LVM layout on
target but will fail to mount it due some kind of race condition (I
don't dig deep enough). But sr-incroduce will not cause an race
condition and will see prepared by sr-create LVM layout and successfully
import it.

3) wait until someone fix this bug.


В Птн, 24/12/2010 в 02:01 +0100, Daniel Sintaj пишет:
> Hi,
> 
> I have been reading this mailing thread 
> http://www.gossamer-threads.com/lists/xen/api/193896?page=last when you 
> mentioned, that CentOS yum upgrade will result into some sr-create errors.
> 
> Error code: SR_BACKEND_FAILURE_53
> Error parameters: , Logical Volume unmount/deactivate error 
> [opterr=errno is 3],
> 
> Would you have some kind recommendation/hint how to solve this situation?
> 
> Thank you for your time and sorry for interrupting in this way of contact.
> 
> Kind regards.
> 
> ~ Daniel.



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

WARNING - OLD ARCHIVES

xen-api

[Xen-API] Re: xcp storage repositories