diff options
author | 2015-09-09 14:02:48 -0400 | |
---|---|---|
committer | 2015-09-09 14:02:48 -0400 | |
commit | 5f603154c96ceecd7cb42eb0440e5c10b8479bda (patch) | |
tree | 8c43b7531f03db649365e9e63569a661d82f63ab | |
parent | cb5d06293232e6bf3902b13d98a438265127b4c8 (diff) |
followup
-rw-r--r-- | doc/bugs/fsck_--incremental-schedule_does_not_work_as_documented/comment_1_f0c7e97cc7697172afa87b372d4d9277._comment | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/bugs/fsck_--incremental-schedule_does_not_work_as_documented/comment_1_f0c7e97cc7697172afa87b372d4d9277._comment b/doc/bugs/fsck_--incremental-schedule_does_not_work_as_documented/comment_1_f0c7e97cc7697172afa87b372d4d9277._comment new file mode 100644 index 000000000..9e2985563 --- /dev/null +++ b/doc/bugs/fsck_--incremental-schedule_does_not_work_as_documented/comment_1_f0c7e97cc7697172afa87b372d4d9277._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-09-09T17:58:09Z" + content=""" +Until version 5.201508125, --time-limit didn't cause a clean shutdown, +and so the fsck database didn't get updated with the last files it checked. +This could result in up to 1000 files being checked over again the next +time the incremental fsck was run. + +I can't reproduce the problem you describe with the current version. +And your transcript seems to be showing the old version, which was known to +have this problem. Only reason I'm not closing this bug immediately +is you seem to have a new enough version on your mac to avoid the problem.. +but it's not clear to me if you're experiencing the problem on the mac. +"""]] |