Completely lost connection to volume at CA-MTL from different account at now
About ten miniutes ago the serverless and pod service all went dead, meets diffenerent error related to File IO.
Error: [Errno 6] No such device or address
4 Replies
@coding_achilles
Escalated To Zendesk
The thread has been escalated to Zendesk!
provide some pod id / the network storage too
network storage: tetggcfobt
pod_id: eqlwbf2e9ntfa8
I have two account meets the same problem, the newly started pod couldnt open jupyter(counldt read any file), the newly started serverless-worker is unable to reach the scripts and model at volume
This is causing serious production issues. Please inform when it will be resolved.
the same is with my account. i have network volume in ca-mtl
my network id is m04dhjwjud. first i was getting error Disk quota exceeded (122) on my network volume, then my volume became unresponsive