In the application running on IIS on Windows Server 2012 R2,
"System.IO.IOException: There is not enough free space on the disk."
has come to occur.
I was trying to print a log to a text file, but when I checked it, I found that it was not limited to this app, but it was no longer possible to write to drive C.
Situation
·Windows runs on VMware.
·C drive has about 35GB of space.
·You can write to the E drive on the same disk.
·You can also read the C drive.It was also possible to copy files to E drives or folders on different servers.
"·Even if you try to create an empty folder or an empty text file for a folder in drive C, it will show ""Not enough free space"" and fail."
·When you try to delete a file, it disappears on the display of the explorer, but it has not been deleted, and when you update it with F5, the file will be displayed again.
You cannot also remove del or rmdir from a command prompt.
·Window reboot did not resolve.
·When I checked the event viewer, there was no log at the time when the above error first occurred.
However, after rebooting, the event viewer now has more logs.
It seems that this feature can now be written to drive C.
·It was restored after returning to the state a few days ago from the backup, but it reappeared after about the same date.
Has anyone experienced this kind of situation?
I would appreciate it if you could give me information such as other places to check.
3Additional information on March 20
Thank you to everyone who responded.
We are moving toward re-creating a new virtual environment.
·It was thin provisioning.
·The capacity on the host side was sufficient.
·Even in this state, you can write and delete E drives.
If you have enough space on your host's C drive, you may be able to use How to increase drive capacity in a virtual guest environment.
The host administrator needs to work with it.
Depending on how you assign a virtual disk, you may want to expand the disk (to the maximum size) as you use it instead of filling the maximum size when you create it.
About Virtual Disk Provisioning Policies (Thin Provisioning)
You may also need a memory swap file (*.vmem) that is the same amount of memory you assigned to the virtual machine, or you may have problems with the disk space on the host OS side of the host OS, such as snapshots of the virtual machine.
Solved: No free space for virtual disk****.vmdk
VMWare "in" OS recognizes
The "physical disk" to which the virtual disk is assigned is
I think it's depleted.
Either way, you should check with your virtual server (host) administrator.
© 2024 OneMinuteCode. All rights reserved.