On Friday, April 10, 2020 at 12:30:20 AM UTC+10, Daniel Jagszent wrote: > > > [...]Which is probably what happened; my mount logs show the > > following, which correspond to the time the corrupt DB was created > > (though the disks all have several GB free, so I'm confused as to the > > cause of the error): > > [...] > > apsw.FullError: FullError: database or disk is full > Looks like the same as > https://groups.google.com/forum/#!topic/s3ql/lN5JrIq0_OU > <https://groups.google.com/forum/#%21topic/s3ql/lN5JrIq0_OU> > > Do you maybe have a ramdisk /tmp ? >
No. /tmp and /var/tmp are on disk. There is/was 6-7GB free, the database is 800M which not vacuumed...I suppose with s3ql cache, two copies of the database (vaccum), and some bad luck...perhaps it became 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/23e8ba63-0d59-4865-af4b-50f733b82782%40googlegroups.com.
