summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-09-19 12:00:06 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-09-19 12:00:06 -0400
commite79890664de6691a7d8ca9ab8369a3ab0a7f267c (patch)
tree84e2144337ee235c98cc4d6d17ab81e1b6a947de /doc
parent6cea492cf23b4ed20a25d72cc3472966b924cd4c (diff)
idea
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/incremental_fsck.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/todo/incremental_fsck.mdwn b/doc/todo/incremental_fsck.mdwn
new file mode 100644
index 000000000..ac6ef1e42
--- /dev/null
+++ b/doc/todo/incremental_fsck.mdwn
@@ -0,0 +1,11 @@
+Justin Azoff realized git-annex should have an incremental fsck.
+
+This requires storing the last fsck time of each object.
+
+I would not be strongly opposed to sqlite, but I think there are other
+places the data could be stored. One possible place is the mode or mtime
+of the .git/annex/objects/xx/yy/$key directories (the parent directories
+of where the content is stored). Perhaps the sticky bit could be used to
+indicate the content has been fsked, and the mtime indicate the time
+of last fsck. Anything that dropped or put in content would need to
+clear the sticky bit. --[[Joey]]