I have SQL Server running on a Large Azure Virtual Machine.
I have an attached disk where all the database MDFs, logging, backup and restore files are kept. Nothing is kept on the C:.
I just logged in now and noticed that there is only 58MB left on the C:! Is it possible to increase this disk space. Is there something I can delete from the C:?
You cannot increase your os disk size. Not sure when you created your Virtual Machine. I know that a long time ago the size was set at (I believe) 30GB, and now the os disks should be around 127GB. You may want to check what size the OS disk is.
I'm not sure what chewed up your OS disk space except maybe some type of temporary os storage.
Related
So I am running a small VM for personal stuff on azure and want to minimize cost. The disk cost is significant part of my per day spending. I am running standard Ubuntu 18.04 image and already selected standard HDD instead of SSD for disk. but the current OS disk is of size 30GB and I am hardly using 3GB of it. I want to use smaller disk but I can't find a option to do so.
For your issue, I'm afraid it's impossible. The reason is that when you gonna create a VM from the VM image, the OS disk size must be bigger than the image size. I think you know the limitation. And in Azure, it also makes sense. For example, you can see the details of the VM image Ubuntu 18.04-LTS:
You see the VM image size is 31, so the VM OS disk size should bigger than 31. When you want to create the VM, you can see the details about the VM image first, and then you will know if what is the minimum size of the OS disk.
Good Morning, Fellow Stack Overflow-ers,
I have a Windows 2019 DC Virtual Machine with a 127GiB OS Disk with MS Azure. The WM image is Standard B2s (2 vcpus, 4 GiB memory)
I want to swap this with a smaller 8GiB OS disk - having successfully created this in my portal and labelled useastOS - Azure is failing to allow me to swap from the previous 127GiB disk to the smaller 8GiB Disk. On the "Swap OS Disk" menu illustrated, you will see there is no option to use the useastOS disk.
Puzzling.
This is a managed disk and so there is no reason whatsoever as to why Azure is not giving me the option.
So my question is there any valid reason as to why Azure is not allowing me to swap to the smaller useastOS or is this bug within Azure that I need to make Azure aware of?
When you are creating a Managed Disk like this, there is no SO installed, it is an empty disk, that's why Azure assumes it is a data disk, not a SO disk.
Now, when you upload your VHD disk to blob storage, you can tell Azure that this disk is OS and not a data disk like this.
Looking for upload VHD to Azure blob, here it is an example https://learn.microsoft.com/en-us/azure/virtual-machines/windows/prepare-for-upload-vhd-image.
Your question is how to swap SO disk to a new one smaller, this is what I understood, in case you just want to add a second disk as a data disk, you can go to VM overview, from blade disk, you can add it easily.
Anyway, I hope that I could help in any :)
Just in case, confirm that you selected an operation system when you created this disk useastOS. For example, in my case it is Windows, but disk can be either Windows or Linux, when you don't select anything, Azure assumes it is a data disk, not an operation system.
Each week nearly two or three times, azure vm stops the responding. When it happens, Disk Read Bytes are dramatically increasing i dont know why. My application has no read disk function (only writes the logs).
As you see in the figure, Read Bytes and Disk Operations are increasing for a moment that causes server to freeze. I have to do restart the VM and it takes nearly 15 minutes to be available again.
Azure Ubuntu VM Stats
i am using Azure Ubuntu 16.04 VM and Size is Standard B1s (1 vcpus, 1 GiB memory).
i have alredy checked these conditions
possible memory leaks by my application
observed all source codes of application whether disk read function exists or not (i dont have any disk ready operation at my application)
i have changed default virtual ram size at ubuntu %60 to %1
i am using docker to run my application and i am using only 1 instance of docker image at vm
i removed all vm and i created it again (including all resources i.e. disk/network etc.)
i want to know why this is happening and how can i investigate what are cause this problem. I haven't seen any suspicious running process at ubuntu when it is happening.
This issue is solved by Azure Technical Support Engineers (Thanks to Micah_MSFT)
That seems Azure VM is going to out of memory. When it happens, VM is acting unsteady, so Disk Operations is rapidly increasing and VM is freezing (they are investigating the issue's details and reported to Linux Technicians).
As clarified by Azure Technical Support Engineer, There is a feature
named Swap Space which helps the saver to reserve storage space as
processing memory.
Here is the configuration
Open the file located under /etc/waagent.conf find these variables and modify them accordingly:
# Format if unformatted. If 'n', resource disk will not be mounted.
ResourceDisk.Format=n /// change this parameter to "y"
# Create and use swapfile on resource disk.
ResourceDisk.EnableSwap=n /// change this parameter to "y"
# Size of the swapfile.
ResourceDisk.SwapSizeMB=0 /// change this parameter to "1024"
Restart the service to apply the changes
sudo systemctl restart walinuxagent.service
That's it
In my opinion, unnecessary increase in disk usage as a result of Out of Memory limit will cause Azure VMs performance to decrease.
I need to know the difference between the SSD disk and the data disk. According to this capture, this virtual machine has a hard disk ssd 16gb, and 4 disks data. But these 4 disks, how much do they have? Are they ssd? what are they for?
enter image description here
data disks can be ssd or not, depending on how you set them up. they are used to store data :)
amount of data disks you can attach depends on the vm sku. you dont always have to attach 4 data disks (or whatever vm supports, you can have 0 - VM SKU maximum data disks).
The 16gb ssd is local ssd (local to the host machine hosting your vm) attached to the VM (not OS disk). its a temporary drive - meaning it can go away when you reboot vm, so content will be lost and you will get a new temporary drive. it can be used to store throw away logs, for example, or temporary files. IO operations on this disk do not count towards IO limit and this drive is completely free (you pay for the VM SKU and it is part of that cost).
you can learn about data disk prices here: https://azure.microsoft.com/en-us/pricing/details/managed-disks/. Storage prices do not take into account os or data disks. they just bill you for storage.
reference:
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/attach-managed-disk-portal
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/attach-disk-ps
It means in addition to the OS disk, you can connect 4 data disks to the VM.
It does not mean there are 4 disks, just that you can add 4 if you want.
You should discuss the VM requirements with your client. Maybe he needs an additional data disk, maybe not.
The capture you posted, specifies that this VM can take up to 4 data disks. The price does not include them. Also, you should check the Azure price calculator to generate more accurate offers.
I've recently upgraded my EC2 server from a m1.small to a m1.medium (old EC2 instances I know) so I have more storage as I recently maxed it out.
When I look at the space available through Terminal I have extra space available on a /dev/sda2 directory
Is there a something I have done wrong when upgrading the server or will the storage automatically balance between the two if I reach 100% on /dev/sda1?
When I run a check I get the following information back:
I've got 1% of 374Gb on /dev/sda2 available but I'm unsure how servers access this memory if /dev/sda1 reaches 100%
I'm a novice at server management so apologies if I'm doing something wrong.
I think you are confusing disk space and memory.
On AWS, different instance types have different memory, cpu and network performances, but the storage space is unrelated: you can extend disk space on a EC2 machine without changing its instance type, by attaching a new disk. I don't understand if your question is about disk space or memory, and I don't understand how a new disk appeared on your instance by simply upgrading it - probably it was there from instance creation.
Anyway, there isn't an "automatic balancing" of storage space - you have to manage your own files and move some files/folders to the new disk before the old one gets filled. Working on Linux, you can leverage symbolic links to move large directories across disk without too much hassle.
you are using m1.medium, which given as SSD. So you just treat it as "virtual physical storage" given to you. So /dev/sda2 space is NOT extendable to /dev/sda1
The SSD storage given is call "instance store". Anything inside /dev/sda are not permanent. You can REBOOT the instance and nothing lost .
HOWEVER, if you STOP or SHUTDOWN the instance, everything is gone. Do not pour important data in there.
EBS volume normally are shown as /dev/xd* , which is extendable.
Please check out. EC2 instance store