summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar gernot <gernot@web>2011-04-23 16:02:42 +0000
committerGravatar admin <admin@branchable.com>2011-04-23 16:02:42 +0000
commita03dc49bb21190bd2823df9d6b99b04158a955ee (patch)
tree326a2718d2b77f3e8e96505473e0babf76fdfc5f
parent028b338c29fa26a3a821fd79172bc8a42a23387a (diff)
-rw-r--r--doc/forum/wishlist:_define_remotes_that_must_have_all_files.mdwn18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/forum/wishlist:_define_remotes_that_must_have_all_files.mdwn b/doc/forum/wishlist:_define_remotes_that_must_have_all_files.mdwn
new file mode 100644
index 000000000..156cfb009
--- /dev/null
+++ b/doc/forum/wishlist:_define_remotes_that_must_have_all_files.mdwn
@@ -0,0 +1,18 @@
+I would like to be able to name a few remotes that must retain *all* annexed
+files. `git-annex fsck` should warn me if any files are missing from those
+remotes, even if `annex.numcopies` has been satisfied by other remotes.
+
+I imagine this could also be useful for bup remotes, but I haven't actually
+looked at those yet.
+
+Based on existing output, this is what a warning message could look like:
+
+ fsck FILE
+ 3 of 3 trustworthy copies of FILE exist.
+ FILE is, however, still missing from these required remotes:
+ UUID -- Backup Drive 1
+ UUID -- Backup Drive 2
+ Back it up with git-annex copy.
+ Warning
+
+What do you think?