On 09/03/16 23:16, Nikolaus Rath wrote:
After backing up the metadata files, please try to run fsck.s3ql. After
that, please move the metadata files (now updated by fsck.s3ql)
somewhere else and try to run mount.s3ql. This should download metadata
from the backend (since there is no local copy). You should then be able
to create files again on the file system. Please also check the file
access times (e.g. using `stat <file>`). There was a possibility for
them to become corrupted (but I believe it did not happen in your case).
Thanks, Nikolaus. That worked perfectly. Access times seem fine too.
I can also confirm that the setgid bit works and that
--backend-options ia works.
Just one thing, I'm not sure it's sensible to push the metadata to
"infrequent access" as it is accessed rather frequently. Maybe just the
actual data?
Thanks again for fixing this so quickly, for all your hard work in
writing s3ql and for your patience in dealing with users like me. :)
Kindest regards
Cliff.
--
Cliff Stanford
Office: +44 20 0222 1666 UK Mobile: +44 7973 616 666
Spain: +34 952 587 666
http://www.may.be/
--
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.
