Comment 6 for bug 892765

While troubleshooting problems like this it could be useful to have a
look at /var/log/SMlog on XenServer's dom0.
It can be confused with a general vdi coalesce problem.
As example, you can have a look at this:

http://paste.openstack.org/show/4685/

in this case the error was generated by some previous failed deploy.
To solve the problem I just had to delete the vdi with uuid
a6661c5d-31ca-416d-b749-c41ea13c29f3 which was totally unrelated with
the resize process that was generating an error.

Hope it helps someone else.
Giuseppe

2012/2/3 Giuseppe Civitella <email address hidden>:
> Hi Rick,
>
> I'm not seeing the problem anymore.
> I should be able to do some final tests on my environment at least by
> the end of next week.
> As soon as I get the results I'll update the bug.
> Anyway I found a solution following Dan Prince's advices reported here
> https://bugs.launchpad.net/nova/+bug/862653 about vm image
> installation.
> Increasing xenapi_vhd_coalesce_poll_interval also helped dealing with
> resize in case of big images (10 to 15 GB thin provisioned disk).
>
>
>
> 2012/2/2 Rick Harris <email address hidden>:
>> Guiseppe: Are you still seeing this issue?
>>
>> I wasn't able to replicate this on 5.6.100-39215p.
>>
>> One thing that may help debug this is if you could start with a fresh
>> SR, replicate the issue, and paste more-or-less the full SM.log output.
>>
>> We should be able to see what VDI is erroneously holding a reference to
>> the base-copy preventing the VHD from coalescing.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/892765
>>
>> Title:
>>  XenServer resize: the second resize of the same vm fails
>>
>> Status in OpenStack Compute (Nova):
>>  Confirmed
>>
>> Bug description:
>>  I'm experiencing the following problem doing a multiple
>>  resize test using XenServer (version 5.6 SP2 and verion 6) as hypervisor.
>>  On first resize everything works as expected. If I do another resize a
>>  few minutes later, I receive an error about "VHD coalesce
>>  attempts exceeded" on destination host.
>>  Here's an extract from nova-compute.log:
>>  http://paste.openstack.org/show/3368/
>>
>>  On the hypervisor's /var/log/SMlog I can find errors like this:
>>  http://paste.openstack.org/show/3369/
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/nova/+bug/892765/+subscriptions