On Feb 25 2016, [email protected] wrote: >>> Looks like something scrubbed /tmp while S3Ql was still using it. Is >>> that possible? >> > Well I don't think it's possible ... Please find attached the content of > all the temp folders used by s3ql. > Do you think we should delete *-cache files that still remains?
No, just run fsck.s3ql. >> > In any case, running fsck.s3ql should make your bucket mountable again. > > > We've done another fsck.s3ql but we are still unable to mount the buckets. > > Here is what we get : > > Using 4 upload threads. > Autodetected 4052 file descriptors available for cache entries > Backend reports that fs is still mounted elsewhere, aborting. What did fsck.s3ql say? Please post the complete output (including the command you used to start it) for both fsck.s3ql and mount.s3ql. >>> contrary to what you said in your second Email, you are using S3QL 2.13, >>> not 2.15. >> >> > You are right! > In fact we've installed s3ql directly using dnf. After checking, the > package installed is s3ql-2.13-1.fc23.x86_64. > Is it better to install it using your method as described here ? > > https://bitbucket.org/nikratio/s3ql/wiki/installation_fedora Don't know, sorry. Not familiar with Fedora. But updating to the newest release is generally a good idea. 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.
