I have a package which has the quota of 2MB, however, I walk through FTP and it let me upload files larger than 2MB, while it should not!
How can I do to assign the disk QUOTA?
I have it installed on CentOS 7.
Related
I am using Minikube to bootstrap a Kubernetes cluster on my local machine (for learning purposes). I am in Windows platform. Minikube is installed on C drive. It's actually low on disk space due to some personal files and other Softwares. According to Minikube documentations, it requires a 20GB of disk space for its VM. However, when I try to bootstrap the Kubernetes cluster sometimes booting up fails stating low disk space. But disk space is available in my other drives.
By default on which drive, Minikube allocates its space? Installed location? Is there any way to specify on which drive Minikube allocates its 20GB space?
As pointed out in the comments, disk allocation is done by the driver which is used to create the VM. In my case I was using hyperv as my VM driver, so I used following steps. (Your steps may slightly vary according to your Windows OS version - I am using Windows 10)
Start ---> Hyper-V manager ---> Hyper-V settings ---> Change the default folder to store virtual hard disk files
You can find detailed illustration in here
I have three servers each with 1 x SSD drive (Ceph base OS) and 6 x 300Gb SAS drives, at the moment I'm only using 4 drives on each server as the OSD's in my Ceph storage array and everything is fine.
My question is that now I have built this and got everything up and running if say in 6 months or so I need to replace these OSD's due to the space of the storage array running out is it possible to remove one disk at a time from each server and replace it with a large drive?
For example if server 1 had OSD 0-5, server 2 has OSD 6-11 and server 3 has OSD 12-17 could I one day remove OSD0 and replace it with a 600Gb SAS drive, wait for it to heal the do the same with OSD6 then OSD12 etc. etc. until all the disks are replaced, and would this then give me a large storage pool?
OK just for anyone that is looking for this answer in the future you can upgrade your drives in the way that I mention above and here are the steps that I have taken (please note that this is in a lab and not production)
Mark the OSD as down
Mark the OSD as Out
Remove the drive in question
Install new drive (must be either the same size or larger)
I needed to reboot the server in question for the new disk to be seen by the OS
Add the new disk into Ceph as normal
Wait for the cluster to heal then repeat on a different server
I have now done this with 6 out of my 15 drives over 3 servers and each time the size of the Ceph storage has increase a little (I'm only doing 320G drives to 400Gb drives as this is only a test and I have some of these not in use).
I plan on starting this on the live production servers next week now that I know it works and going from 300G to 600G drives I should see a larger increase in storage (I hope).
For whom have installed Eclipse Che. Did you have a look at the RAM usage of the core system ? I mean, before starting to code ?
See What are the minimum requirements to run an Eclipse Che server for 1 user?
I personally run Minishift on Windows 10 in order to play with Red Hat CodeReady Workspaces 1.0.1 (the product version of Che 6.x). I recommend giving minishift 6GB of ram, if you can spare it.
The resource requirements are detailed in the Che documentation admin guide.
For a multi-user Che deployment, there are 3 containers, which require RAM and storage space for persistent volumes. The absolute minimum resources are:
Che workspace server: 750MB of RAM, 1GB of disk in a PVC
Keycloak: 1GB of RAM, 2 PVCs, 1GB each
PostgreSQL: ~515MB of RAM, 1GB PVC for the database
So just to run the workspace server, you will need about 3GB of RAM and 4GB of persistent storage.
In addition, workspaces will need ~2GB of RAM each (requirements change based on language runtime and developer tools). Workspaces can use ephemeral storage or persistent storage for source code and work. If using ephemeral storage, you will need to commit your work before the workspace is stopped or auto-suspended. If using persistent storage, you can use one large PVC which is shared by all workspaces, or a separate PVC per workspace (which may take more storage resources, and makes right-sizing more difficult).
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.
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.