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? 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. Thank you. -- 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.
