# How do I unblock my MongoDB database?

If a MongoDB cluster’s storage disk ever becomes completely full, it may suffer severe issues. For example, the cluster may become stuck in a crash-loop, where it indefinitely crashes, restarts, and crashes again during its reboot, until we manually troubleshoot it.

To prevent this, when a cluster’s disk reaches 97% capacity, we automatically block further writes to it. If your cluster is blocked, you receive an email notification.

To remove this block, you can use one of the following methods:

- You can [upgrade your cluster’s maximum disk space](https://docs.digitalocean.com/products/databases/mongodb/how-to/resize/index.html.md).
- You can [open a support ticket](https://cloudsupport.digitalocean.com) and request that we manually override the block.

## Related Topics

[How do I fix the "Cannot create property _id on string" type error?](https://docs.digitalocean.com/support/how-do-i-fix-the-cannot-create-property-_id-on-string-type-error/index.html.md): Remove the \_id field from your JSON data so MongoDB can automatically generate unique \_id values for each document during import.

[How do I fix the "DNSHostNotFound Failed to look up service" error?](https://docs.digitalocean.com/support/how-do-i-fix-the-dnshostnotfound-failed-to-look-up-service-error/index.html.md): Use a public DNS server, such as Google’s 8.8.8.8, to resolve SRV lookups required by MongoDB’s connection string.

[How do I fix the "Connection Refused" error when connecting to my database?](https://docs.digitalocean.com/support/how-do-i-fix-the-connection-refused-error-when-connecting-to-my-database/index.html.md): Verify the connection string, ensure correct port usage, and add your local machine to the database cluster’s trusted sources.