Unexpected Storage Full Issue on Network Volume
I am currently using a network volume. I have rented a total of 800GB, and during the process of uploading data and extracting compressed files, I encountered an issue where the storage space became insufficient. I have tried running commands such as du -sh, df -h, and df -i, but I couldn't identify any apparent issues. The output of du -sh workspace/ shows approximately 352GB, and there are no additional data or files that I have added in other directories.
If anyone has experienced a similar issue or knows a possible solution, I would greatly appreciate your advice.
4 Replies
How do you upload your data?
it might get zipped/tar (compress) outside /workspace, for example in /tmp, or somewhere else the app decids
so i guess you can try adding more container disk storage
I uploaded the data directly from my local PC to the workspace's working folder via SSH.
I also checked the parent folders outside the workspace, but there isn't enough data to cause a storage issue.
I even tried deleting the entire network volume and re-uploading all the data, but the issue still occurs—whenever I start extracting the compressed files, the network volume gets completely full... 😭
I also checked the parent folders outside the workspace, but there isn't enough data to cause a storage issue.
I even tried deleting the entire network volume and re-uploading all the data, but the issue still occurs—whenever I start extracting the compressed files, the network volume gets completely full... 😭
I am wondering if you extract to container disk and it didn’t have enough space there, when you get error, can you check the UI and see which disk is full?
The container disk has sufficient space, but the volume disk is getting full.
I'm suspecting there might be an issue during the decompression process, so I tried directly uploading the original uncompressed data from my local desktop via SSH.
However, the same issue still occurs.
I'm suspecting there might be an issue during the decompression process, so I tried directly uploading the original uncompressed data from my local desktop via SSH.
However, the same issue still occurs.