On Jun 17 2016, Brandon Orwell <[email protected]> wrote:
> I've been using S3QL for a few days now, and whenever I am copying over
> large amounts of data the mount point seems to 'lock up' for a period of
> time (as well as anything else trying to access it), and then I start
> getting 'transport endpoint not connected' errors. I "umount" the mount
> point, run fsck on it. and then continue archiving until the problem
> happens again.

I've heard this kind of story before, but it still amazes me. What train
of thought led you to this procedure, instead of reporting the problem?

> Does anyone know what would cause these problems?

Where did you look for the answer?
https://bitbucket.org/nikratio/s3ql/wiki/FAQ#!what-does-the-transport-endpoint-not-connected-error-mean
says:

,----
| What does the "Transport endpoint not connected" error mean?
| 
| It means that the file system has crashed. Please check mount.log for a
| more useful error message and report a bug if appropriate. If you can't
| find any errors in mount.log, the mount process may have
| "segfaulted". To confirm this, look for a corresponding message in the
| dmesg output. If the mount process segfaulted, please try to obtain a C
| backtrace (see Providing Debugging Info) of the crash and file a bug
| report.
| 
| To make the mountpoint available again (i.e., unmount the crashed file 
system), use the fusermount -u command.
| 
| Before reporting a bug, please make sure that you're not just using the
| most recent S3QL version, but also the most-recent version of the most
| important dependencies (python-llfuse, python-apsw, python-lzma).
`----


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.

Reply via email to