diff options
11 files changed, 187 insertions, 0 deletions
diff --git a/doc/forum/Broken_symlinks_remain_after_drop/comment_2_399ba969a17a41a022c69a1f7c480857._comment b/doc/forum/Broken_symlinks_remain_after_drop/comment_2_399ba969a17a41a022c69a1f7c480857._comment new file mode 100644 index 000000000..f9225b066 --- /dev/null +++ b/doc/forum/Broken_symlinks_remain_after_drop/comment_2_399ba969a17a41a022c69a1f7c480857._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="ghen1" + ip="66.41.70.34" + subject="comment 2" + date="2014-10-09T02:20:14Z" + content=""" +Thank you for your reply and suggestions. How could I maintain an archive folder on a local repo without those changes (moved files) being reflected in the other repos? Would this require branching as well? How does the assistant do it? +"""]] diff --git a/doc/forum/How_to_list_all_existing_metadata_types__63__.mdwn b/doc/forum/How_to_list_all_existing_metadata_types__63__.mdwn new file mode 100644 index 000000000..43b3c1cfc --- /dev/null +++ b/doc/forum/How_to_list_all_existing_metadata_types__63__.mdwn @@ -0,0 +1,15 @@ +Is there any way to list all of the existing tag and metadata field types? What I mean is, I have files tagged with several different tags, files with several metadata fields; is there any way to list all the tag and field names being used (not all the files WITH those tags)? + +For example, something like: + + git annex metadata --listfields + lastchanged + month + month-lastchanged + year + year-lastchanged + + git annex metadata --listtags + Public + Personal + Work diff --git a/doc/forum/Preserving_extended_attributes.mdwn b/doc/forum/Preserving_extended_attributes.mdwn new file mode 100644 index 000000000..5533daeea --- /dev/null +++ b/doc/forum/Preserving_extended_attributes.mdwn @@ -0,0 +1,5 @@ +Hey, + +I was wondering if it is currently possible to let the assistant (or git-annex in general) preserve extended attributes. I didn't find any options hinting at this, although it should be possible at least in theory by using the metadata system of git-annex... + +Considering that some applications use extended attributes to store custom meta data (like tags etc.), I think it would be valuable to have such an option... diff --git a/doc/forum/files_being_dropped_undesirably.mdwn b/doc/forum/files_being_dropped_undesirably.mdwn new file mode 100644 index 000000000..2a4d1bf7c --- /dev/null +++ b/doc/forum/files_being_dropped_undesirably.mdwn @@ -0,0 +1,47 @@ +I currently am using 3 repositories for my personal annex, and on each of them I'm running the assistant (they are normal git annex repositories). However all my files are migrating to my work desktop. My other two repositories seem to keep dropping them. + +Last night on my laptop I did a "git annex get *" to pull _all_ the files onto it. I saw in the .git/annex/daemon.log that each file was being dropped as soon as it was gotten. The output of "git annex get" showed files being transfered across, and the .git/annex/daemon.log showed files being dropped straight away. Currently I'd like to keep all my files on all my repositories (and perhaps later I'll revise that). + +Could someone please help me understand why annex is dropping my files, and what I could do to keep them on all my repositories? + +Here is the output of a get for a single file: + + ~/Documents/personal-annex $ git annex get 2014/09/15/IMG_1123.JPG + get 2014/09/15/IMG_1123.JPG (from pea15.local_Documents_annexpersonal...) + SHA256E-s1841221--deeaa13935907ad606f941397bb57432c1eccfd5c361b8c16d2b19bfbe8437a6.JPG + 1,841,221 100% 11.40MB/s 0:00:00 (xfr#1, to-chk=0/1) + ok + (Recording state in git...) + + +Here is the corresponding daemon.log output: + + [2014-10-09 09:11:34 AEDT] Committer: Committing changes to git + [2ok + (Recording state in git...) + (Recording state in git...) + (Recording state in git...) + drop 2014/09/15/IMG_1123.JPG 01(checking pea15.local_Documents_annexpersonal...) 4-10-09 09:11:34 AEDT] Pusher: Syncing with pea15.local_Documents_annexpersonal + [2014-10-09 09:11:35 AEDT] Committer: Committing changes to git + To ssh://geoffc@git-annex-pea-15-geoffc_Documents.2Fannex.2Dpersonal/~/Documents/annex-personal/ + 04742c0..d1a5a36 git-annex -> synced/git-annex + [2014-10-09 09:11:38 AEDT] Pusher: Syncing with pea15.local_Documents_annexpersonal + Everything up-to-date + + +And here is a snippet from my .git/config: + + [annex] + uuid = 57c4e6d1-0c6b-4c49-a235-4119d3864c14 + version = 5 + direct = true + #diskreserve = 2 gigabyte + autoupgrade = ask + debug = false + expireunused = false + autocommit = true + [remote "pea15.local_Documents_annexpersonal"] + url = ssh://geoffc@git-annex-pea-15-geoffc_Documents.2Fannex.2Dpersonal/~/Documents/annex-personal/ + fetch = +refs/heads/*:refs/remotes/pea15.local_Documents_annexpersonal/* + annex-uuid = 2ef6bbfe-662f-48ba-aa52-8e2f82bcfb15 + annex-cost = 175.0 diff --git a/doc/forum/files_being_dropped_undesirably/comment_1_d03f8ed7d3f3da58612bf238c1790fb4._comment b/doc/forum/files_being_dropped_undesirably/comment_1_d03f8ed7d3f3da58612bf238c1790fb4._comment new file mode 100644 index 000000000..887b12ac9 --- /dev/null +++ b/doc/forum/files_being_dropped_undesirably/comment_1_d03f8ed7d3f3da58612bf238c1790fb4._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="Bram" + ip="81.20.68.186" + subject="Group and wanted expression" + date="2014-10-09T12:09:58Z" + content=""" +What are the group and wanted expressions for your repository? + + git annex group . + git annex wanted . +"""]] diff --git a/doc/forum/how_to_set_up_syncing_for_multiple_computer_and_a_centralized_backup_unit.mdwn b/doc/forum/how_to_set_up_syncing_for_multiple_computer_and_a_centralized_backup_unit.mdwn new file mode 100644 index 000000000..960f563ce --- /dev/null +++ b/doc/forum/how_to_set_up_syncing_for_multiple_computer_and_a_centralized_backup_unit.mdwn @@ -0,0 +1,9 @@ +Been using Unison for a while to sync a folder at three different computers (can be on or off simultanously). However, I've for different reasons been looking for a different solution. Here comes git annex.e + +I started out with one computer, generated a new repo locally and at the server (a synology nas) with the assistant. Then i put all my files into the local directory and the files uploaded to the server. All good. I put the local computer in client mode and the server in backup mode. Then i configured a second computer with an empty repo folder, was asked to join repos, did that. Also put this computer in client mode and the server in backup. After a while all the files was located in the second computers repo directory. Yes, I was confident this was the way to go. + +Howewer, doing the same with my laptop was not successful at all. After similar setup as above it only downloaded about 5% of the data. Bummer. While I tried to study the logs I thought I should check the second computers repo. That was modified and a lot of files where gone. Wow...of course I have backup, but I was hoping for a proper and consistent operation. + +So what causes this? Should I not put the server in backup mode? Anyone have an idea? + +Other thoughts? diff --git a/doc/tips/How_To_Permanently_Delete_a_File__63__.mdwn b/doc/tips/How_To_Permanently_Delete_a_File__63__.mdwn new file mode 100644 index 000000000..fd654079f --- /dev/null +++ b/doc/tips/How_To_Permanently_Delete_a_File__63__.mdwn @@ -0,0 +1,13 @@ +Hi, + +We have several large git annex repos where all of the files are on remotes and we want to got through and clean up the repositories by deleting some subset of files. + +What is the fastest way to permanently delete files from a git annex repository with remotes? + +I guess I can to ``git annex drop --numcopies=0 <file>; git rm <file>``. Does that actually delete the file permanently? + +Is there a faster way? + +Thanks, + +Mike diff --git a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_1_7f2cefb0991789be5a960eb9c0a9df3f._comment b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_1_7f2cefb0991789be5a960eb9c0a9df3f._comment new file mode 100644 index 000000000..c0eb14174 --- /dev/null +++ b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_1_7f2cefb0991789be5a960eb9c0a9df3f._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmwjQzWgiD7_I3zw-_91rMRf_6qoThupis" + nickname="Mike" + subject="comment 1" + date="2014-10-09T17:53:04Z" + content=""" +I experimented with this by making an empty directory with two empty files and one file with some content. I added them all, then ran ``git annex drop --numcopies=0 <file>; git rm <file>`` on one of the empty files. + +Interestingly, what happened is that git annex deleted the empty file from .git/annex/objects, but left the directory structure. In this case the link pointed to: + +.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 + +After the drop command what was left was the following empty directory: + +.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/ + +Also interestingly and terrifyingly, because there were two empty files, both pointed to the same object, the ``git annex drop`` command deleted the file in the objects directory, and now the second link points to nothing. The file is done. + +This means that if you have a git annex repository and you have two copies of a file, and you think to yourself, \"oh, let me just delete one, I don't need two\", and you use the method above, you will permanently and irrevocably delete both files. Not good. + +Any better ideas on how to do this? +"""]] diff --git a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_2_d13b456c5b3990082c16e78a50f5db91._comment b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_2_d13b456c5b3990082c16e78a50f5db91._comment new file mode 100644 index 000000000..959ac282f --- /dev/null +++ b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_2_d13b456c5b3990082c16e78a50f5db91._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmwjQzWgiD7_I3zw-_91rMRf_6qoThupis" + nickname="Mike" + subject="comment 2" + date="2014-10-09T18:02:59Z" + content=""" +Tried another approach: + +``git annex unannex <file>; rm <file>`` + +This does not delete the original, and it only works if you do ``git annex get <file>`` first. It won't update the remote, unless you cd into that remote and run ``git annex sync`` there. After that there is the illusion the file is done, but its content is still in .git/annex/objects. In my test case I could vim into the file in question in the objects directory and it was still there. + +So ``git annex drop`` deletes both copies of duplicate files and so is too dangerous to use and ``git annex unannex`` doesn't delete the file anywhere. I am a little stuck here, what do I do? +"""]] diff --git a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_3_854c17ff8cb38486c4bef618d1e94919._comment b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_3_854c17ff8cb38486c4bef618d1e94919._comment new file mode 100644 index 000000000..404d12ae4 --- /dev/null +++ b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_3_854c17ff8cb38486c4bef618d1e94919._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmwjQzWgiD7_I3zw-_91rMRf_6qoThupis" + nickname="Mike" + subject="comment 3" + date="2014-10-09T18:16:34Z" + content=""" +OK, I should have read more before writing. + +It seems like the procedure is described here: +http://git-annex.branchable.com/walkthrough/unused_data/ + +The process is: +1. rm files or directories +2. git annex sync in all remotes (that is a pain, I wish I only had to do it once) +3. git annex unused +4. git annex dropunused +5. Repeat 4 and 5 on any repository where the data is stored + +That does work for me, it is just slightly cumbersome. If there is another way or if I am missing something, please let me know. + +Thanks, + +Mike +"""]] diff --git a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment new file mode 100644 index 000000000..6e8ddc595 --- /dev/null +++ b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.54" + subject="comment 4" + date="2014-10-09T18:23:58Z" + content=""" +This post is misplaced, it is not a tip about how to use git-annex, but a question. I will be moving it to the forum after posting this comment. + +The right answer is probably to run: `git annex drop $file`, with no --numcopies, no --force, etc. Just let git-annex do its job; it will check the remotes to ensure that enough copies of the file exist to make it safe to drop the content of the file from the local repository. ( +Note that --numcopies=0 is very unsafe, you're asking git-annex to delete even the last copy of your data without checking when you do that.) + +If your goal is to get rid of every copy of this file from every repository that has a copy, I suggest just `git rm $file; git commit`, followed by running `git annex unused` in the various repositories to clean them up. + +There is a faster way, which is to run `git annex drop --from $remote` for each remote that has the file. If you want to get rid of every copy of the file, for sure, you could add a --force to that. + +git-annex deduplicates data, so it's completely expected that if two files have the same content, dropping one will remove the content of the other. + +I cannot reproduce any .git/annex/objects/foo empty directories being left behind by git-annex after doing that. Perhaps you are not using a current version of git-annex? +"""]] |