summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar augusto <augusto@web>2014-04-04 14:11:26 +0000
committerGravatar admin <admin@branchable.com>2014-04-04 14:11:26 +0000
commit2e4c82aa1fa427ff9c72bf1d92a64e678dcac0c7 (patch)
tree681661fd223d5546680ec37588fc628ff68b603f
parent2e8005cb1d9f2c59ca701627959d62d4234b3b5e (diff)
-rw-r--r--doc/forum/A_tiny_filesystem__63__.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/forum/A_tiny_filesystem__63__.mdwn b/doc/forum/A_tiny_filesystem__63__.mdwn
new file mode 100644
index 000000000..44a397e2f
--- /dev/null
+++ b/doc/forum/A_tiny_filesystem__63__.mdwn
@@ -0,0 +1,7 @@
+First of all, thanks for the amazing work! I've already tried Owncloud, SparkleShare, Unison, rsync and lsycnd. Finally I may have found the real deal.
+
+My main problem with git-annex right now is that it is not fast/reliable enough. The main issues being: broken links now and then (I've probably done something wrong) and the slow: "startup scans", "consistency checks", "attempting to fix here" and "syncing with server". (50 Giga, Work-Server-Home, setup via webapp assistant)
+
+Please, tell me if I'm wrong, but I have the impression that git-annex would get much more robust if it was 100% sure that nobody could mess with its file tree. One possibility would be to add the option (when creating a repo) to make a protected filesystem controlled by git-annex only via FUSE (not something like ShareBox). This could be a tiny filesystem (such as loggedfs) that does nothing but make sure that only git-annex can mount/change files. This would definitely add to speed (reducing checks) and stability.
+
+I'm I being too naive? Most likely there is something I'm overlooking, like the amount of work this would involve.