response

1 files changed, 16 insertions, 0 deletions

diff --git a/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_1_2a71a108fc711617c88ff3b38b83d91c._comment b/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_1_2a71a108fc711617c88ff3b38b83d91c._comment
new file mode 100644
index 000000000..3b5bcb050
--- /dev/null
+++ b/doc/bugs/incremental___40__continued__41___fsck_start_froms_beginning__44___rechecks_files_already_checked_/comment_1_2a71a108fc711617c88ff3b38b83d91c._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-07-30T16:59:40Z"
+ content="""
+What's actually going on is that incremental fsck has switched to using a
+sqlite database to record what files it's fscked. Since making a new commit
+to the database after every single file would tend to slow it down a lot,
+it only commits after each 1000 files fscked.
+
+So, if you're fscking less than 1000 files, it won't resume; with more
+files it will resume after some even thousand multiple of files.
+
+This could probably be improved by making it commit after some period of
+time, like once per minute or so.
+"""]]