In that case, I think it is stuck on a previous Node, I can;t think of any other reason.
Do you have something else on the same PV that was lost ? like api server configuration?
No worries, and I hope you manage to get that backup.
Now I suspect what happened is it stayed on another node, and your k8s never took care of that
(I mean new logs, while we are here did it report any progress)
Meaning the node restarted (or actually moved)
Could it be it was never allocated to begin with ?
what do you mean?
I will investigate a bit more and then check if I can recover
thank you for your time and support, I appreciate it!
so if the node went down and then some other node came up, the data is lost
yea the api server configuration also went away
okay that proves it
yea the api server configuration also went away
That somehow the PV never worked and it was all local inside the pod
Could it be it was never allocated to begin with ?
Oh dear, I think your theory might be correct, and this is just the mongo preallocating storage.
Which means the entire /opt/trains just disappeared
check if you have any more of those recovery reports in the mongo log, it should report progress
I think I have sent you all the existing logs
Now I suspect what happened is it stayed on another node, and your k8s never took care of that
that's an interesting theory
And if this is the case, that would explain the empty elastic as well
but the PV seems to be just a path to the labeled node
so if the node went down and then some other node came up, the data is lost
That might be the case. where is the k8s running ? cloud service ?