mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2021-01-18 12:42:34 -04:00
parent 5193aae385
commit f89721e13f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/bugs/Directory_remotes_with_same_mount_point/comment_2_90351193c14f4c68f9b92640dae82f13._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2021-01-18T16:23:42Z"
content="""
I don't think this has anything to do with mount points being in common.
Consider that, a single disk with a git-annex repository, and 2 directory
special remotes all on it has everything under a common mount point. And
I'm pretty sure works. Also there's just nothing in the relevant code that
cares what the mount point is.
It looks to me like the inode was somehow not the same in the "list" stage
of the command as it was in the "import" stage, or the file that was seen
in the first stage was no longer present in the second stage. I don't see
how that could be a git-annex bug. It could, for example, happen if one SD
card was mounted there at the "list" stage, and then a different card got
mounted there at the "import" stage, or even if the SD card just got
unmounted in between the two stages.
I have not been able to replicate the problem either, using 2 removable
devices on the same mount point, 2 special remotes, etc. So you will have
to show me how to reproduce this if it's actually a bug.
"""]]