Hi,
First thanks for S3QL, it is a great bit of software!
One interesting case I have found that other users may want to be aware of
is some of the fsck.s3ql operations make use of sqlite operations that can
make large of temporary files that appear to default to location /var/tmp
This is biting me on a particular server that has been provisioned with a
relatively small /var partition. Setting environment variable
*SQLITE_TMPDIR* and using *fsck.s3ql --cachedir *don't seem to help.
I can see from my "munin" graphs it is the /var partition filling up during
the fsck.s3ql
I am just about to redo my fsck with /var/tmp mounted elsewhere, but does
anybody have any suggestions on how to manage where fsck.s3ql keeps it's
working files?
My S3QL database is 39GB. My /var has 20GB free :-)
Traceback (most recent call last):
File "/usr/bin/fsck.s3ql", line 11, in <module>
load_entry_point('s3ql==2.22', 'console_scripts', 'fsck.s3ql')()
File
"/usr/lib64/python3.4/site-packages/s3ql-2.22-py3.4-linux-x86_64.egg/s3ql/fsck.py",
line 1293, in main
db.execute('VACUUM')
File
"/usr/lib64/python3.4/site-packages/s3ql-2.22-py3.4-linux-x86_64.egg/s3ql/database.py",
line 98, in execute
self.conn.cursor().execute(*a, **kw)
File "src/cursor.c", line 231, in resetcursor
apsw.FullError: FullError: database or disk is full
--
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.
