Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 271
  • Last Modified:

Sized maxed

I have a critical server running on our poweredge r710 and ESX4.
The machine which has 450gb local disk, is provisioned to a 250gb disk for the virtual server. The remaining space is free. I just looked on the console and it shows that the maximum size is 256. When I login to the actual virtual server, we have 16gb free.

So my problem? I have 150gb of usable space on the local disk of the physical server, but the virtual disk is configured at 256 and is apparently maxed out. What can I do?
0
shankshank
Asked:
shankshank
  • 2
1 Solution
 
Danny McDanielClinical Systems AnalystCommented:
your maximum file / virtual disk size is limited by the block size set on the datastore which defaults to 1mb and that limits you to 256 GB.  Your only choices are to move the VM off and re-create the datastore with a larger block size or, ... create a 2nd disk and add in the volume under directory (not sure what OS your VM is).

I'm wondering, though, if you only have the one VM on this ESX host and if so, why???  If you're only going to run the single VM, why not just run it natively on the r710 so you get full access to it
0
 
shankshankAuthor Commented:
If I move the VM off, what do you mean by recreating the datastore? How would I copy that file off? And you are saying to log on vsphere and recreating the localdisk with a block size? That won't hurt th eOS right?

We have other hosts, but their disk is on a NAS.
0
 
Danny McDanielClinical Systems AnalystCommented:
You will need to power down the VM, unless you are licensed for storage vmotion, but you can migrate the VM to another datastore in a couple of different ways.

1.  the source host sees the NAS datastore, so you just right-click on the VM and choose migrate...follow the wizard to move it. (with VC and Storage Vmotion license you can do this while VM is running, otherwise; you will need to power down the VM)
2.  the source host doesn't see the NAS but it is in vCenter Server along with 1 or more hosts that do see the NAS.  power down the VM, right-click and choose migrate.  this will move it to another host and datastore.
3.  use Converter to move the VM from one host/datastore to another(can be done while VM is running, tell converter it is a physical machine)
4.  use SCP(FastSCP is better) to move the VM from one host to another.  vm must be powered off for this.

Then you can change the block size on the existing datastore.

http://kb.vmware.com/kb/1013210 Reformatting the local VMFS partition's block size in ESX 4.x (post-installation) or http://kb.vmware.com/kb/1012683 Increasing the block size of local VMFS storage in ESX 4.x during installation
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now