How to increase the disk space in Oracle VM Virtalbox ?I want to allocate 80 GB .Can anyone help me?
If your disk is in .vdi Format, you can use
VBoxManage modifyhd YOUR_DISK.vdi --resize SIZE_IN_MB
If you have a disk in another format, you could convert it to .vdi by cloning it with a destination format.
If you have snapshots, resizing is not possible, so you have to remove them first or use a clone.
Related
I have been using Google colab for quite sometime. Recently I noticed that 43 GB of disk space is already occupied. Even if I change runtime to TPU 43 GB out of 107 GB remains occupied. I tried factory reset runtime but it doesn't work. Even if I use Google colab from another Google account still 43 GB of disk space is occupied. How to clear the disk space ?
There's some amount of space that's used by the base operating system and libraries. You won't be able to trim this value very much by deleting files since most will be required for normal operation.
If you need a larger disk, consider Colab Pro, which has 2x the disk space.
I've created an APFS volume on a MBP running High Sierra in order to use it as a Time Machine drive for the iMac I use at work (we don't have a backup solution so this is my hacky way to keep myself safe as the MPB itself is backed up separately).
I foolishly assumed 100GB would be enough (as I only back up certain folders) however in less than a week the iMac has filled it and Time Machine is complaining about insufficient disk space.
I am trying to figure out a way to expand the volume (to say 150GB) however every help page and blog I can find shows you how to shrink a container.
I've tried using Disk Utility but it doesn't give me the option to resize individual volumes (only the overall container).
Disk Utility Screenshot
I've also tried using the diskutil in terminal but don't want to break things.
I'd prefer not to dump and re-create the partition of possible, but if it's the only option I will deal with it.
Cheers
Matt
Find out your container first with:
diskutil apfs list
Say you found out its disk0, then you do:
sudo diskutil apfs resizeContainer disk0 0
In my example (see screenshots) you see that disk1 container grew, and this was the one line in the output that indicates a happier you:
"Growing APFS Physical Store disk0s2 from 864,999,997,440 to
1,000,345,825,280 bytes"
Before and after output of diskutil list: (note disk1)
Short answer: APFS volumes cannot be resized, only APFS containers.
Longer story:
An APFS volume exists inside an APFS container but not outside of it. That APFS container is the "thing" that in reality occupies space, i.e. bytes, on a medium, not the APFS volume. Hence only APFS containers can be resized but not APFS volumes. If one thinks of APFS volumes as being "just fancy labels for virtual space", then it becomes much clearer what is what. The direct effect of this is that within an APFS container the volumes coexist and compete for the remaining/free/unallocated space of the container.
The longer story is true.
But does not mention two facts about APFS volumes.
Quota: When creating a volume, the use can specify the maximum space that new volume will be allowed to use, of the total space in that volume's container. That volume can not use more space.
Reserve: When creating a volume, the use can specify an amount of space in the container, which will be reserved for that new volume. No other volume in the container can use space that would reduce the available space below the sum of the reservations of the other volumes.
So, the next question is: can the quota or reserve be changed? Not using Disk Utility. How about using diskutil in the Terminal interface? (Answer: maybe so. But, dear reader, be very careful. And know that Apple Care says: "We do not support Terminal.")
I am using Centos 7 on the host, and with QEMU emulation windows server, I create a 15 GB disk, then after a week or so, the disk goes to 30 GB, is there a way to stop this? I am using snapshots. Is there any windows service that may be creating lots of files, or maybe the HD is being used as RAM to imprive system? from 15 GB to 30 is a lot, and the server's HD is not bigger, so It's a big issue to me. I reinstalled all and turned a lot of things off, but the same thing happens again. Little help here.
You don't mention what kind of disk image you're using, and what its configuration is. I'm guessing from your description that its a qcow2 image, since you mention use of snapshots. Snapshots stored inside the qcow2 image will increase its size beyond that visible to the guest OS. eg if you create a qcow2 image that has a virtual disk size of 15 GB, then it is possible for it to consume much more than 15 GB on the host if you have saved multiple different snapshots in the image and the guest has been writing alot of data between each snapshot. Even when snapshots are deleted, this space consumed by qcow2 won't be released back to the OS normally. So while seeing 30 GB of usage sounds quite large it is not totally unreasonable if using snapshots alot.
I am running Xen on Fedora 21 and want to upgrade my Notebook with a SSD. I'd like to run the dom0 and the OS part of the domUs on the SSD but store their data on the HDD. I only want to buy a 128 GB SSD because of pricing but have to store a lot of code and binaries.
Is there a way to assign another image to the domU (saved on the HDD) that the domU will recognize as another disk? Do you have any recommendations how to solve this? What would be the best performing solution? Is this possible with an LVM setup as well?
Thanks in advance for your help!
I found a solution myself. I am adding an IDE Device in virt-manager containing the .img file on the HDD. Another way would be adding a LVM partition to the domU. It's really easy to achieve with virt-manager.
My pc have 3G memory,and I store data into redis.I write data to disk via dump.rdb. I found when dump.rdb is about 1.5G,redis will shut down,why that?
and when I input info in redis-cli,I found all my memory are spent by redis.
how to tackle that?
I use 32bit, ubuntu 12.04.
if I add more memory,32bit machine only can hold 4G memory,so if I will add more 5G data，how to tackle that much dat?
thx guys.
You're hitting the 32 bit process memory limit. 2GB of the address space is reserved for the kernel, leaving only 2GB left. You then read 1.5GB, and presumably do some more stuff with it that involves allocating more memory, and somewhere in this process, you run out.
If you want to be able to use more than that you'll need a machine with more ram and a 64 bit operating system.