response
This commit is contained in:
parent
7637208bce
commit
e309146832
1 changed files with 16 additions and 0 deletions
|
@ -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.
|
||||||
|
"""]]
|
Loading…
Reference in a new issue