Bad file descriptor
I deployed several CPU pods with a network volume, and at first, they work well.
But after a few hours, with some of them, I get a "Bad file descriptor" error when I try to access "/workspace"
15 Replies
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
I am not sure what things I did wrong. I simply ran the script in /workspace dir(network volume) with pm2. After after a few hours, pm2 couldn't find the script and I can not access to "/workspace"
Which region is your network strorage in?
Sounds like there may have been an issue with the network storage.
EU-RO-1
CPU pods are only available with network volumes in EU-RO-1 , arent they?
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
I can still use the network volume with another pod, but I can't run the process consistently on a certain pod.
I wanna make multiple pods to run the same script on one network volume. is this possible?
not only some of CPU pods, but all CPU pods makes "bad file descriptor error".
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
I am facing the same issue. 3 pods, same network volume. On 1, I get a bad file descriptor when doing a 'ls /workspace'. The same volume works as expected on the other 2 pods.
Which region is this in?
@Levi Morin 's issue is RO, I didnt see @Roberτ say their region.
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
Yes, RO
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
Must be some issue with the network storage in RO, but I can't replicate it on a pod or 2 different endpoints that have network storage in RO
Thanks, guys, so can I use CPU pods with network volume safely?
and which region is available for CPU pods with network volume?
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View