On Aug 21 2015, Keebs <[email protected]> wrote:
> This morning I try to pull a directory on my s3ql mount and I get
> :Transport endpoint is not connected
> I try to unmount: File system appears to have crashed.
> I try to run fsck: Can not check mounted file system.
> So I force unmount: fusermount -u
> Then run fsck again: Ignoring locally cached metadata (outdated). Backend
> reports that file system is still mounted elsewhere. Either the file system
> has not been unmounted cleanly or the data has not yet propagated through
> the backend. In the later case, waiting for a while
> should fix the problem, in the former case you should try to run fsck on
> the computer where the file system has been mounted most recently. Enter
> "continue" to use the outdated data anyway:
>
> Any time I enter "continue", I lose data. What do I do at this point to
> prevent losing data?
Try to the computer where the file system has been mounted most
recently. If you are already doing that, ensure that you are using the
same cache directory.
> Also, any idea why this is occurring? Mount was working fine less than 12
> hours ago and the only entry in mount.log from the last 32 hours is from
> this morning:
>
> 2015-08-21 08:47:25.974 6446:MainThread root.excepthook: Mountpoint does
> not exist.
The only way for mount.s3ql to exit without printing something to its
logfile is if it segfaulted (there should be an entry in the kernel
log), or if something prevented it from writing the mount.log
file. But maybe the log file has been rotated? Try looking at mount.log.1.
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.
