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

init: Display an additional message when it detects a filesystem that allows writing to files whose write bit is not set.

Browse source
This commit is contained in:
Joey Hess 2017-08-28 13:21:18 -04:00
parent 291d5bb471
commit db2a06b66f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
5 changed files with 40 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

1
doc/bugs/Git-annex_not_properly_detecting_symlink_capability_in_CryFS.mdwn
View file

@ -60,3 +60,4 @@ git-annex-6.20170519-1.fc26.x86_64
I love git-annex.
> [[done]] --[[Joey]]

17
doc/bugs/Git-annex_not_properly_detecting_symlink_capability_in_CryFS/comment_1_78f6f047578974df0dd73740ab05ee8c._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2017-08-28T17:06:35Z"
content="""
git-annex has detected problems with the filesystem, since symlinks
work I think it detected that the filesystem allows writing to a
file even when the file's write bit is not set.
In that situation, a git-annex repository using symlinks will apprear to
work, but if you have an annexed file "foo" in there, and run "echo hi >
foo", it will follow the symlink, and overwrite the annexed file, ignoring
the lack of write bit. This can result in data loss in an unexpected way,
which is why git-annex avoids using the symlinks in this situation.
I've added an additional message to make more clear what is happening.
"""]]