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

RE: [Xen-API] Resizing VDI with Local Caching enabled


  • To: 'Marco Sinhoreli' <msinhore@xxxxxxxxx>
  • From: Jonathan Davies <Jonathan.Davies@xxxxxxxxxxxxx>
  • Date: Thu, 24 Mar 2011 15:01:48 +0000
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc: xen-api <xen-api@xxxxxxxxxxxxxxxxxxx>, Andrei Lifchits <Andrei.Lifchits@xxxxxxxxxx>
  • Delivery-date: Thu, 24 Mar 2011 08:02:12 -0700
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
  • Thread-index: Acvpa7Nz2ILzHDynToSgb+YaICoA5wAx8zjQ
  • Thread-topic: [Xen-API] Resizing VDI with Local Caching enabled

Hi Marco,

No, that's not the expected behaviour...

Andrei (cc'd) has not been able to reproduce this. Are you able to provide 
/var/log/SMlog and some more detailed reproduction steps?

Thanks,

Jonathan

> -----Original Message-----
> From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-api-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Marco Sinhoreli
> Sent: 23 March 2011 15:03
> To: xen-api
> Subject: [Xen-API] Resizing VDI with Local Caching enabled
> 
> Hello all:
> 
> I'm trying resize a VDI cloned from a gold-image. I'm using storage
> local caching in my tests. After resize, the virtual machine isn't
> booting. Bellow the exception:
> 
> 
> <output>
> [root@server ~]# vdi=$(xe vbd-list
> vm-uuid=fa537d17-1b07-b472-74c7-67b2a2f5561f device=xvda
> params=vdi-uuid --minimal)
> [root@server ~]# xe vdi-resize uuid=$vdi disk-size=40GiB
> [root@server ~]# echo $?
> 0
> [root@server ~]# xe vm-start  uuid=fa537d17-1b07-b472-74c7-67b2a2f5561f
> There was an SR backend failure.
> status: non-zero exit
> stdout:
> stderr: Traceback (most recent call last):
>   File "/opt/xensource/sm/NFSSR", line 253, in ?
>     SRCommand.run(NFSSR, DRIVER_INFO)
>   File "/opt/xensource/sm/SRCommand.py", line 246, in run
>     ret = cmd.run(sr)
>   File "/opt/xensource/sm/SRCommand.py", line 94, in run
>     return self._run_locked(sr)
>   File "/opt/xensource/sm/SRCommand.py", line 131, in _run_locked
>     return self._run(sr, target)
>   File "/opt/xensource/sm/SRCommand.py", line 183, in _run
>     caching_params)
>   File "/opt/xensource/sm/blktap2.py", line 1280, in activate
>     if self._activate_locked(sr_uuid, vdi_uuid, caching_params):
>   File "/opt/xensource/sm/blktap2.py", line 29, in wrapper
>     ret = op(self, *args)
>   File "/opt/xensource/sm/blktap2.py", line 1312, in _activate_locked
>     dev_path = self._activate(sr_uuid, vdi_uuid, caching_params)
>   File "/opt/xensource/sm/blktap2.py", line 1326, in _activate
>     dev_path = self.setup_cache(sr_uuid, vdi_uuid, caching_params)
>   File "/opt/xensource/sm/blktap2.py", line 1468, in setup_cache
>     local_sr_uuid, scratch_mode)
>   File "/opt/xensource/sm/blktap2.py", line 1550, in _setup_cache
>     standby=scratch_mode)
>   File "/opt/xensource/sm/blktap2.py", line 711, in launch_on_tap
>     raise TapdiskFailed(cls.Arg(_type, path), ctl)
> blktap2.TapdiskFailed:
> Tapdisk(vhd:/var/run/sr-mount/01cbd019-bd89-1296-a4bf-
> fd9d412f64f4/05732396-9466-4828-9926-2217a10a18c9.vhdcache):
> ['/usr/sbin/tap-ctl', 'open', '-p', '21483', '-m', '3', '-a',
> 'vhd:/var/run/sr-mount/01cbd019-bd89-1296-a4bf-fd9d412f64f4/05732396-
> 9466-4828-9926-2217a10a18c9.vhdcache',
> '-e', '0', '-2',
> 'vhd:/var/run/sr-mount/b5631d2b-7931-c93c-39da-5a20978e823b/05732396-
> 9466-4828-9926-2217a10a18c9.vhd']
> failed: status=22, pid=21485, errmsg=
> </output>
> 
> Is it a bug or could I have done something not permitted?
> 
> Thoughts?
> 
> 
> Cheers!
> 
> --
> Marco Sinhoreli
> 
> _______________________________________________
> xen-api mailing list
> xen-api@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xen-api
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

 


Rackspace

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