torstai 10. maaliskuuta 2016 2.45.02 UTC+2 Riku Bister kirjoitti: > > > >> If you did something like that, you can try to get things in order by >> removing the s3ql_metadata_bak* files from the storage backend, as well >> as the local cached copy of the metadata (.db and .param file) and then >> running S3QL 2.17's fsck. But no guarantees. >> >> nope, but i have a backup of those files before upgrade from storage. is > it safe restore them and re-try? only files i dont have back up is the data > files > > Managed to fix it, removed from ~.s3ql/ mountpoint .db and .param files. i done nothing on storage backend. also applied the hotfix 2.17.1 right away. thanks for fixing so fast the issue. :)
-- 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.
