I'd like to make an app that displays the % free disk space.
I can get the IsolatedStorageFile.GetUserStoreForApplication().AvailableFreeSpace, but not the amount of global space (storage size) to do the math.
Any help?
Thanks.
Related
I'm currently doing some cleanup on an Azure environment and just wanted to check calculations. I have about 55 Databases on an elastic server, which is currently sitting at 3.64TB of the maximum 4TB. Having a look at each of the databases within this pool, I can see that they have their own Used / Allocated / Maximum sizes. Each of these is ranging between 0.1% and 80% of their allocated 250GB. Is the allocated size of the elastic pool dependent on the maximum sizes of each of the databases within that elastic pool? IE if I took a database that is using 1GB of 250GB and reduced the maximum size of this database within the elastic pool from the default 250GB down to 20GB, would it have any positive/negative implications? If anyone can suggest any good resources for azure environment maintenance plans it would be greatly appreciated as I'm coming from an AWS background.
Your allotted area will immediately expand; you do not need to be concerned; this is typical. You'll see that occupied space is always close to available space. The key is when the total amount of allotted and utilised storage space approaches the maximum storage size.
If the database size reaches the maximum size, use the following statement to raise the maximum size or use Azure portal to alter the maximum size.
ALTER DATABASE AzureDB2 MODIFY (EDITION='STANDARD', MAXSIZE= 50 GB)
The database receives a certain amount of log space depending on the tier. When you specify the storage size in vCore, you are given a fixed amount of space for your logs. If you pick 1TB of storage, for example, 300GB is set aside for logs.
We had recently upgraded our 8 host MarkLogic cluster from ML8 to ML9 (9.0-8.2). We enabled telemetry for our cluster and we did see around 1 MB data is getting uploaded to telemetry in ErrorLog.txt. We had a system /tmp space of 5GB but whereas in Memory,Disk, Swap space requirements (https://docs.marklogic.com/9.0/guide/installation/intro#id_11335) it says
"System temp space sizing - when using telemetry allow for 20 GB maximum in system temp space, although normal usage will likely be less than 100 MB."
My concern is do we face some performance issues if we didn't increase /tmp to 20 GB?
I had a 50gb disk for my vm instance and I went to the disks in compute engine and changed to size to 100gb.
I restarted my server twice now and it is still showing the disk as only 50gb
Is there some form of delay associated with changing the disk size?
Here is an image of what it looks like on the Google Cloud Console
Here is an image of what it says on the server
Changing the size of the physical disks associated with your Compute Engine VM instance doesn't change the usage of that disk without first performing some additional steps. These steps change the partitioning of the disks.
Recipes for both Linux and Windows can be found in the documentation:
Resizing the file system and partitions on a zonal persistent disk
i have problem with disk resize.
I try to change size in Proxmox, but show size in virtual machine not showing.
But if I try qemu-img info vm-100-disk-1.qcow2 i have this result:
image: vm-100-disk-1.qcow2
file format: qcow2
virtual-size: 491G (527207235584 bytes)
disk size: 161G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
What is virtual size? This as I tried to adjust the size, I increased the size of the virtual disk more than really has.
I need this:
virtual size: 250G
disk size: 250G
Can you help me wih this problem?
Thank you in advance.
ps. Debian wheezy (updated)
Qcow2 disk images are not preallocated. So it's only as large as the data it contains.
You did resize the disk successfully to 491GB (virtual-size), but the disk contains only 161GB of data.
After you resize a virtual disk, you also need to extend the partitions and or filesystems inside the virtual disk to make use of the new extended disk space.
You wrote that you only need to extend your disk to 250GB, but instead you did (multiple) resizes to the current 491GB. If you did not yet resize the partitions and filesystems, you can still shrink the image. This command will basically just cut off the file. So be sure you didn't make any use of the new extended disk size.
At the Monitor in the VM on Proxmox you can execute this command:
block_resize drive-ide0 250G
What is the maximum database size? Is there a chart that shows maximum database size across different devices? Can you store a pre-populated database on an SD card and plug that into the device and read that database with titanium?
There is no limit (as far as I know besides SQL limits) on the size of a database except available storage on device, but obviously your app wont really function responsively if you have a ridiculous (a million rows) amount of data stored on the device.
The chart would just be comparing phone flash memory.
Probably, but there hasn't been a lot of success. Check here, and here and here.