Write failed during Unlock

[fert2]

While configuring esxi 4.1 I have an error message:

Call "HostNetworkSystem.UpdateNetworkConfig" for object "networkSystem" on ESXi "esx2" failed.

Operation failed, diagnostics report: Error interacting with configuration file /etc/vmware/esx.conf: Write failed during Unlock. This is likely due to a full or read-only filesystem. Original Error was: Error interacting with configuration file /etc/vmware/esx.conf: Unable to write to file /etc/vmware/esx.conf.5oq5MT while saving /etc/vmware/esx.conf operation aborted. It is likely this was caused by a Full Disk.

1. df -h

visorfs 1.3G 301.2M 1.0G 22% /

vfat 4.0G 2.8M 4.0G 0% /vmfs/volumes/4c8a24ad-646bd0f7-6f75-003048dbc0d1

vmfs3 228.8G 562.0M 228.2G 0% /vmfs/volumes/4c8a0aaf-b9fa49fc-aaed-003048dbc0d1

vfat 249.7M 4.0k 249.7M 0% /vmfs/volumes/a3dca277-08dc2669-05d6-9f5ad8c4e5ee

vfat 249.7M 92.0M 157.7M 37% /vmfs/volumes/a9fe4d70-77a1356e-e95b-58cca2bd2fc9

vfat 285.9M 135.5M 150.4M 47% /vmfs/volumes/3c3693e8-f77a642a-1910-5c6bdcb26d3a

/var/log # vdf -h

Tardisk Space Used

SYS1 199M 199M

SYS2 55M 55M

SYS3 12K 12K

SYS4 12K 12K

SYS5 12K 12K

SYS6 16K 16K

SYS7 12M 12M

-----

Ramdisk Size Used Available Use% Mounted on

MAINSYS 32M 32M 0B 100% --

tmp 192M 4K 191M 0% --

updatestg 750M 8K 749M 0% --

hostdstats 107M 1M 105M 1% --

Accidently,I found strange thing:

1. cd /var/log

1. vdu

For './vmware':

+ tardisk SYS1: 0 ( 1 inodes)+

+ ramdisk MAINSYS: 487424 ( 4 inodes)+

+ heap : 6239 ( 6 inodes)+

For './configRP.log':

+ ramdisk MAINSYS: 4096+

For './sysboot.log':

+ ramdisk MAINSYS: 16384+

For './esx-boot.gz':

+ ramdisk MAINSYS: 40960+

For './smbios.bin':

+ ramdisk MAINSYS: 4096+

For './ipmi':

+ heap : 10240 ( 7 inodes)+

+ ramdisk MAINSYS: 32509952 ( 3 inodes)+

For './messages.1.gz':

+ heap : 2048+

For './messages.0.gz':

+ heap : 2048+

For './messages':

+ ramdisk MAINSYS: 159744+

For '.':

+ tardisk SYS1: 0 ( 2 inodes)+

+ ramdisk MAINSYS: 33222656 ( 12 inodes)+

+ heap : 20575 ( 15 inodes)+

So, I found an enormous file in /var/log/ipmi/0/: sel and sel.raw 32 Mb in a sum. Think it is the couse of the problem.

I'll try to set up my BIOS' IPMI to stop fooding logs.

Couldn't find anything about MAINSYS. So I want to warn you about such problem.

[MagyarKA]

Any update on this? I am experiencing a similar issue with two ESXi 4.1 servers in my environment. I cannot unmount/mount NFS datastores.

[satish_lx]

Which version of ESXi 4.1 are you using ? is it embedded or installable version ?

check out http://technodrone.blogspot.com/2010/12/esxi-has-32mb-memory-footprint.html

[DanielOtte]

I have this exact same issue, the same file has grown out of porportion. What was your final resolution? Did you also delete the file?

Thanks for your info!

Daniel

[fert2]

Yes, I deleted them, but be careful when deleting anything in VMware .

And don't forget to remove the cause of data flooding.

[DanielOtte]

Thanks!