[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-API] LVMoISCSI SR resize

  • To: xen-api@xxxxxxxxxxxxxxxxxxx
  • 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
  • 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=
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

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

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


xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.