I try out to increase vitrual disk on running Xen VM.
I use order
xe vdi-resize uuid=a68471c4-y4f6-4e8f-9cde-74cba33d67d1 disk-size=13GiB online=accurate
Decreasing XenServer Virtual Disk size. Shut down VM and attach second VHD of the desired size. Boot from Gparted and change the partition table on the the original VHD to become minimal. Then completely copy over from the original VHD to the new VHD smaller volume, direct rom Gpdarted menu.
where
a68471c4-y4f6-4e8f-9cde-74cba33d67d1
is definitely uuid of my xen visitor VM.I try out to raise disk size on operating VM, but I possess a mistake:
The SR backend will not help the operation (verify the SR't allowed operations)sr: elizabeth062ce43-056b-1044-02af-00fd6c8dc028 (iSCSI virtual disk storage)
I use iSCSI virtual disk storage space
What I perform incorrect?
I make use of latest Xenserver edition/
Has the Xenserver online disk resize feature?
Thanks in advance!
Darkwind
DarkwindDarkwind
2 Answers
You're not intended to give the uuid of the VM, you should end up being making use of the uuid of the disk you're also trying to resize.
7b8df1e0-2f0c-4176-44a7-6fa94c42c4fa is the uuid you need to give to the vdi-resize command word.
anaumannanaumann
The command 'xe vdi-resize online=correct uuid=VDI' is certainly valid in the XenAPI but not really noted on the admin guide.
But the API guideline mentions the command resizeonline.
I tested on SR kind shared lvm and regional ext and got the SROPERATIONNOTSUPPORTED error on both.It appears that the SR require the param VDI.resizeonline and that presently no SR implements that.
The right after link says that this param was eliminated in 2011 because of dependability issues.
So as it appears, on the web resizing can be currently not really supported for all SR varieties.
cf. source
Francois ScheurerFrancois Scheurer
Not really the reply you're looking for? Browse other questions tagged resizediskxen or request your very own query.
A Citrix XenServer dom0 currently operates with a 4GB main partition which is certainly pretty little by today's specifications. A little amount of workable storage room can end up being quite simple to rapidly fill up. It will be therefore important that dom0 has free space in purchase for it to work correctly. Here we will include some various methods that can end up being utilized to free of charge up disk room within XenServer.
Edit the log turn scripts
As you most likely know, record files are well known for consuming valuable disk room in a system, and XenServer is no different. While you can personally delete previous wood logs from /var/journal there are better methods to go about this.
In my activities through the XenServer cron files, I've found something useful that doesn'testosterone levels show up to become well noted which unfortunately is furthermore the greatest way for rapidly reducing disk space usage by log data files in /var/record in my knowledge. As it turns out now there are scripts already in place to execute the majority of required log turn for us, we can make use of these to our advantage by changing them as required.
Our trip starts in the /etc/cron.m/logrotate.cron document which includes the below cron entry.
Basically this is certainly set up to run the /opt/xensource/rubbish bin/logrotate-xenserver screenplay every one minute. Within this screenplay two extra scripts are usually called mainly because below.
Very first lets get a look into /opt/xensource/bin/deleteoldlogsbyspace, best at the best we discover the below information.
Good, so we can just change BUDGETMB to something lower if required, for instance 50MB. After editing the file and conserving it, you can either run the party script by hand or simply wait around for the cron to get care of it.
It's a related story within the /opt/xensource/trash can/rotatelogsbysize file, as proven below.
These ideals can become altered in order to maintain a smaller log footprint on the disk and can be modified as you notice match.
Enable sign compression
This 1 is quick and easy to implement and furthermore provides some official documentation from Citrix. Essentially you can allow log data compresion to conserve disk space by uncommenting ‘shrink' from the /etc/logrotate.conf document.
Modify Sysstat
Sysstat wood logs are discovered in /var/log/sa and do not generally get up quite much disk area by default. In my experience this listing seems to range from 20MN-50MB in complete size. While not a large quantity, when your root file program is just 4GM in size there are occasions when every extra bit adds up considerably.
I don't recommend level out removing the documents in here as they provide useful performance details which can become useful during troubleshooting. Instead you should consider how many days value of information you desire to keep. By default sysstat will store 7 times value of data down to 10 minute amounts.
You can alter how numerous days worthy of of history are saved in /var/sign/sa by modifying the /etc/sysconfig/sysstat file which is definitely shown below.
You could also alter how often information is usually logged, by default /etc/cron.d/sysstat is certainly arranged to execute this every 10 moments so you could alter it to 30 minutes instead for example.
Personally I've under no circumstances needed to direct to the information kept within these data files as an external monitoring alternative is recommended, therefore disabling them entirely may also be an choice if you're also desperate for the additional space. Nevertheless in most cases the several MB of size required for the documents is most likely worth providing up for additional performance information, how much you need to adjust the disk space utilized to helpful information logged industry off is definitely upward to you and your particular atmosphere.
Delete short-term data files
As the name implies, documents kept within /tmp are usually designed to end up being short-term so this is definitely a index worth looking at when on the hunt for disk area. In XenServer 6.5 and newer this will not appear to end up being as much of a issue, however in XenServer 6.2 I've found a lot of small xenguest record files being composed to /tmp and although they are usually small they can quickly build upward and before long 100s are existing. With that stated I've found single documents in surplus of 100MB that possess been great to delete, therefore it's well worth a check during the clean up procedure.
You can run the below command to screen the overall size of /tmp
To view the largest files you can operate ‘ls -lrSh' as demonstrated below, where -S i9000 types by file size, -ur reverses the ordering displaying the largest documents at the bottom of the output, and -h will screen the size in a individual readable file format.
Delete older patch files
Over time various hotfix and up-date patch data files will be uploaded during maintenance actions, these old documents can be deleted. Like files are usually stored in the /var/repair directory, nevertheless don't move through removing anything just yet! First of all some important information relating to /var/patch, do not eliminate anything within /var/spot/applied. Items in /var/repair (eliminating the used directory) may be safely removed after XenServer has been rebooted and any pending up-dates have become fully applied.
You should not delete items from /var/spot if a XenServer web host in the pool is usually pending a reboot for a hotfix for illustration. Once all XenServer offers have become rebooted for improvements that have got been applied you can after that safely eliminate from /var/repair. Unfortunately this is presently a regular procedure so you will have got to carry out it on each XenServer web host in your swimming pool.
It will be not uncommon to discover documents in surplus of 100MN in here, so purging old data files from /var/spot is usually a great method to claim back disk area in XenServer.
Conclusion
The reduced amount of disk room that the XenServer dom0 has to function with (only 4GB) wants to become supervised and managed in order to avoid problems caused by it filling up up. How you monitor the disk area is upward to you, external monitoring tools such as Nagios for illustration can fulfil this job. Disk room can become freed up by purging old record files, allowing log compression, altering sysstat, removing temporary files, and removing old repair files. Are usually there any additional methods you make use of to free up disk space in XenServer? Allow me understand in the feedback below and I can obtain the posting up to date.