Sent: 31 December 2010 14:11
To: Jonathon Royle
Cc:
xen-api@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-API] XCP 1.0 beta - Locked VDI issue
Well... I'm not familiar with file-based VDI provisioning, but I'm think
the problem is not in XCP (well, XCP have the bug, but it only trigger
state), but in some forgotten mount.
Check fuser/lsof output, and try to restart xapi (xe-toolstack-restart).
And look to /var/log/messages and /var/log/xensource.log, every domain
start it filling with huge amount of debug info (I sometime thinking,
that this info reduce domain start/shutdown speed at least half).
В Птн, 31/12/2010 в 13:56 +0000, Jonathon Royle пишет:
> George,
>
> Thanks - now my oops, I thought I had included SR details
>
> SR - /dev/cciss/C0d0p3 ext3, thin provisioned
>
> Server HP ML370 G5 - running Raid1
>
> NB Same thing happens on RAID 5 /dev/cciss/C0d1p1 also ext3. Not tested with Local LVM but I can do.
>
> Jon
>
>
>
> -----Original Message-----
> From: George Shuklin [mailto:
george.shuklin@xxxxxxxxx]
> Sent: 31 December 2010 13:13
> To: Jonathon Royle
> Cc:
xen-api@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-API] XCP 1.0 beta - Locked VDI issue
>
> Oops, sorry, miss it.
>
> Next: is SR iscsi-based? Check if corresponding volume mounted and try
> to deactivate it by lvchange. (name of LV will contain VDI uuid).
>
>
> В Птн, 31/12/2010 в 12:13 +0000, Jonathon Royle пишет:
> > George,
> >
> > Thanks for quick response.
> >
> > List of created VBD is as per original post - ie only attached to intended VM. As part of initial trouble shoot I did remove all VBDs as there was (from memory) an errant one.
> >
> > Regards,
> >
> > Jon
> >
> >
> > -----Original Message-----
> > From: George Shuklin [mailto:
george.shuklin@xxxxxxxxx]
> > Sent: 31 December 2010 12:06
> > To: Jonathon Royle
> > Cc:
xen-api@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-API] XCP 1.0 beta - Locked VDI issue
> >
> > Try to see created vbd for this vdi (xe vbd-list vdi-uuid=UUID), some of
> > them will be attached to control domain where VM was stopped.
> >
> >
> > В Птн, 31/12/2010 в 11:42 +0000, Jonathon Royle пишет:
> > > First time post so hope I am using the correct list.
> > >
> > >
> > >
> > > I have been trialling XCP1.0 beta for a few weeks now and have had no
> > > issues until now. If the host is ungracefully shutdown (power fail in
> > > my case) then the VDI of the running VM become unusable upon host
> > > restart.
> > >
> > >
> > >
> > >
> > >
> > > [root@----]# xe vm-start uuid=03ed2489-49f6-eb48-0819-549c74a96269
> > >
> > > Error code: SR_BACKEND_FAILURE_46
> > >
> > > Error parameters: , The VDI is not available [opterr=VDI
> > > fc77b366-950b-49be-90ce-2a466cf73502 already attached RW],
> > >
> > >
> > >
> > > I have been able to repeat this on several occasions.
> > >
> > >
> > >
> > > I have tried toolstack restart, host reboot as well as vbd-unplug
> > > etc. The only solution I have found is to use sr-forget (a bit
> > > drastic) and then reintroduce the SR
> > >
> > >
> > >
> > > Some config output.
> > >
> > >
> > >
> > > [root@----]# xe vdi-list uuid=fc77b366-950b-49be-90ce-2a466cf73502
> > >
> > > uuid ( RO) : fc77b366-950b-49be-90ce-2a466cf73502
> > >
> > > name-label ( RW): Cacti - /
> > >
> > > name-description ( RW): System
> > >
> > > sr-uuid ( RO): 0fe9e89c-e244-5cf2-d35d-1cdca89f798e
> > >
> > > virtual-size ( RO): 8589934592
> > >
> > > sharable ( RO): false
> > >
> > > read-only ( RO): false
> > >
> > >
> > >
> > > [root@----]# xe vbd-list vdi-uuid=fc77b366-950b-49be-90ce-2a466cf73502
> > >
> > > uuid ( RO) : 350d819b-ec36-faf4-5457-0a81668407f0
> > >
> > > vm-uuid ( RO): 03ed2489-49f6-eb48-0819-549c74a96269
> > >
> > > vm-name-label ( RO): Cacti
> > >
> > > vdi-uuid ( RO): fc77b366-950b-49be-90ce-2a466cf73502
> > >
> > > empty ( RO): false
> > >
> > > device ( RO):
> > >
> > >
> > >
> > >
> > >
> > > Is this a known bug, is there a better solution – happy to test
> > > further
> > >
> > >
> > >
> > > Regards,
> > >
> > >
> > >
> > > Jon
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > xen-api mailing list
> > >
xen-api@xxxxxxxxxxxxxxxxxxx
> > >
http://lists.xensource.com/mailman/listinfo/xen-api
> >
> >
>
>
Home