On 27/03/2019 15:06, Cliff Stanford wrote:
I've moved ~/.s3ql to the local SSD boot disk and I will report back
whether that solves the issue.
cliff@pt: ~$ time s3qlstat /opt/s3ql
Directory entries: 21726199
Inodes: 21726203
Data blocks: 2103253
Total data size: 3.51 TB
After de-duplication: 442 GiB (12.30% of total)
After compression: 320 GiB (8.91% of total, 72.45% of de-duplicated)
Database size: 3.07 GiB (uncompressed)
Cache size: 3.65 GiB, 1591 entries
Cache size (dirty): 0 bytes, 0 entries
Queued object removals: 0
real 0m10.140s
user 0m0.468s
sys 0m0.083s
So it's definitely better than it was.
Incidentally, if I try to access the database via the CLI while
mount.s3ql is running, I get "Error: database is locked". I'm running
sqlite version v3.22.0 so it could be that. Or is it possible that s3ql
is leaving a SELECT open? Or is it deliberately locking the database?
Regards
Cliff.
--
Cliff Stanford
London: +44 20 0222 1666 Swansea: +44 1792 469666
Spain: +34 603 777 666 Estonia: +372 5308 9666
UK Mobile: +44 7973 616 666
--
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.
