On Mar 08 2016, Ilya Yakushin <[email protected]> wrote:
> Hello. I've transferred the S3QL filesystem from one host to another.
> Something gone wrong during the transfer and the filesystem on the target
> host is not mount-able or fsck-able at this moment. I don't have access to
> the source host, so please help me recover my data from transferred
> filesystem on the target host.
How *exactly* did you do the transfer? What exactly do you mean with
"not mount-able or fsck-able"? What was the exact error message?
> I've tried to recover the filesystem by hands (by restoring backup files
> which was made by S3QL (e.g. move s3ql_metadata_bak_1 to
> s3ql_metadata))
This sounds like a bad idea. The more you did manually, the smaller the
probability of me understanding what went wrong and being able to fix
it.
> can you please provide instruction how to correctly preform such
> restoration?
>
> Additional information: the filesystem was made by S3QL version 2.15. As a
> back-end storage I've used a mounted windows share (with "local:///"
> prefix). The filesystem was encrypted.
Copying all the files should be sufficient. The local backend doesn't
use extended attributes or any other fancy features.
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.
