Request: Detect transport endpoint disconnection and automatically attempt to remount

[AndydeCleyre]

Hi,

One of my buckets in particular (the largest, > 1 TB) periodically gets its goofys mountpoint broken ("Transport endpoint is not connected"). When this happens, I need to ssh in, unmount and run the goofys mounting command again.

Is it possible for goofys itself to monitor for this state, and attempt a remount when encountered?

goofys --version

0.0.11

[kahing]

Transport endpoint is not connected means goofys has crashed, and there are some fixes in the 0.0.13 release, so try that first. Also, since goofys has crashed, it's not possible for it to remount itself, but you can write a wrapper script that does that.

[AndydeCleyre]

Thank you. I had thought the process was still running, but you're probably right. I'll write back if I find otherwise.

[Niek]

Same here. Sometimes goofys crashes and rhe only thing that helps is running umount /path/to/mountpount && goofys

[zheliazkov]

Same problem here using goofys version 0.24.0-45b8d78375af1b24604439d2e60c567654bcdf88.
Someone found a solution?

[varontron]

Like @zheliazkov, I also see this error with 0.24.0-45b8d78375af1b24604439d2e60c567654bcdf88

[malaniarpit]

We have encountered a similar issue using goofys version 0.24.0-45b8d78375af1b24604439d2e60c567654bcdf88.

➜  ~ goofys --version
goofys version 0.24.0-45b8d78375af1b24604439d2e60c567654bcdf88

[smitty-exos]

Just had the dreaded : failed (107: Transport endpoint is not connected)

goofys version 0.24.0-0c993271269b539196330a18716a33fbeeebd624

Mounting wasabi. umount / mount fixes, but would prefer this didn't happen. I love goofys but I can't have this keep happening.
Ideas?