Jump to content
Welcome to our new Citrix community!
  • 0

XenServer local storage after deleting snapshot?


Bit-101

Question

Free disk space on Host in XenServer local storage after deleting snapshot?

Local storage on one Host in XenServer displays 100%
Now, I deleted some old snapshot, but cant free disk space on local storage that still displays 100%.

What more can I do to free up disk space?

 

Really appreciate your answer.

Link to comment

14 answers to this question

Recommended Posts

  • 0

Putty into XenServer with that host ip

cat /etc/xensource-inventory | grep -i installation_uuid

host_uuid.thumb.JPG.c532677f0d4d39de07c27733de2e87d4.JPG

xe sr-scan uuid=82exxaxx-xxxx-xxx-xxxx-xxxxxxxx25d

And if I have look in the XC-console I also can see that the UUID is right but I still get this error message from the scan command:

Error message: "The uuid you supplied was invalid"

.

(Note: In this post I ´ve hiding the UUI with x)

Link to comment
  • 0

Could not paste it in as code:

[root@server000 ~]#
[root@server000 ~]# xe sr-list uuid=d641e1df-ba32-b43b-a9ad-c713593af338 params=                                                                                                              all
uuid ( RO)                    : d641e1df-ba32-b43b-a9ad-c713593af338
              name-label ( RW): Local storage
        name-description ( RW):
                    host ( RO): server000
      allowed-operations (SRO): VDI.create; VDI.snapshot; PBD.create; PBD.destro                                                                                                              y; plug; update; VDI.destroy; scan; VDI.clone; VDI.resize; unplug
      current-operations (SRO):
                    VDIs (SRO): d523cd68-8219-4e1f-a73e-acca8c4661e2; 76425ece-1                                                                                                              47a-4345-8d04-07178012c284; e483a5f7-065d-470b-b23a-89b5767ffc12; 43d2b86b-bebd-                                                                                                              4a91-b77c-c89974689871; 8a9f6231-e098-4640-9342-93d930ebbb40; db5b2dd3-dca9-4810                                                                                                              -b14f-3e5ae1c035c3; b1fbf4e9-64a0-411f-95d0-3c66e07d81c7; 72e31bf0-814b-4e97-bfe                                                                                                              1-d58626ea9c0d; bfceb79a-9648-496b-a30d-fcc3993b6c6b; 674b36d0-cc02-4d6d-857b-7a                                                                                                              4c4f9d81fb; 0fd1176b-afee-4f24-83a4-2149663cbf07; 67e0f3d6-4e0b-4eb3-a736-0dcaeb                                                                                                              b970de; 91872cd4-19d8-41c0-93bc-c61ec7a122d6; 7cf83fb9-3a9e-4ac8-a3eb-6a057209e0                                                                                                              3a
                    PBDs (SRO): 2a7d2ca8-5dc4-4f42-06f2-8865a1d55bc2
      virtual-allocation ( RO): 332868354048
    physical-utilisation ( RO): 277633662976
           physical-size ( RO): 286789713920
                    type ( RO): ext
            content-type ( RO): user
                  shared ( RW): false
           introduced-by ( RO): <not in database>
            other-config (MRW): i18n-original-value-name_label: Local storage; i                                                                                                              18n-key: local-storage
               sm-config (MRO): devserial: scsi-3600508b1001c09ef6f320d08a027c7b                                                                                                              5
                   blobs ( RO):
     local-cache-enabled ( RO): true
                    tags (SRW):
 

Link to comment
  • 0

Did anything change since running the scan? Did you check what's running with  "xe task-list" to see if it's still running? The operation can take a long time under some circumstances. It looks to be pretty full based on the listing you provided. If too full, a scan won't be able to recover free space.

Link to comment
  • 0

Ok, it´s obvious that it is to full.

Any idea how to free upp space for example remove a VM snapshot, that XEN host refuses to let go, after a restart of the host.

Or any other idea? I dont use pools in XenServer

 

 

Update 2022-06-22:

Found this article, but I´m not a familiar with XenServer and storage in general

https://support.citrix.com/article/CTX123400/how-to-reclaim-disk-space-from-deleted-xenserver-snapshots
But how do I know if it´s LVM or not? or if this link is the right way forward?

 

I Really appreciate your answer.

Edited by Peter Fällman
Complete question
Link to comment
  • 0

It´s not possible to move VM.

Turn VM off and try to move:

"Select the storage repository that you would like to move the VM to:
Local storage on server00 Current location"

This is greyed out and I cant choose any other SR-location.

(Delete is not an option.)

 

Update:
The GUI and the command does not display the same:
i can recognize VM1 and VM2 

Then I have 2 Master VM and 3 more VM
But I dont have any clue which is which of the rest of the VM.
The GUI says VM3, VM4, VM5

 

Here´s the output:

[root@sb-xen100 ~]# xe vdi-list sr-uuid=d641e1df-ba32-b43b-a9ad-c713593af338
uuid ( RO)                : 76425ece-147a-4345-8d04-07178012c284
          name-label ( RW): VMServer1
    name-description ( RW): VMServer1
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 21474836480
            sharable ( RO): false
           read-only ( RO): false


uuid ( RO)                : e483a5f7-065d-470b-b23a-89b5767ffc12
          name-label ( RW): VMServer2 0
    name-description ( RW): Created by template provisioner
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 53687091200
            sharable ( RO): false
           read-only ( RO): false


uuid ( RO)                : d523cd68-8219-4e1f-a73e-acca8c4661e2
          name-label ( RW): base copy
    name-description ( RW):
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 53687091200
            sharable ( RO): false
           read-only ( RO): true


uuid ( RO)                : 43d2b86b-bebd-4a91-b77c-c89974689871
          name-label ( RW): base copy
    name-description ( RW):
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 53687091200
            sharable ( RO): false
           read-only ( RO): true


uuid ( RO)                : 8a9f6231-e098-4640-9342-93d930ebbb40
          name-label ( RW): base copy
    name-description ( RW):
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 53687091200
            sharable ( RO): false
           read-only ( RO): true


uuid ( RO)                : db5b2dd3-dca9-4810-b14f-3e5ae1c035c3
          name-label ( RW): XenServer Transfer VM system disk
    name-description ( RW):
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 8388608
            sharable ( RO): false
           read-only ( RO): false


uuid ( RO)                : b1fbf4e9-64a0-411f-95d0-3c66e07d81c7
          name-label ( RW): VMMaster1
    name-description ( RW): Created by template provisioner
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 53687091200
            sharable ( RO): false
           read-only ( RO): false


uuid ( RO)                : 72e31bf0-814b-4e97-bfe1-d58626ea9c0d
          name-label ( RW): VMServer2
    name-description ( RW): VMServer2
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 21474836480
            sharable ( RO): false
           read-only ( RO): false


uuid ( RO)                : bfceb79a-9648-496b-a30d-fcc3993b6c6b
          name-label ( RW): VMServer3
    name-description ( RW): VMServer3
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 21474836480
            sharable ( RO): false
           read-only ( RO): false


uuid ( RO)                : 674b36d0-cc02-4d6d-857b-7a4c4f9d81fb
          name-label ( RW): base copy
    name-description ( RW):
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 53687091200
            sharable ( RO): false
           read-only ( RO): true


uuid ( RO)                : 0fd1176b-afee-4f24-83a4-2149663cbf07
          name-label ( RW): VMServer4 0
    name-description ( RW): Created by template provisioner
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 53687091200
            sharable ( RO): false
           read-only ( RO): false


uuid ( RO)                : 67e0f3d6-4e0b-4eb3-a736-0dcaebb970de
          name-label ( RW): VMMaster2 0
    name-description ( RW): Created by template provisioner
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 53687091200
            sharable ( RO): false
           read-only ( RO): false


uuid ( RO)                : 91872cd4-19d8-41c0-93bc-c61ec7a122d6
          name-label ( RW): base copy
    name-description ( RW):
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 53687091200
            sharable ( RO): false
           read-only ( RO): true


uuid ( RO)                : 7cf83fb9-3a9e-4ac8-a3eb-6a057209e03a
          name-label ( RW): VMServer5
    name-description ( RW): Created by template provisioner
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 53687091200
            sharable ( RO): false
           read-only ( RO): false


Update 2022-06-28:

What's strange is is that the UUID:s does not correspond between GUI (User Interface) and commands output- see example with one VM:

xe vdi-list sr-uuid=d641e1df-ba32-b43b-a9ad-c713593af338:
uuid ( RO)                : 7cf83fb9-3a9e-4ac8-a3eb-6a057209e03a
          name-label ( RW): VMServer5
    name-description ( RW): Created by template provisioner
             sr-uuid ( RO): d641e1df-ba32-b43b-a9ad-c713593af338
        virtual-size ( RO): 53687091200
            sharable ( RO): false
           read-only ( RO): false

The GUI displays: UUID e3a2f4a7-5e20-5d6b-5be7-d917d70b5a4a

And I cant find any snapshot on that VM.
I have a theory that a snapshot from VMServer5 is not deleted from the local storage and still allocate disk after I deleted the snapshot through GUI

Therefore I started this topic 

 

Quantity VM by commands: 13

Quantity VM by GUI: 7

 

-So, I want tio get rid of those VM that´s obsolete, its´5 .

But I dont have any clue which is which of these 5 VM.
(1 of those is XenServer Transfer VM system disk)

 

Edited by Bit-101
Spelling
Link to comment
  • 0

There is only one snapshot but on a another host with a lot of free disk.

And it´s not possible to compare what storage that is  associated to each VM.

 

The UUID does not correspond depending on what command I´m executing

As an example:

1. xe vdi-list sr-uuid=85a4dc1d-c127-13de-15df-281f0c10e282

ServerExample has the UUID=208d187c-73bb-408b-91cc-c213380a9a8f

    1.1 xe vdi-list sr-uuid=<the UUID for the local SR> displays on all hosts the name of the VM but with UUID that´s not correspond to the UUID in the GUI and a lot of

          names like base copy and so on.

2. xe vm-list executed on the same host with it´s local storage (SR) UUID=85a4dc1d-c127-13de-15df-281f0c10e282 

ServerExample has the UUID=b6555fa4-f00e-bbe7-d3fc-acf21be594cd

     2.1 This command also displays the name of the VM and the same UUID as in the GUI.

 

So it´s the same "problem" on all hosts, the UUID does not correspond depending on what command you execute. 

 

The final question:

1. What command is displaying the right UUID for a VM on a particular SR?
2. And how do I know if I´m deleting the right VM on a particular hosts SR (local storage) based on its UUID?

 

Maybe I have missunderstand something here, but I really want to know if it is so.
Or so is something terrible wrong here.

Right now I´m stuck with a host with full disk.

 

?

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...