Disk quota exceeded error hours after resizing
Hello, yesterday I created a network volume to which I uploaded a compresssed archive, forgetting I need double the space to extract it. Today, a few hours ago I resized the archive to get extra space. Even after retrying on multiple pods I still get the error "Disk quota exceeded" after filling up the original size. I am wondering how long it should take for the size to be updated?
Update: Even after creating a new network storage with enough space (so 60 gb) it says "Disk quota exceeded" at 30gb usage. I am at a bit of a loss on what to do.
Update: Even after creating a new network storage with enough space (so 60 gb) it says "Disk quota exceeded" at 30gb usage. I am at a bit of a loss on what to do.
Solution
Answered by support: "Thank you for your patience.
Our reliability team ran diagnostics on your network volume and, while you only see ~11 GB via du, the backend reports a “size” of 56 GB and a “real size” of 112 GB due to how files and metadata are stored. This exceeds your 60 GB quota and is triggering the error.
To resolve this, you can either:
1. Increase your volume size to at least 120 GB to cover the actual storage usage, or
2. Remove any unneeded files from the volume before extraction.
I hope this helps. If you have any questions or need further assistance, feel free to reach out—we’re here to help."
Our reliability team ran diagnostics on your network volume and, while you only see ~11 GB via du, the backend reports a “size” of 56 GB and a “real size” of 112 GB due to how files and metadata are stored. This exceeds your 60 GB quota and is triggering the error.
To resolve this, you can either:
1. Increase your volume size to at least 120 GB to cover the actual storage usage, or
2. Remove any unneeded files from the volume before extraction.
I hope this helps. If you have any questions or need further assistance, feel free to reach out—we’re here to help."
