Added a comment

This commit is contained in:
jgoerzen 2022-09-05 22:01:24 +00:00 committed by admin
parent 403dca7c42
commit aa4ba3fc7c

View file

@ -0,0 +1,35 @@
[[!comment format=mdwn
username="jgoerzen"
avatar="http://cdn.libravatar.org/avatar/090740822c9dcdb39ffe506b890981b4"
subject="comment 6"
date="2022-09-05T22:01:24Z"
content="""
With the latest v10 git, I'm seeing some things like this:
```
get Pictures/0_New/5/20-03-31 21-12-12 0184.mp4 (from source...) file content has changed
Unable to access these remotes: source
No other repository is known to contain the file.
failed
```
Now, the file content really had not chnaged. That file looks like this:
```
$ cat 20-03-31\ 21-12-12\ 0184.mp4
/annex/objects/SHA256E-s55936559--0d418e4bb62cfc7ef5b053f8b622dd72794781a49931abc41bb9499acaf51b09.mp4
```
And on-disk, the file is:
```
$ sha256sum 20-03-31\ 21-12-12\ 0184.mp4
0d418e4bb62cfc7ef5b053f8b622dd72794781a49931abc41bb9499acaf51b09 20-03-31 21-12-12 0184.mp4
```
So, this is something different, but it's producing the same result (files left around not checked out). I obvserve that in .dtrash/info, the directory that had such a problem before, zero files now do. But in .dtrash/files, the problem seems to be triggered by a file that has a duplicate somewhere in the source repository (with the same sha256sum). I was able to find another file with the same sha256sum as that one in the same directory. In the origin repo, in which the given files were not present and it's using unlock-present, all instances of the file contained a broken symlink to the appropriate target. In the repo in question here, which uses plain unlock and is on NTFS (though Linux is the OS accessing it), I'm having this problem.
"""]]