Edit

Share via

No space is available on drive E or F

  • Article

This article discusses how to resolve a scenario in which drive E or F on Microsoft Azure Cloud Services runs out of free space.

Symptoms

You host an instance of Cloud Services, but you discover that your drive E or F has zero free space.

Cause

Because drives E and F are used as the application disk drive, no application-related data should be stored on those drives. Data storage can cause the space usage to be much greater than the sum of the individual file sizes. For more information, see Where did my space go?.

The storage space that's used shouldn't affect the operation of the application. After the drives are created, Azure virtual machines don't write to them unless the application code does. The application code shouldn't be writing to these drives, anyway.

Solution

For data that an application has to read from and write to, we recommend that you use an external storage service, such as Azure Storage or Azure SQL Server.

If the location of the local data store is needed, make sure that the application code uses local storage resources. These are stored on the local drive C. For more information, see Configure local storage resources and Azure disk partitions.

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Contact us for help

If you have questions or need help, create a support request, or ask Azure community support. You can also submit product feedback to Azure feedback community.