Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question

I'm curious as to where your rsync errors are coming from. Do a "grep s3fs /var/log/syslog" or "grep s3fs /var/log/messages" to try to uncover internal error conditions. You can report these as an issue at for potential help. If these messages imply a connectivity issue, then there isn't much that can be done.

share|improve this answer
Unfortunately (or, rather, fortunately), after upgrade to 10.10 this issue does not appear anymore. – Alexander Gladysh Jan 25 '11 at 17:31
up vote 0 down vote accepted

Upgrade to Ubuntu 10.10 helped.

share|improve this answer

Command to unmount:

% fusermount -u /s3

Command to mount:

% /usr/bin/s3fs -o allow_other bucketname /s3
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.