On Aug 21 2017, [email protected] wrote: > 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?
It seems that this should work, yes. But apparently other people have similar issues: https://stackoverflow.com/questions/23249843/sqlite3-vacuum-database-or-disk-is-full. Maybe try the .pragma approach (https://sqlite.org/tempfiles.html)? You'd need to temporary change the S3QL sources for that though. 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]. For more options, visit https://groups.google.com/d/optout.
