summaryrefslogtreecommitdiff
path: root/doc/bugs
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs')
-rw-r--r--doc/bugs/__34__metadata_only__34___git-remote-gcrypt_syncing_files_anyway/comment_1_30a0a715fb9d8738e5ec53296375c1b3._comment8
-rw-r--r--doc/bugs/fsck__44___no_known_copies.mdwn33
-rw-r--r--doc/bugs/git_annex_adjust_--unlock_seems_to_cause_migration_of_a_file_to_another_backend.mdwn58
3 files changed, 99 insertions, 0 deletions
diff --git a/doc/bugs/__34__metadata_only__34___git-remote-gcrypt_syncing_files_anyway/comment_1_30a0a715fb9d8738e5ec53296375c1b3._comment b/doc/bugs/__34__metadata_only__34___git-remote-gcrypt_syncing_files_anyway/comment_1_30a0a715fb9d8738e5ec53296375c1b3._comment
new file mode 100644
index 000000000..515079a79
--- /dev/null
+++ b/doc/bugs/__34__metadata_only__34___git-remote-gcrypt_syncing_files_anyway/comment_1_30a0a715fb9d8738e5ec53296375c1b3._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="chris@f4ea67aa5ae4709d79959f782fcebb5edae9a79b"
+ nickname="chris"
+ subject="similar problem"
+ date="2016-06-02T16:28:18Z"
+ content="""
+For me it's a version 6 repository, but I also get lots of queued transfers to my \"metadata only\" git-remote-gcrypt repo when I launch the webapp. Luckily they don't actually seem to turn up amongst the remote repo's objects (unless I'm missing something), but it causes the assistant to be busy being useless for a while.
+"""]]
diff --git a/doc/bugs/fsck__44___no_known_copies.mdwn b/doc/bugs/fsck__44___no_known_copies.mdwn
new file mode 100644
index 000000000..8d97be3ac
--- /dev/null
+++ b/doc/bugs/fsck__44___no_known_copies.mdwn
@@ -0,0 +1,33 @@
+### Please describe the problem.
+
+Sometimes I end up having files whose contents _do_ exist in this repo, but the location log says otherwise.
+
+For indirect repos, I can just run `annex fsck` on the directory, it says "(fixing location log)", and everything is fine.
+
+But when I try to do the same in a _direct_ repo, it refuses to admit that it just found a copy:
+
+[[!format text """
+┌ frost ~/Attic/Anime (annex)
+┘ annex fsck Foo/
+fsck Foo/[HorribleSubs] Foobar - 01 [720p].mkv (checksum...)
+ ** No known copies exist of Foo/[HorribleSubs] Foobar - 01 [720p].mkv
+failed
+fsck Foo/[HorribleSubs] Foobar - 02 [720p].mkv (checksum...)
+ ** No known copies exist of Foo/[HorribleSubs] Foobar - 02 [720p].mkv
+failed
+...and so on.
+"""]]
+
+(A copy _does_ exist; after all, `annex` just spent 30 seconds checksumming it.)
+
+I work around this bug by switching to indirect mode temporarily, which allows fsck to fix the log.
+
+### What steps will reproduce the problem?
+
+For the fsck bug, I think you just need a file that physically exists in the repo, but not marked as such in the location log.
+
+As for how such files happen in the first place, I've no idea myself. (For what it's worth, the log seems fine.)
+
+### What version of git-annex are you using? On what operating system?
+
+Arch's community/git-annex 6.20160511
diff --git a/doc/bugs/git_annex_adjust_--unlock_seems_to_cause_migration_of_a_file_to_another_backend.mdwn b/doc/bugs/git_annex_adjust_--unlock_seems_to_cause_migration_of_a_file_to_another_backend.mdwn
new file mode 100644
index 000000000..443a1abd2
--- /dev/null
+++ b/doc/bugs/git_annex_adjust_--unlock_seems_to_cause_migration_of_a_file_to_another_backend.mdwn
@@ -0,0 +1,58 @@
+### Please describe the problem.
+
+Interestingly, on my first attempt I had two files which migrated from MD5 to MD5E backend, but may be I have done some steps differently which provoked also also utils/test/test_data.tar.gz to get to the same destiny (actually later replicated on a fresh clone).
+I am also a bit confused why git diff reports change in the symlink if file is already a real file (I guess all the smudging magic)
+
+### 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
+(git)smaug:~exppsy/freesurfer-upstream2[master]git
+$> git status
+On branch master
+Your branch is up-to-date with 'origin/master'.
+nothing to commit, working directory clean
+
+$> git annex adjust --unlock
+adjust
+Checking out files: 100% (468/468), done.
+Switched to branch 'adjusted/master(unlocked)'
+ok
+git annex adjust --unlock 23.70s user 35.25s system 32% cpu 2:59.41 total
+changes on filesystem:
+ vtkutils/vtkKWRGBATransferFunctionEditorTester-scalars.mgh | 2 +-
+
+$> git status
+On branch adjusted/master(unlocked)
+Changes not staged for commit:
+ (use "git add <file>..." to update what will be committed)
+ (use "git checkout -- <file>..." to discard changes in working directory)
+
+ modified: vtkutils/vtkKWRGBATransferFunctionEditorTester-scalars.mgh
+
+no changes added to commit (use "git add" and/or "git commit -a")
+changes on filesystem:
+ vtkutils/vtkKWRGBATransferFunctionEditorTester-scalars.mgh | 2 +-
+
+$> git diff
+diff --git a/vtkutils/vtkKWRGBATransferFunctionEditorTester-scalars.mgh b/vtkutils/vtkKWRGBATransferFunctionEditorTester-scalars.mgh
+index 9ea90d3..7bc0177 100644
+--- a/vtkutils/vtkKWRGBATransferFunctionEditorTester-scalars.mgh
++++ b/vtkutils/vtkKWRGBATransferFunctionEditorTester-scalars.mgh
+@@ -1 +1 @@
+-/annex/objects/SHA256-s655672--85f9b50e8fb8a72a8783152c7ad098c0600222256a7244ccd595cbe67b9ea949
++/annex/objects/SHA256E-s655672--85f9b50e8fb8a72a8783152c7ad098c0600222256a7244ccd595cbe67b9ea949.mgh
+changes on filesystem:
+ vtkutils/vtkKWRGBATransferFunctionEditorTester-scalars.mgh | 2 +-
+
+$> ls -ld vtkutils/vtkKWRGBATransferFunctionEditorTester-scalars.mgh
+-rw------- 1 yoh yoh 655672 Jun 1 23:28 vtkutils/vtkKWRGBATransferFunctionEditorTester-scalars.mgh
+
+$> git annex version
+git-annex version: 6.20160523+gitg33c00ab-1~ndall+1
+
+"""]]
+
+
+[[!meta author=yoh]]