VMware Cloud Community
ashmita87
Contributor
Contributor

VMware ESXi6.0 is giving the error message "File system where disk resides is full"

While trying to deploy a VM on VMware ESXi 6.0, with 1.6 TB free storage capacity, the ESXi is throwing the following error message:

2016-02-02T17:22:48.296Z| vmx| I120: Msg_Question:

2016-02-02T17:22:48.296Z| vmx| I120: [msg.vmxaiomgr.retryabort.diskfull] The operation on the file "/vmfs/devices/deltadisks/17cf42b6-xyz-x86-64-101-2020201.0-s001.vmdk" failed (Bad address).

2016-02-02T17:22:48.296Z| vmx| I120+ The file system where disk "/vmfs/devices/deltadisks/17cf42b6-xyz-x86-64-101-2020201.0-s001.vmdk" resides is full.

2016-02-02T17:22:48.296Z| vmx| I120+ Select _Retry to attempt the operation again.

2016-02-02T17:22:48.296Z| vmx| I120+ Select Cancel to end the session.

2016-02-02T17:22:48.296Z| vmx| I120: ----------------------------------------

Details of the configuration:

ESXi deployed on a system with sufficient RAM (above 32GB), 1.6 TB available space in the data Store.

The VM configuration is 2 GB RAM and VMversion 10, 25 GB Hard Disk space.

Hard disk Configured as LSI Logical SAS, ID (0:0)

Verified the /vmfs/devices/deltadisks directory and found the space to be occupied by only the image for the VM in consideration, i.e. 17cf42b6-xyz-x86-64-101-2020201.0-s001.vmdk of 25GB

The ESX doesn't contain any other running Virtual Machines.

Can anyone suggest what is going wrong or what is happening with the system?

vmkernel.log shows the following from boot up to the point the error message is displayed:

2016-02-02T18:14:12.570Z cpu6:2696186)Sched: vm 2696217: 6485: Adding world 'vmm0:VR_new', group 'host/user', cpu: shares=-1 min=-1 minLimit=-1 max=-1, mem: shares=-1 min=-1 minLimit=-1 max=-1

2016-02-02T18:14:12.570Z cpu6:2696186)Sched: vm 2696217: 6500: renamed group 19676636 to vm.2696186

2016-02-02T18:14:12.570Z cpu6:2696186)Sched: vm 2696217: 6517: group 19676636 is located under group 4

2016-02-02T18:14:12.578Z cpu6:2696186)MemSched: vm 2696186: 8113: extended swap to 43176 pgs

2016-02-02T18:14:12.590Z cpu6:2696186)WARNING: MemSched: 6236: Psharing is disabled but ballooning is not.

2016-02-02T18:14:12.888Z cpu1:2696217)VMMVMKCall: 235: Received INIT from world 2696217

2016-02-02T18:14:12.890Z cpu1:2696261)WARNING: NetDVS: 658: portAlias is NULL

2016-02-02T18:14:12.890Z cpu1:2696261)Net: 2444: connected VR_new eth0 to VM Network, portID 0x3000018

2016-02-02T18:14:12.890Z cpu1:2696261)NetPort: 1573: enabled port 0x3000018 with mac 00:00:00:00:00:00

2016-02-02T18:14:12.900Z cpu19:34872)Config: 679: "SIOControlFlag2" = 0, Old Value: 1, (Status: 0x0)

2016-02-02T18:14:50.454Z cpu7:33407)NMP: nmp_ResetDeviceLogThrottling:3345: last error status from device naa.600605b006c4ed401b2488fc33246435 repeated 1 times

2016-02-02T18:14:57.089Z cpu1:2696229)WARNING: UserMem: 13591: vpn 0xb0048e81 status bad0026

2016-02-02T18:14:57.094Z cpu1:2696229)WARNING: UserMem: 13591: vpn 0xb0048ea1 status bad0026

2016-02-02T18:15:05.676Z cpu1:2696229)WARNING: UserMem: 13591: vpn 0xb003d116 status bad0026

2016-02-02T18:15:05.676Z cpu1:2696229)WARNING: UserMem: 13591: vpn 0xb003d116 status bad0026

2016-02-02T18:15:05.676Z cpu1:2696229)WARNING: UserMem: 13591: vpn 0xb003d116 status bad0026

2016-02-02T18:15:05.676Z cpu1:2696229)WARNING: UserMem: 13591: vpn 0xb003d116 status bad0026

2016-02-02T18:15:05.676Z cpu1:2696229)WARNING: UserMem: 13591: vpn 0xb003d116 status bad0026

2016-02-02T18:15:05.676Z cpu1:2696229)WARNING: UserMem: 13591: vpn 0xb003d116 status bad0026

3 Replies
continuum
Immortal
Immortal

That sounds like you get a rather poor error-message.
A vmdk with the extension *-s001.vmdk uses a Workstation-format that is not directly compatible with ESXi 6.
So your problem is not a full disk but an incompatible vmdk.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

ashmita87
Contributor
Contributor

Thanks a lot Continuum.

So can I use the VMware Convertor Software to make the vmdk file compatible with ESXi 6.0??

Atleast I think I want to give it a try....

Reply
0 Kudos
continuum
Immortal
Immortal

Converter operates with VMs - not vmdks.
You either use Workstation vmware-vdiskmanager's convert function
or on ESXi load the module that adds support for split and sparse vmdks - then you can use vmkfstools -i to clone the existing vmdk into a new one.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos