On Nov 05 2015, Chris Croome <[email protected]> wrote: > Hi > > I'm using s3ql to backup several servers and roughly every other night > one of the backup fails during the rsync with: > > rsync: write failed on "/example.file.txt": Transport endpoint is not > connected (107) > > Is there anything I can do to reduce these errors? Is there any further > information about these failures that I could provide that could help > solve this?
Where did you look for further information? I presume not in https://bitbucket.org/nikratio/s3ql/wiki/FAQ#!what-does-the-transport-endpoint-not-connected-error-mean? > Is there a better way than using `df` to check for this problem -- the > delay makes it unreliable -- this is a script I have been using to try > to work around this problem, running it before and after each backup: [...] People never cease to amaze me. You are experiencing regular file system crashes, and you have created a *script* to work around the issue? I would drop everything and use a different file system until the problem was fixed. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
