I set up standalone ironic with mitaka version. I created a whole disk image (ubuntu14.04) by virt-install and used Coreos pxe image (Here) as deploy kernel and ramdisk. (ubuntu 14.04) The disk image size is 10G, and it could be deployed successfully on my node. When I logged in the node and checked the disk info, it only used 10G disk size for /dev/sda. The physical disk size of node is 500G.
How do I make my image to use whole disk size of node after deploying? Thanks.
You have a swap partition after the root partition and that will block the online growing of the root FS.
You need to either move the swap to the front of the disk or remove it entirely.
Related
We want to run a data science model using docker images in Azure batch service.
Our docker image size is 20 GB to 25 GB. Can it be run on Azure batch service?
It depends. Currently, Azure Batch, by default using standard image configurations:
On Linux, maps container images on disk to the local temporary disk (or resource disk) with the azure-batch published container images. The selected VM Size and its local disk size and free space, would determine if your image would fit. Note that all task data would reside on this disk as well.
On Windows, maps container images (unmodified) to the OS disk. The size and free space of the OS disk would determine if your image would fit or not.
Generally speaking, a container image of that size is unwieldy and you would incur very large costs in not only distribution time for non-trivial pool sizes, but also unpack time.
I have a Kubernetes node with a small root disk and a large disk plumbed into /var/lib/docker
Kubernetes does GC on disk images when the used space reaches X%. Whats it looking at though? I can't find it in the docs.
Just to clarify, if you've got / with 20GB of space and /var/lib/docker with a second disk of 100GB, if K8S looks a / the % free is much less, potentially than /var/lib/docker, but / doesn't change much where as the mapped in drive, does.
Configuration info for kubelet cleanup of unused images and containers is here:
https://kubernetes.io/docs/concepts/cluster-administration/kubelet-garbage-collection/
Default for X% in the question is 90%; default cleanup target is 80%.
I created a hdd.img using Yocto and copied the same to pendrive using dd command.
On PC it is mounted as single partition "boot".
When I checked on command line using sudo fdisk -l, it is showing four partitions.
I booted my hardware from pendrive, now I want to remove rootfs.img from boot partition mounted at /media/realroot and copy same rootfs.img again to the same partition.
It is giving No disk space error. I am trying to copy the same rootfs.img which I deleted.
Why it is using only 700MB for boot partiton of 16GB pendrive, or how to increase boot partition size in Yocto to make use of full 16GB?
I'm not sure I understood the real problem but if you are looking for a way to increase the free space on the rootfs, take a look at IMAGE_ROOTFS_EXTRA_SPACE as well as IMAGE_OVERHEAD_FACTOR.
We have a server (centos 6) and our disk is nearly full, we asked for 2 new disk to be added on our server but don't know how to proceed to mount and see it on our server.
Thanks
If you are using RAID1 with the LVM partition then you can increase your current partition otherwise you will have to create new home partition on your server with the new disk and mount it. Once new disk is mounted you can move our current data from old disk to new disk.
While creating virtual Machine i forgot to "Tick" - Allocate all disk space now.
I have already setted up machine, and cloned several from the one, and made changes. :(
So i was looking for any option so that i could change my machine (thin disk province) to change to pre-allocated where it will be equal to dedicated size.
using: VMWARE workstation 7.1.4
created disk without allocating disk size now need fixed allocated disk size.
any help would be highly appreciated.
To sum up: how to change growable disk to pre-allocated in vmware workstation.
vmware-vdiskmanager -r sourceDisk.vmdk -t 2 targetDisk.vmdk
as an administrator while using cmd from windows..
lets say, windows, 7 and we have to open cmd as administrator and cd to the particular location where vmware is installed and run this command,
I'm not sure that you can change the disk type to pre-allocated. You can, however, expand a growable-type disk by selecting Utilities->Expand in the Hardware tab of the VM settings. You can only expnad the disk if the VM has no snapshots and the VM is not a linked clone or the parent of a linked clone. In order to make the newly added space available to your VM, you have to use a disk management tool to increase the size of the existing partition to match the new expanded size of the virtual disk.