On 05/02/16 18:24, Nikolaus Rath wrote:
Assuming that you indeed wrote 3.1 MB, why should it go up? It's
currently at 39.1 GiB - a difference of 3.1 MB would be in the third
digit after the decimal point.
You're right, of course. I seem to have been having problems that day
with orders of magnitude. :( Sorry.
--allow-other --fg --metadata-upload-interval 3600 --compress none
--cachesize 524288000
and mount.log reports:
s3ql.mount.main: Setting cache size to 1404564 MB
Also why is it saying a 1.3 TB cache size when I requested 500 GB?
I'm again puzzled. It says that it *used* 39.1 GB (out of the available
500 GB). I don't see1.3 TB mentioned anywhere at all.
1404564 MB is about 1.3 TB (unless I'm still confused). I limited the
cache size to 500 GB (--cachesize 524288000) so I am surprised that
mount.log states 1404564 MB.
Regards
Cliff.
--
Cliff Stanford
Office: +44 20 0222 1666 UK Mobile: +44 7973 616 666
Spain: +34 952 587 666
http://www.may.be/
--
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.
