XenServer 6.5 - Clean Up Storage Repository
-
Run out of space while coalescing is a snapshot thing.
How many snapshots for this vm right now?
If it says zero, i think you mention this then you have some orphaned vdis and that should be the problem. -
@momurda As I said in the OP, none.
-
Do you have Xencenter installed on a desktop?
If you choose View>Hidden Objects then look at the Storage Tab of the SR you might see the problem.If not there is some cli stuff involving vhd-util
-
@momurda said in XenServer 6.5 - Clean Up Storage Repository:
Do you have Xencenter installed on a desktop?
If you choose View>Hidden Objects then look at the Storage Tab of the SR you might see the problem.If not there is some cli stuff involving vhd-util
I do, and View > Hidden Objects is enabled. I only see the two disks in the list. For what it's worth I am using XenServer 7.2 since we have some 7.2 hosts in our environment (working on bringing every host up to 7.2). Not sure if this makes a difference.
-
Taking a look at this now: https://support.citrix.com/article/CTX139224
-
I have done this once before, that is the doc i used, plus some google.
-
Hmm, I'm not sure how to interpret the output...
[root@vmhost10 ~]# vhd-util scan -f -m "VHD-*" -l VG_XenStorage-8b007a92-c815-6d9a-d539-125db0c4b016 -p vhd=VHD-c52a7680-b3fa-4ffd-8e73-a472067eb710 capacity=1099511627776 size=92312436736 hidden=1 parent=none vhd=VHD-00c565b0-ab40-4e6d-886e-41c51f62992a capacity=1099511627776 size=1100304351232 hidden=1 parent=VHD-c52a7680-b3fa-4ffd-8e73-a472067eb710 vhd=VHD-1ab9f17f-eefa-4e62-9455-3e73623d1453 capacity=1099511627776 size=29364322304 hidden=1 parent=VHD-00c565b0-ab40-4e6d-886e-41c51f62992a vhd=VHD-586e7cc3-3fbc-4aa1-89bc-6974454aee7d capacity=1099511627776 size=1101667500032 hidden=0 parent=VHD-1ab9f17f-eefa-4e62-9455-3e73623d1453 vhd=VHD-1be106fb-8d7a-438a-98df-23438fc87f75 capacity=21474836480 size=21525168128 hidden=0 parent=none [root@vmhost10 ~]# -
I suspect those hidden guys are what I want to get rid of...
-
@anthonyh Yea looks like you have 3 hidden snapshots of the mail db.
-
From what I'm reading here, I either need to grow the SR or do an offline coalesce: https://support.citrix.com/article/CTX201296
SR_BACKEND_FAILURE_44 insufficient space:
The process of taking snapshots requires additional overhead on your SR. So you need sufficient room to perform the operation. For a running VM with a single snapshot to get coalesce you need twice the space in case of LVM SR’s (Active VDI + Single Snapshotting VDI). If we are in short of space in the SR, we get the following error.
Either do an offline coalesce or increase the SR size to accommodate online coalescing.
I could grow the SR, but I don't want to throw disk space at it for the sake of more disk space. Perhaps I'll need to plan some downtime to do an offline coalesce.
-
Well...
I know XenServer supports growing SRs, but does it support shrinking SRs?
If so, I can grow the SR to 4 TB, perform the online coalesce, then shrink the SR back to 2 TB.
Thoughts?
-
You can also move storage to another SR to get rid of these.
Or Export/Import the vm.You can also try a
xe sr-scan uuid=uuid of SR
which is supposed to force a coalesce. -
@anthonyh No shrinking of SRs.
Are there other vm on the SR you could move? -
@momurda said in XenServer 6.5 - Clean Up Storage Repository:
@anthonyh No shrinking of SRs.
Are there other vm on the SR you could move?Nope, the SR is dedicated to Zimbra. I suppose I could create a new 2TB SR for Zimbra and move the disks, then delete the old SR when it's done. Though moving a 1TB VHD of this importance makes me nervous, haha.
-
@anthonyh said in XenServer 6.5 - Clean Up Storage Repository:
From what I'm reading here, I either need to grow the SR or do an offline coalesce: https://support.citrix.com/article/CTX201296
SR_BACKEND_FAILURE_44 insufficient space:
The process of taking snapshots requires additional overhead on your SR. So you need sufficient room to perform the operation. For a running VM with a single snapshot to get coalesce you need twice the space in case of LVM SR’s (Active VDI + Single Snapshotting VDI). If we are in short of space in the SR, we get the following error.
Either do an offline coalesce or increase the SR size to accommodate online coalescing.
I could grow the SR, but I don't want to throw disk space at it for the sake of more disk space. Perhaps I'll need to plan some downtime to do an offline coalesce.
Offline coalesce is the better option
-
The coalesce job in my experience usually doesn't take too long, but it's purely based on your host Sr performance.
And while you can kick it off manually once offline, you would still have no status.
Do you have XO? I believe it'll show you unhealthy SRs.
-
@dustinb3403 said in XenServer 6.5 - Clean Up Storage Repository:
The coalesce job in my experience usually doesn't take too long, but it's purely based on your host Sr performance.
And while you can kick it off manually once offline, you would still have no status.
Do you have XO? I believe it'll show you unhealthy SRs.
I do not have XenOrchestra. I should set that up...
-
Last night I set up a new SR for Zimbra and live migrated the OS disk over to the new SR without any issues. Took ~5 minutes for the 20 GB VHD.
I'd like to do the same for the 1 TB VHD, but it makes me nervous...
If the process was to bomb mid-progress, what would happen? Is it easy to recover from?
-
@anthonyh said in XenServer 6.5 - Clean Up Storage Repository:
@dustinb3403 said in XenServer 6.5 - Clean Up Storage Repository:
The coalesce job in my experience usually doesn't take too long, but it's purely based on your host Sr performance.
And while you can kick it off manually once offline, you would still have no status.
Do you have XO? I believe it'll show you unhealthy SRs.
I do not have XenOrchestra. I should set that up...
It literally takes longer to update the guest.
https://mangolassi.it/topic/12809/xen-orchestra-community-edition-installing-with-yarn
-
@anthonyh said in XenServer 6.5 - Clean Up Storage Repository:
Last night I set up a new SR for Zimbra and live migrated the OS disk over to the new SR without any issues. Took ~5 minutes for the 20 GB VHD.
I'd like to do the same for the 1 TB VHD, but it makes me nervous...
If the process was to bomb mid-progress, what would happen? Is it easy to recover from?
You would have a backup, but why go through this process? Why not let the system run a coalesce? Is this a production system or your lab?
