> > > > > 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. > > > Now that I'm aware of the issue the easy way out for me was temporary remount of /var/tmp to a more spacious location using the handy bind option for mount, which allowed my fsck.s3ql to complete without error.
-- 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.
