Thanks Nikolaus for your feedback. I tried on a "real" local backend, unfortunately after 8GB I ran out of local diskspace (that's why we use NAS'es for a reason ;-) ) - I retry later today on a new spare disk.
On the otherhand, my sshfs testcase - hosting an s3ql filesystem locally, and exported by CIFS ànd local cp - successfully completed its job: [root@strobiserver /]# s3qlstat /mnt/s3ql-ttt-local/ Directory entries: 13088 Inodes: 13090 Data blocks: 15196 Total data size: 76280.19 MiB After de-duplication: 74266.21 MiB (97.36% of total) After compression: 72883.05 MiB (95.55% of total, 98.14% of de-duplicated) Database size: 4.02 MiB (uncompressed) (some values do not take into account not-yet-uploaded dirty blocks in cache) Network still was "slow", but load of server never exceeded 2.5. I'll destroy this test case, and rebuild one with local backend and report the results later. PS. as per documentation uncertainty: if the "local" ~/.s3ql is lost, is the s3ql filesystem still mountable? -- 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.
