On Apr 09 2018, Viktor Szépe <szepe.vik...@gmail.com> wrote:
> 2018-04-09 03:11:06.123 14588:MainThread s3ql.mount.main: Cleaning up local 
> metadata...
> 2018-04-09 03:11:06.531 14588:MainThread s3ql.mount.main: All done.
> at this point the S3 bucket got totally empty
> 2018-04-10 04:33:45.592 12961:MainThread s3ql.mount.determine_threads: 
> Using 2 upload threads.
> 2018-04-10 04:33:45.593 12961:MainThread s3ql.mount.main: Autodetected 4058 
> file descriptors available for cache entries
> 2018-04-10 04:33:45.691 12961:MainThread root.excepthook: No S3QL file 
> system found at given storage URL.
> verified with s3cmd.
> Please advise.
> How could several days of backup disappear without trace? I use S3QL on all 
> client servers.

Uhm.. no idea. mount.s3ql should not be able to do this (even if there
was a bug that caused it to delete all filesystem data, you'd still see
the s3ql_metadata and s3ql_seq_no_* objects).


GPG 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 s3ql+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to