Hi Christian, A: Because it confuses the reader. Q: Why? A: No. Q: Should I write my response above the quoted reply?
..so please quote properly, as I'm doing in the rest of this mail: On Jun 27 2019, Christian Loitsch <[email protected]> wrote: >> On Jun 26 2019, Daniel Jagszent <[email protected]> wrote: >> >> [...] During the update files were missing and I decided to copy >> >> everything to a local disk before continuing the upgrade process. >> >> [...] >> > did you copy the files from an object storage (S3, Google Storage, >> > OpenStack Swift)? That does not work. S3QL needs metadata of the >> > copied "files" that you probably did not copy over – and even if, the >> > Local file backend stores the metadata differently, AFAIK. >> >> That's right. >> >> > You cannot easily copy a S3QL filesystem from one backend type to >> > another. >> >> It's pretty easy if you use the right tools :-). >> >> https://github.com/s3ql/s3ql/blob/master/contrib/clone_fs.py > > Am I correct, that `clone_fs.py` requires the "old" filesystem to be > available? > > I only took a quick look, but AFAICT I can't convert the already copied > filesystem. correct? As Daniel said, your copy did not include all the data. So no, it can't conjure this data back :-). Best, -Nikolaus -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/871rzeer98.fsf%40vostro.rath.org. For more options, visit https://groups.google.com/d/optout.
