We're using XenServer 6.1 Advanced on three blades in a pool. I'm in the process of moving storage from an old SAN to a new SAN using Storage XenMotion. So far, so good!

I discovered though, on a LUN that has no free space, Storage Xenmotion isn't able to create the snapshot, and therefore fails the transfer.

What is striking me as odd though, is that the new SAN is reporting space as if the VD had actually been moved.

Here is a shot of the current vdisks existing on the new SAN: Vdisks on new SAN

However, here is a shot from the General Tab of the storage repository on the new SAN: Storage Repository

This XenServer pool is the only thing that accesses this storage repository. At most, I would think ~150 GB should be used. Maybe a little more, but certaintly not double that. My current hypothesis is that it has something to do with the failed storage XenMotion.

Question: Are there XenServer tools (command line or within XenCenter) that can help me understand where the extra storage went and reclaim it?

As always, I'm more than willing to provide more information to help narrow the problem down! Thanks in advance!

1 Answer 1


I found the issue, and it as I suspected. The Storage XenMotion was creating orphaned virtual disks when it would fail, but those wouldn't show up in XenCenter. This article was extremely useful: http://appsense.wordpress.com/2009/11/24/deleting-orphaned-disks-in-citrix-xenserver-5-5/

I chose the easy method. On a current VM's storage tab, attach the orphaned disk (they show up in this list!), then delete.

Things are reporting much more accurately now!

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .