On Mon, 15 Sep 2025, at 02:36, '[email protected]' via s3ql wrote: > > Running fsck.s3ql --force on this filesystem takes about 4 days, is there >> > a way to avoid doing this? >> >> Which steps take the longest? Depending on that, --fast may or may not help. > > > I'm currently mounting the file system with a fairly large cache size, so it > tends to have a fairly large number of dirty blocks (about 1 million). I > will try mounting with a much smaller cache size in future and see if that > helps...
That's an interesting datapoint, but doesn't answer the question. If you'd like advice on this, you need to tell us which fsck steps take the longest. Best, -Nikolaus -- 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 visit https://groups.google.com/d/msgid/s3ql/06a67a49-81c9-4ec4-b023-47058d593b1b%40app.fastmail.com.
