WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

[Xen-API] LVMoISCSI SR resize

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] LVMoISCSI SR resize
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Wed, 12 Jan 2011 14:23:43 +0300
Delivery-date: Wed, 12 Jan 2011 03:23:59 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; bh=IBIbfTztT8aoBb2Nnxw9slSFGeN4YKS93UnkAOwJgm0=; b=Dj3vSeVsYxWIuvpuWdy+fU0H10KVQRPLKkSWNkMti+CeKxZst/n+vD0uBjAc2eJJjt karhc7VlzEe5Xvx8449cIq+Pzn584NF/J0vd3IviSXyZ8lrx75iZo4hkNXy+Sfdcw+rt KwrkJ4HEzmtGEwjphfR0hPyX1+PqRbxx3S7/Y=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=LkQP1CvzWn/cFWgD4itr5t7JLoD03KzPY02Zu+jlAA9/7xpDGrgyyg1MWruR+waPWB qm8zY9Zo+vhKfzbysMuL0xMIB9f/r4ob5ydnjeHLrmp3eqnBIvVGPmxXucWy65b+6+6I xHycLZRXzRoWWL2TQ6StKzVcpTElFdguDKKvk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Good day.

As I know XCP have no support for SR resize. Here my workaround for
LVMoISCSI resize. I think it correct, but before accepting it to product
environment I'd like to ask someone to look it from 'XCP internals'
point of view.

1. Resize block device on ISCSI target
2. Restart ISCI target daemon.
3. Evacuate and reboot any slave host in pool. Wait until it boots.
4. Designate this host as new pool master.

After things settle, new SR size (physical-size) will be visible via
sr-list.

Is this method correct? Can it break something within XCP?

Thanks.



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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-API] LVMoISCSI SR resize, George Shuklin <=