Hello,
I am unable to use datastore in ESXi 5.5
Here is some back ground
- Had ESXi 4.1 running on the server before installation of ESXi 5.5
- While 5.5 installation selected option to 'preserve datastore'
- After successful installation of 5.5 logged in via vSphere client.
- Able to see preserved datastore & vm's.
But if I am trying to create a new vm it says no free space left.
Is it because datastore version compatibility? Datastore file system is vmfs 3.5
I want to avoid formatting this local datastore.
Pls suggest.
Thanks & Regarda,
Amey.
How much free space was there in the datastore before the upgrade versus now? Did you check for any snapshots that may be taking up space?
You could upgrade the datastore to VMFS5 and see if this resolves the issue, would be a good first step imo. It does not require downtime doing this.
i understand your VMFS 3.5 Data store has big size of Block size and caused this issue. So since you are upgraded esxi 5.5 I would suggest migrate all the running VM to other data store and format and upgrade this data store to VMFS 5 .5. " The block size of the datastore also has an impact on the maximum file size (including virtual disk size being added to a virtual machine) that can be created on it. Therefore you must also consider the largest file or virtual disk size that you want to use when creating the VMFS datastore" below link clearly expalain about old VMFS datastore block size: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100356...
Thanks all for quick updates.
dhanarajramesh : Thanks. Yes I realized that after doing SSH. 1 of the vm disk occupied almost whole datastore. I created disks using 'Thin Provisioning' style. Is there any way to upgrade file system on existing datastore without need to format?
in your case since the blaock size is constrain I suggest below KB. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100532... and FYI: Limitations resulting from an in-place upgrade from VMFS3 to VMFS5:</>VMFS 5 retains the used block size (instead of the now usual unified block size of 1 MB) • VMFS 5 still uses 64 KB sub-blocks instead of the new 8K sub-blocks • VMFS 5 still uses MBR instead of GPT after the in-place upgrade. But when the volume exceeds the 2 TB limit it will be switched to GPT without affecting the virtual machines. • VMFS 5 still uses sector 128 for the start partition instead of sector 2048 • also the file limit remains: there is still a limit of 30720 files if you make an in-place upgrade (with a newly created VMFS 5 > 100.000 files)
