s3fs: how to force remount on errors?

Posted by Alexander Gladysh on Server Fault See other posts from Server Fault or by Alexander Gladysh
Published on 2011-01-10T06:13:45Z Indexed on 2011/01/10 6:55 UTC
Read the original article Hit count: 423

Filed under:
|
|

I use s3fs 1.33 on Ubuntu 9.10.

Regularily it gives me errors like this:

rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: close failed on "/mnt/s3/mybucket/filename": Software caused connection abort (103)
rsync error: error in file IO (code 11) at receiver.c(731) [receiver=3.0.6]
rsync: connection unexpectedly closed (86 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6]

Any attempt to work with mounted directory after that gives this error:

Transport endpoint is not connected

To get rid of this, I have to remount.

Is there a way to force a remount automatically?

© Server Fault or respective owner

Related posts about ubuntu

Related posts about amazon-s3