Cool...that all worked...and it has led to another interesting bottleneck. There are a LOT of small files. What I now have is:
Disk A: root Disk B: /home Disk C: (temporary, S3QL bucket) I am copying from C to B....and disk A is being overloaded! I'm *guessing* it's temp files or something used by the s3ql mount process...still investigating... On Thursday, April 15, 2021 at 9:44:13 PM UTC+10 [email protected] wrote: > On Apr 15 2021, Grunthos <[email protected]> wrote: > > OK...possibly made a silly mistake...I have the bucket mounted (for a > copy) > > elsewhere, while running clone-fs. While no writes are occurring, the > > metadata does get uploaded periodically, I believe. > > > > Am I therefor likely now to have a corrupt clone? It doesn't look like > > clone-fs has 'rsync-like' features, so I can't just unmount and re-do to > > get updates AFAICT. Any thoughts? > > If there were no changes, then the metadata has not changed and thus > will not be uploaded. > > If there were minor changes (e.g. file atime but no file contents), then > running fsck.s3ql on the clone should clear the dirty flag without > finding any problems. After that, you're good to go. > > 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/94866d32-9858-41b9-9618-db07e6de77b7n%40googlegroups.com.
