From 4c08cd5c0a3a2875c7045b1c784531ff4514f087 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawl2I59wfwq505F9W0a6f7sFDcC9neWcc24" Date: Mon, 5 May 2014 14:03:34 +0000 Subject: [PATCH 01/25] --- doc/forum/Basic_set_up_with_one_remote.mdwn | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/Basic_set_up_with_one_remote.mdwn diff --git a/doc/forum/Basic_set_up_with_one_remote.mdwn b/doc/forum/Basic_set_up_with_one_remote.mdwn new file mode 100644 index 0000000000..669c281d3d --- /dev/null +++ b/doc/forum/Basic_set_up_with_one_remote.mdwn @@ -0,0 +1,14 @@ +Hi, I'm new to git annex and so far it's looking really useful. I'm convinced what I'm trying to achieve is possible, but I can't seem to hit upon the right combination. Here's what I'd like to set up. + +One server with git annex / rsync / ssh access, but configured such that it contains a history of all the files as a full backup. +Two clients WITHOUT ssh access (these are portable machines and I'd rather not open any ports I don't absolutely have to). + +I've used the assistant to set up syncing between all three, using a jabber account to send signals and the server to pass on the files between the machines. This all works beautifully. But what I can't seem to get right is the server / backup aspect. If I set up the server using the assistant as a remote, and set it to "full backup" from the drop down list, it doesn't seem to have any files in the repository except in the .git/annex/objects folder. Which are all cryptic file names and not really accessible. If I run commands such as + +> git annex find + +(which should list all files as far as I can tell) in the server repository, it doesn't list any files at all. As the clients are all set up as direct repositories I can't access any history of the files there, so this doesn't seem to be quite what I'm after. The sync is working, but I really want the backup / history aspect as well. + +Does anyone know if what I want is possible? If so hopefully I'm close and someone can point out where I've gone wrong. I'm not afraid of the command line, but the assistant is a very convenient way to get started. + +Thanks for your help. From af79cf93ef0b50cdc37268491f33cf8c3297e9fd Mon Sep 17 00:00:00 2001 From: martin Date: Mon, 5 May 2014 14:37:53 +0000 Subject: [PATCH 02/25] --- .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 0aa4d03ca9..15790e5eff 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -1,6 +1,6 @@ The Date resolution for FAT is only 2 seconds for the "last modified time." This leads to the strange behaviour, that after umount and remount of an usb drive (direct mode) git-annex thinks that suddenly approx. 50% of -the files are modified. (after remount the times appears to be rounded to even values) +the files are modified. (after remount the times appears to be rounded to even values) So git-annex is not real "guilty" but it would be fine to create a "workaround" for this problem... Possible the best solution for this is to set even values for the seconds in the filesystem and in annex internal tables direct after the "git annex get". Other solution would be to treat differences up to 1s in modification time as unmodified or create an new parameter like rsync's "modify-window" for this. To do an "git annex sync" or git annex add is in my opinion not a good option, because one could add so Bad file content by accident... From 02f68a7ef654e16df4f056619e63c1991ed12ce8 Mon Sep 17 00:00:00 2001 From: martin Date: Mon, 5 May 2014 15:05:10 +0000 Subject: [PATCH 03/25] --- .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 15790e5eff..290dbdceed 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -1,6 +1,6 @@ The Date resolution for FAT is only 2 seconds for the "last modified time." This leads to the strange behaviour, that after umount and remount of an usb drive (direct mode) git-annex thinks that suddenly approx. 50% of -the files are modified. (after remount the times appears to be rounded to even values) So git-annex is not real "guilty" but it would be fine to create a "workaround" for this problem... +the files are modified. (after remount the times appears to be rounded to even values - the inode cache before unmount had 1 second resolution) So git-annex is not real "guilty" but it would be fine to create a "workaround" for this problem... Possible the best solution for this is to set even values for the seconds in the filesystem and in annex internal tables direct after the "git annex get". Other solution would be to treat differences up to 1s in modification time as unmodified or create an new parameter like rsync's "modify-window" for this. To do an "git annex sync" or git annex add is in my opinion not a good option, because one could add so Bad file content by accident... From 67b9b5eb3b77e76e356e1900c4a1f21e87355792 Mon Sep 17 00:00:00 2001 From: martin Date: Mon, 5 May 2014 15:10:54 +0000 Subject: [PATCH 04/25] --- ...ion_for_mtime_2s--__62___implications.mdwn | 30 +++++++++---------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 290dbdceed..f70ca2c428 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -7,16 +7,16 @@ Other solution would be to treat differences up to 1s in modification time as un Here's an konsole session to show this behaviour: -martin@dell:$ mount /mnt/transfer/ +$ mount /mnt/transfer/ -martin@dell:$ git clone source/ /mnt/transfer/transfer-repo +$ git clone source/ /mnt/transfer/transfer-repo Klone nach '/mnt/transfer/transfer-repo'... Fertig. -martin@dell:$ cd /mnt/transfer/transfer-repo/ +$ cd /mnt/transfer/transfer-repo/ -martin@dell:$ git annex init "test" +$ git annex init "test" init test Detected a filesystem without fifo support. @@ -36,12 +36,12 @@ group here (merging origin/git-annex into git-annex...) ok (Recording state in git...) -martin@dell:$ git annex wanted here standard +$ git annex wanted here standard wanted here ok (Recording state in git...) -martin@dell:$ git annex get --auto +$ git annex get --auto get n01.mp3 (from origin...) SHA256E-s1159018--5674452792970dc03e9ba47d3a8af5ad7c8da6b3ca19e8e64b9a4cf462d4a92d.mp3 @@ -65,21 +65,21 @@ ok –--> All 29 files (n01.mp3 to n29.mp3) successfully got (Recording state in git...) -martin@dell:$ git annex status +$ git annex status -martin@dell:$ stat * >../stat-before-umount +$ stat * >../stat-before-umount -martin@dell:$ cd / +$ cd / -martin@dell:/$ umount /mnt/transfer +$ umount /mnt/transfer -martin@dell:/$ mount /mnt/transfer +$ mount /mnt/transfer -martin@dell:/$ cd /mnt/transfer/transfer-repo +$ cd /mnt/transfer/transfer-repo -martin@dell:/mnt/transfer/transfer-repo$ stat * >../stat-after-remount +$ stat * >../stat-after-remount -martin@dell:/mnt/transfer/transfer-repo$ git annex status +$ git annex status M n05.mp3 @@ -105,7 +105,7 @@ M n26.mp3 M n27.mp3 -martin@dell:$ diff -u ../stat-before-umount ../stat-after-remount | grep -B8 "+Modifiziert" | grep -E "Datei:|Modifi" +$ diff -u ../stat-before-umount ../stat-after-remount | grep -B8 "+Modifiziert" | grep -E "Datei:|Modifi" Datei: „n05.mp3“ -Modifiziert: 2014-05-03 19:42:39.000000000 +0200 From 4976b92af266c6bde73eee5aea87f8cf18e6a0d0 Mon Sep 17 00:00:00 2001 From: martin Date: Mon, 5 May 2014 15:19:39 +0000 Subject: [PATCH 05/25] --- .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index f70ca2c428..ed62ae002c 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -29,7 +29,7 @@ init test ok (Recording state in git...) -martin@dell:$ git annex group here transfer +$ git annex group here transfer group here (merging origin/git-annex into git-annex...) (Recording state in git...) From c010fea763e527e6167f008e72a8a6c05a5a5b2a Mon Sep 17 00:00:00 2001 From: martin Date: Mon, 5 May 2014 15:25:21 +0000 Subject: [PATCH 06/25] --- .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index ed62ae002c..9255749f51 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -65,6 +65,7 @@ ok –--> All 29 files (n01.mp3 to n29.mp3) successfully got (Recording state in git...) + $ git annex status $ stat * >../stat-before-umount From 256cebc964cd8e7a4a9ee86a56a16d0e613e92a6 Mon Sep 17 00:00:00 2001 From: martin Date: Mon, 5 May 2014 15:31:48 +0000 Subject: [PATCH 07/25] --- .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 9255749f51..5ede475d2c 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -1,4 +1,4 @@ -The Date resolution for FAT is only 2 seconds for the "last modified time." +The Date resolution of the FAT filesystem is only 2 seconds for the "last modified time." This leads to the strange behaviour, that after umount and remount of an usb drive (direct mode) git-annex thinks that suddenly approx. 50% of the files are modified. (after remount the times appears to be rounded to even values - the inode cache before unmount had 1 second resolution) So git-annex is not real "guilty" but it would be fine to create a "workaround" for this problem... From 5c573c82ddb38d1f4b1d8f2e31264724018c88a0 Mon Sep 17 00:00:00 2001 From: martin Date: Mon, 5 May 2014 15:36:56 +0000 Subject: [PATCH 08/25] --- .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 5ede475d2c..84955c83e8 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -1,6 +1,6 @@ The Date resolution of the FAT filesystem is only 2 seconds for the "last modified time." This leads to the strange behaviour, that after umount and remount of an usb drive (direct mode) git-annex thinks that suddenly approx. 50% of -the files are modified. (after remount the times appears to be rounded to even values - the inode cache before unmount had 1 second resolution) So git-annex is not real "guilty" but it would be fine to create a "workaround" for this problem... +the files are modified. (after remount the "seconds" appears to be rounded to even values - the inode cache before unmount had 1 second resolution) So git-annex is not real "guilty" but it would be fine to create a "workaround" for this problem... Possible the best solution for this is to set even values for the seconds in the filesystem and in annex internal tables direct after the "git annex get". Other solution would be to treat differences up to 1s in modification time as unmodified or create an new parameter like rsync's "modify-window" for this. To do an "git annex sync" or git annex add is in my opinion not a good option, because one could add so Bad file content by accident... From 52173d97c004c338aa0e3044b896fc3b7edab718 Mon Sep 17 00:00:00 2001 From: "50.56.228.64" <50.56.228.64@web> Date: Mon, 5 May 2014 17:14:06 +0000 Subject: [PATCH 09/25] poll vote (OpenStack SWIFT) --- doc/design/assistant/polls/prioritizing_special_remotes.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/design/assistant/polls/prioritizing_special_remotes.mdwn b/doc/design/assistant/polls/prioritizing_special_remotes.mdwn index a87a674ba4..8fbe2a7d97 100644 --- a/doc/design/assistant/polls/prioritizing_special_remotes.mdwn +++ b/doc/design/assistant/polls/prioritizing_special_remotes.mdwn @@ -6,7 +6,7 @@ locally paired systems, and remote servers with rsync. Help me prioritize my work: What special remote would you most like to use with the git-annex assistant? -[[!poll open=yes 16 "Amazon S3 (done)" 12 "Amazon Glacier (done)" 9 "Box.com (done)" 72 "My phone (or MP3 player)" 25 "Tahoe-LAFS" 10 "OpenStack SWIFT" 33 "Google Drive"]] +[[!poll open=yes 16 "Amazon S3 (done)" 12 "Amazon Glacier (done)" 9 "Box.com (done)" 72 "My phone (or MP3 player)" 25 "Tahoe-LAFS" 11 "OpenStack SWIFT" 33 "Google Drive"]] This poll is ordered with the options I consider easiest to build listed first. Mostly because git-annex already supports them and they From b8ff2c8f2971710b48c16571da75a704d5c156b9 Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/FHnTlSBo1eCGJRwueeKeB6.RCaPbGMPr5jxx8A--#ce0d8" Date: Mon, 5 May 2014 21:46:51 +0000 Subject: [PATCH 10/25] --- .../Upgrade_Does_not_Complete_on_OS_X.mdwn | 29 +++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 doc/bugs/Upgrade_Does_not_Complete_on_OS_X.mdwn diff --git a/doc/bugs/Upgrade_Does_not_Complete_on_OS_X.mdwn b/doc/bugs/Upgrade_Does_not_Complete_on_OS_X.mdwn new file mode 100644 index 0000000000..a69ea1e39b --- /dev/null +++ b/doc/bugs/Upgrade_Does_not_Complete_on_OS_X.mdwn @@ -0,0 +1,29 @@ +### Please describe the problem. + +Every time git-annex launches (after a reboot). It prompts me to finish upgrade, even though the binary is not updated. (All my repos are set to not auto update and this happens on all my repos). + + +### What steps will reproduce the problem? + +Relaunching git-annex. + + +### What version of git-annex are you using? On what operating system? + +OS X 10.9 + +git-annex version: 5.20140419-g477c0c0 +build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV FsEvents XMPP DNS Feeds Quvi TDFA CryptoHash +key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL +remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external + + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log + + +# End of transcript or log. +"""]] From 29c513a30a3f9b816601dc69be65239019f14ee8 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawk3HGoDpnOPob5jOjvIootmkve1-nCpRiI" Date: Tue, 6 May 2014 06:10:07 +0000 Subject: [PATCH 11/25] Added a comment: ssh remote defaults to bare repo --- ...nt_1_3ad06a0dbebf62e6440f549e77af59b6._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/Basic_set_up_with_one_remote/comment_1_3ad06a0dbebf62e6440f549e77af59b6._comment diff --git a/doc/forum/Basic_set_up_with_one_remote/comment_1_3ad06a0dbebf62e6440f549e77af59b6._comment b/doc/forum/Basic_set_up_with_one_remote/comment_1_3ad06a0dbebf62e6440f549e77af59b6._comment new file mode 100644 index 0000000000..c262611075 --- /dev/null +++ b/doc/forum/Basic_set_up_with_one_remote/comment_1_3ad06a0dbebf62e6440f549e77af59b6._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawk3HGoDpnOPob5jOjvIootmkve1-nCpRiI" + nickname="Kalle" + subject="ssh remote defaults to bare repo" + date="2014-05-06T06:10:06Z" + content=""" +Hi, + +When setting up a ssh remote the default is to create a repo without a human readable file structure. To achieve what you are looking for you have to initialize a git annex repo on the server and then add the remote to the clients. afaik this has to be done using the command line interface. + +If i remember correctly you add remotes with `git remote add ssh://example.com/path/to/annex` + +Cant find the docs atm (I'm commuting and at my final dest) + +"""]] From a4387a2c3c062fe78321f938eb091b7d2353ad35 Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:24:14 +0000 Subject: [PATCH 12/25] --- ...AT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 84955c83e8..a228d3d209 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -7,6 +7,8 @@ Other solution would be to treat differences up to 1s in modification time as un Here's an konsole session to show this behaviour: + + $ mount /mnt/transfer/ $ git clone source/ /mnt/transfer/transfer-repo @@ -156,3 +158,5 @@ $ diff -u ../stat-before-umount ../stat-after-remount | grep -B8 "+Modifiziert" -Modifiziert: 2014-05-03 19:44:39.000000000 +0200 +Modifiziert: 2014-05-03 19:44:38.000000000 +0200 + + From 2cbd0f6335253d0b129ec43839d4e808bf8af56b Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:28:27 +0000 Subject: [PATCH 13/25] --- ..._Date_resolution_for_mtime_2s--__62___implications.mdwn | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index a228d3d209..b421034000 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -7,11 +7,11 @@ Other solution would be to treat differences up to 1s in modification time as un Here's an konsole session to show this behaviour: - -$ mount /mnt/transfer/ -$ git clone source/ /mnt/transfer/transfer-repo + $ mount /mnt/transfer/ + + $ git clone source/ /mnt/transfer/transfer-repo Klone nach '/mnt/transfer/transfer-repo'... Fertig. @@ -158,5 +158,4 @@ $ diff -u ../stat-before-umount ../stat-after-remount | grep -B8 "+Modifiziert" -Modifiziert: 2014-05-03 19:44:39.000000000 +0200 +Modifiziert: 2014-05-03 19:44:38.000000000 +0200 - From 9459ae4f6fbcb447d1b2840a4e7b23434a7ab423 Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:29:17 +0000 Subject: [PATCH 14/25] --- ...T:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index b421034000..121a51fbb3 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -9,9 +9,8 @@ Here's an konsole session to show this behaviour: - $ mount /mnt/transfer/ - - $ git clone source/ /mnt/transfer/transfer-repo + $ mount /mnt/transfer/ + $ git clone source/ /mnt/transfer/transfer-repo Klone nach '/mnt/transfer/transfer-repo'... Fertig. From e2bc97de81b1bb93ed8dfa12baed6bf1fbdcd1f2 Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:30:12 +0000 Subject: [PATCH 15/25] --- .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 121a51fbb3..5abfaaf0bc 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -9,7 +9,7 @@ Here's an konsole session to show this behaviour: - $ mount /mnt/transfer/ + $ mount /mnt/transfer/ $ git clone source/ /mnt/transfer/transfer-repo Klone nach '/mnt/transfer/transfer-repo'... From 9b5ff45875a30d260f15c6cc51bdf8827c5ed83c Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:30:37 +0000 Subject: [PATCH 16/25] --- .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 5abfaaf0bc..6f0f4196fc 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -9,7 +9,7 @@ Here's an konsole session to show this behaviour: - $ mount /mnt/transfer/ + $ mount /mnt/transfer/ $ git clone source/ /mnt/transfer/transfer-repo Klone nach '/mnt/transfer/transfer-repo'... From 5b7da9db3c67bee2ca7fc8c9660dfc9fe3c62d59 Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:33:14 +0000 Subject: [PATCH 17/25] --- ...Date_resolution_for_mtime_2s--__62___implications.mdwn | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 6f0f4196fc..c997e65f57 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -7,10 +7,10 @@ Other solution would be to treat differences up to 1s in modification time as un Here's an konsole session to show this behaviour: + - - $ mount /mnt/transfer/ - $ git clone source/ /mnt/transfer/transfer-repo +$ mount /mnt/transfer/ +$ git clone source/ /mnt/transfer/transfer-repo Klone nach '/mnt/transfer/transfer-repo'... Fertig. @@ -157,4 +157,4 @@ $ diff -u ../stat-before-umount ../stat-after-remount | grep -B8 "+Modifiziert" -Modifiziert: 2014-05-03 19:44:39.000000000 +0200 +Modifiziert: 2014-05-03 19:44:38.000000000 +0200 - + From af457d3205cbcc3ebd005fe6e84ec13df3780b97 Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:33:57 +0000 Subject: [PATCH 18/25] --- .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index c997e65f57..c10c0ddb81 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -9,7 +9,7 @@ Here's an konsole session to show this behaviour: -$ mount /mnt/transfer/ +$ mount /mnt/transfer/\\ $ git clone source/ /mnt/transfer/transfer-repo Klone nach '/mnt/transfer/transfer-repo'... From 1d37e08683923770b352eecc4e4fa5aee98dec77 Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:36:26 +0000 Subject: [PATCH 19/25] --- ...lution_for_mtime_2s--__62___implications.mdwn | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index c10c0ddb81..b17a7c305e 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -7,17 +7,15 @@ Other solution would be to treat differences up to 1s in modification time as un Here's an konsole session to show this behaviour: - + $ mount /mnt/transfer/ + $ git clone source/ /mnt/transfer/transfer-repo -$ mount /mnt/transfer/\\ -$ git clone source/ /mnt/transfer/transfer-repo + Klone nach '/mnt/transfer/transfer-repo'... + Fertig. -Klone nach '/mnt/transfer/transfer-repo'... -Fertig. + $ cd /mnt/transfer/transfer-repo/ -$ cd /mnt/transfer/transfer-repo/ - -$ git annex init "test" + $ git annex init "test" init test Detected a filesystem without fifo support. @@ -157,4 +155,4 @@ $ diff -u ../stat-before-umount ../stat-after-remount | grep -B8 "+Modifiziert" -Modifiziert: 2014-05-03 19:44:39.000000000 +0200 +Modifiziert: 2014-05-03 19:44:38.000000000 +0200 - + From 143bc5af84d4cdee72347c4f4603ba3a3832f834 Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:37:30 +0000 Subject: [PATCH 20/25] --- ...ion_for_mtime_2s--__62___implications.mdwn | 27 +++++++++---------- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index b17a7c305e..9dcc21be04 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -14,28 +14,27 @@ Here's an konsole session to show this behaviour: Fertig. $ cd /mnt/transfer/transfer-repo/ - $ git annex init "test" -init test - Detected a filesystem without fifo support. + init test + Detected a filesystem without fifo support. - Disabling ssh connection caching. + Disabling ssh connection caching. - Detected a crippled filesystem. + Detected a crippled filesystem. - Enabling direct mode. -ok -(Recording state in git...) + Enabling direct mode. + ok + (Recording state in git...) -$ git annex group here transfer + $ git annex group here transfer -group here (merging origin/git-annex into git-annex...) -(Recording state in git...) -ok -(Recording state in git...) + group here (merging origin/git-annex into git-annex...) + (Recording state in git...) + ok + (Recording state in git...) -$ git annex wanted here standard + $ git annex wanted here standard wanted here ok (Recording state in git...) From 3c28f96dd431bea2b0b3abcd1357110486886a54 Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:40:41 +0000 Subject: [PATCH 21/25] --- ...ion_for_mtime_2s--__62___implications.mdwn | 170 ++++++++---------- 1 file changed, 75 insertions(+), 95 deletions(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 9dcc21be04..3f4bbccd8b 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -36,122 +36,102 @@ Here's an konsole session to show this behaviour: $ git annex wanted here standard -wanted here ok -(Recording state in git...) + wanted here ok + (Recording state in git...) -$ git annex get --auto + $ git annex get --auto -get n01.mp3 (from origin...) -SHA256E-s1159018--5674452792970dc03e9ba47d3a8af5ad7c8da6b3ca19e8e64b9a4cf462d4a92d.mp3 - 1159018 100% 82.62MB/s 0:00:00 (xfer#1, to-check=0/1) + get n01.mp3 (from origin...) + SHA256E-s1159018--5674452792970dc03e9ba47d3a8af5ad7c8da6b3ca19e8e64b9a4cf462d4a92d.mp3 + 1159018 100% 82.62MB/s 0:00:00 (xfer#1, to-check=0/1) -sent 1159308 bytes received 31 bytes 2318678.00 bytes/sec -total size is 1159018 speedup is 1.00 -ok + sent 1159308 bytes received 31 bytes 2318678.00 bytes/sec + total size is 1159018 speedup is 1.00 + ok -get n02.mp3 (from origin...) -SHA256E-s1622113--03998dc10c4839d5ab9aeaceaa63f0363c9d728aaaca2a2707f025c7b9e920a3.mp3 + get n02.mp3 (from origin...) + SHA256E-s1622113--03998dc10c4839d5ab9aeaceaa63f0363c9d728aaaca2a2707f025c7b9e920a3.mp3 1622113 100% 34.45MB/s 0:00:00 (xfer#1, to-check=0/1) -sent 1622459 bytes received 31 bytes 3244980.00 bytes/sec -total size is 1622113 speedup is 1.00 -ok + sent 1622459 bytes received 31 bytes 3244980.00 bytes/sec + total size is 1622113 speedup is 1.00 + ok -... -... + ... + ... -–--> All 29 files (n01.mp3 to n29.mp3) successfully got + –--> All 29 files (n01.mp3 to n29.mp3) successfully got -(Recording state in git...) + (Recording state in git...) -$ git annex status + $ git annex status + $ stat * >../stat-before-umount + $ cd / + $ umount /mnt/transfer + $ mount /mnt/transfer + $ cd /mnt/transfer/transfer-repo + $ stat * >../stat-after-remount + $ git annex status + M n05.mp3 + M n10.mp3 + M n11.mp3 + M n13.mp3 + M n16.mp3 + M n17.mp3 + M n20.mp3 + M n22.mp3 + M n23.mp3 + M n24.mp3 + M n26.mp3 + M n27.mp3 + $ diff -u ../stat-before-umount ../stat-after-remount | grep -B8 "+Modifiziert" | grep -E "Datei:|Modifi" -$ stat * >../stat-before-umount + Datei: „n05.mp3“ + -Modifiziert: 2014-05-03 19:42:39.000000000 +0200 + +Modifiziert: 2014-05-03 19:42:38.000000000 +0200 -$ cd / + Datei: „n10.mp3“ + -Modifiziert: 2014-05-03 19:43:05.000000000 +0200 + +Modifiziert: 2014-05-03 19:43:04.000000000 +0200 -$ umount /mnt/transfer + Datei: „n11.mp3“ + -Modifiziert: 2014-05-03 19:43:07.000000000 +0200 + +Modifiziert: 2014-05-03 19:43:06.000000000 +0200 -$ mount /mnt/transfer + Datei: „n13.mp3“ + -Modifiziert: 2014-05-03 19:43:15.000000000 +0200 + +Modifiziert: 2014-05-03 19:43:14.000000000 +0200 -$ cd /mnt/transfer/transfer-repo + Datei: „n16.mp3“ + -Modifiziert: 2014-05-03 19:43:21.000000000 +0200 + +Modifiziert: 2014-05-03 19:43:20.000000000 +0200 -$ stat * >../stat-after-remount + Datei: „n17.mp3“ + -Modifiziert: 2014-05-03 19:43:29.000000000 +0200 + +Modifiziert: 2014-05-03 19:43:28.000000000 +0200 -$ git annex status + Datei: „n20.mp3“ + -Modifiziert: 2014-05-03 19:43:53.000000000 +0200 + +Modifiziert: 2014-05-03 19:43:52.000000000 +0200 -M n05.mp3 + Datei: „n22.mp3“ + -Modifiziert: 2014-05-03 19:44:13.000000000 +0200 + +Modifiziert: 2014-05-03 19:44:12.000000000 +0200 -M n10.mp3 + Datei: „n23.mp3“ + -Modifiziert: 2014-05-03 19:44:23.000000000 +0200 + +Modifiziert: 2014-05-03 19:44:22.000000000 +0200 -M n11.mp3 + Datei: „n24.mp3“ + -Modifiziert: 2014-05-03 19:44:31.000000000 +0200 + +Modifiziert: 2014-05-03 19:44:30.000000000 +0200 -M n13.mp3 + Datei: „n26.mp3“ + -Modifiziert: 2014-05-03 19:44:35.000000000 +0200 + +Modifiziert: 2014-05-03 19:44:34.000000000 +0200 -M n16.mp3 - -M n17.mp3 - -M n20.mp3 - -M n22.mp3 - -M n23.mp3 - -M n24.mp3 - -M n26.mp3 - -M n27.mp3 - -$ diff -u ../stat-before-umount ../stat-after-remount | grep -B8 "+Modifiziert" | grep -E "Datei:|Modifi" - - Datei: „n05.mp3“ --Modifiziert: 2014-05-03 19:42:39.000000000 +0200 -+Modifiziert: 2014-05-03 19:42:38.000000000 +0200 - - Datei: „n10.mp3“ --Modifiziert: 2014-05-03 19:43:05.000000000 +0200 -+Modifiziert: 2014-05-03 19:43:04.000000000 +0200 - - Datei: „n11.mp3“ --Modifiziert: 2014-05-03 19:43:07.000000000 +0200 -+Modifiziert: 2014-05-03 19:43:06.000000000 +0200 - - Datei: „n13.mp3“ --Modifiziert: 2014-05-03 19:43:15.000000000 +0200 -+Modifiziert: 2014-05-03 19:43:14.000000000 +0200 - - Datei: „n16.mp3“ --Modifiziert: 2014-05-03 19:43:21.000000000 +0200 -+Modifiziert: 2014-05-03 19:43:20.000000000 +0200 - - Datei: „n17.mp3“ --Modifiziert: 2014-05-03 19:43:29.000000000 +0200 -+Modifiziert: 2014-05-03 19:43:28.000000000 +0200 - - Datei: „n20.mp3“ --Modifiziert: 2014-05-03 19:43:53.000000000 +0200 -+Modifiziert: 2014-05-03 19:43:52.000000000 +0200 - - Datei: „n22.mp3“ --Modifiziert: 2014-05-03 19:44:13.000000000 +0200 -+Modifiziert: 2014-05-03 19:44:12.000000000 +0200 - - Datei: „n23.mp3“ --Modifiziert: 2014-05-03 19:44:23.000000000 +0200 -+Modifiziert: 2014-05-03 19:44:22.000000000 +0200 - - Datei: „n24.mp3“ --Modifiziert: 2014-05-03 19:44:31.000000000 +0200 -+Modifiziert: 2014-05-03 19:44:30.000000000 +0200 - - Datei: „n26.mp3“ --Modifiziert: 2014-05-03 19:44:35.000000000 +0200 -+Modifiziert: 2014-05-03 19:44:34.000000000 +0200 - - Datei: „n27.mp3“ --Modifiziert: 2014-05-03 19:44:39.000000000 +0200 -+Modifiziert: 2014-05-03 19:44:38.000000000 +0200 + Datei: „n27.mp3“ + -Modifiziert: 2014-05-03 19:44:39.000000000 +0200 + +Modifiziert: 2014-05-03 19:44:38.000000000 +0200 From 40e0a83d296fd8cd22be1b78a1923a53d16a2065 Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:42:32 +0000 Subject: [PATCH 22/25] --- .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 3f4bbccd8b..0deb3ceab6 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -2,7 +2,7 @@ The Date resolution of the FAT filesystem is only 2 seconds for the "last modifi This leads to the strange behaviour, that after umount and remount of an usb drive (direct mode) git-annex thinks that suddenly approx. 50% of the files are modified. (after remount the "seconds" appears to be rounded to even values - the inode cache before unmount had 1 second resolution) So git-annex is not real "guilty" but it would be fine to create a "workaround" for this problem... -Possible the best solution for this is to set even values for the seconds in the filesystem and in annex internal tables direct after the "git annex get". +Possible the best solution for this is to set even values for the seconds in the filesystem and in annex internal tables direct after the `git annex get`. Other solution would be to treat differences up to 1s in modification time as unmodified or create an new parameter like rsync's "modify-window" for this. To do an "git annex sync" or git annex add is in my opinion not a good option, because one could add so Bad file content by accident... Here's an konsole session to show this behaviour: From 898f9947537fd10c2d3491017f6b43f7360e04e7 Mon Sep 17 00:00:00 2001 From: martin Date: Tue, 6 May 2014 08:43:27 +0000 Subject: [PATCH 23/25] --- .../FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn index 0deb3ceab6..6752923176 100644 --- a/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn +++ b/doc/forum/FAT:_Date_resolution_for_mtime_2s--__62___implications.mdwn @@ -3,7 +3,7 @@ This leads to the strange behaviour, that after umount and remount of an usb dri the files are modified. (after remount the "seconds" appears to be rounded to even values - the inode cache before unmount had 1 second resolution) So git-annex is not real "guilty" but it would be fine to create a "workaround" for this problem... Possible the best solution for this is to set even values for the seconds in the filesystem and in annex internal tables direct after the `git annex get`. -Other solution would be to treat differences up to 1s in modification time as unmodified or create an new parameter like rsync's "modify-window" for this. To do an "git annex sync" or git annex add is in my opinion not a good option, because one could add so Bad file content by accident... +Other solution would be to treat differences up to 1s in modification time as unmodified or create an new parameter like rsync's "modify-window" for this. To do an `git annex sync` or `git annex add` is in my opinion not a good option, because one could add so Bad file content by accident... Here's an konsole session to show this behaviour: From 238996d9b366f8c7df38c4577dad54431b6af057 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawl2I59wfwq505F9W0a6f7sFDcC9neWcc24" Date: Tue, 6 May 2014 12:45:06 +0000 Subject: [PATCH 24/25] Added a comment --- ...comment_2_59e18e759c907b8adabf8c34eef08065._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Basic_set_up_with_one_remote/comment_2_59e18e759c907b8adabf8c34eef08065._comment diff --git a/doc/forum/Basic_set_up_with_one_remote/comment_2_59e18e759c907b8adabf8c34eef08065._comment b/doc/forum/Basic_set_up_with_one_remote/comment_2_59e18e759c907b8adabf8c34eef08065._comment new file mode 100644 index 0000000000..40ed2c8b5a --- /dev/null +++ b/doc/forum/Basic_set_up_with_one_remote/comment_2_59e18e759c907b8adabf8c34eef08065._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawl2I59wfwq505F9W0a6f7sFDcC9neWcc24" + nickname="Andrew" + subject="comment 2" + date="2014-05-06T12:45:05Z" + content=""" +OK that sounds reasonable. I'll give it a go. + +I don't mind so much that the remote is not human readable as I wont be browsing directly on the remote, but what I did find disconcerting is that I didn't seem to be able to access any files. For example if I lose both the client machines, how do I get access to the files on the remote? +"""]] From 5d7b831e1fe5c87eb6f6894dd8acea8bc500e6db Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawl2I59wfwq505F9W0a6f7sFDcC9neWcc24" Date: Tue, 6 May 2014 17:35:21 +0000 Subject: [PATCH 25/25] Added a comment: Still missing something --- ..._5221a713ee3f65fa2740c9fa6cb1db0f._comment | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 doc/forum/Basic_set_up_with_one_remote/comment_3_5221a713ee3f65fa2740c9fa6cb1db0f._comment diff --git a/doc/forum/Basic_set_up_with_one_remote/comment_3_5221a713ee3f65fa2740c9fa6cb1db0f._comment b/doc/forum/Basic_set_up_with_one_remote/comment_3_5221a713ee3f65fa2740c9fa6cb1db0f._comment new file mode 100644 index 0000000000..43dbb5d635 --- /dev/null +++ b/doc/forum/Basic_set_up_with_one_remote/comment_3_5221a713ee3f65fa2740c9fa6cb1db0f._comment @@ -0,0 +1,27 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawl2I59wfwq505F9W0a6f7sFDcC9neWcc24" + nickname="Andrew" + subject="Still missing something" + date="2014-05-06T17:35:20Z" + content=""" +On the server I ran + +git init +git annex init + +On client I ran + +git init +git annex init +git annex direct + +then dropped some files in and ran + +git sync + +This didn't upload any files. I now have a broken link on the server without the actual file. + +When I tried to set up the server in the same way, then used the web assistant to create the repository on the client and then combine it with the manually created repository on the server, it actually worked for the first file. I could see a working link to the file it had just uploaded. But any subsequent files didn't reflect in the file structure. Additional files would show up in the .git/annex/objects folder, but again I have no way to explore these. git annex find showed nothing, git annex status showed only the first file and git log didn't show much. I tried re-adding this remote to a new annex repository, but it didn't give me access to the files or the history of the files. I'm confused! + +Is it me or is this not working as expected? +"""]]