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

comment

Browse source
This commit is contained in:
Joey Hess 2023-05-01 13:09:47 -04:00
parent 57c1b4f5e5
commit d98a7f0afc
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/forum/git_annex_sync_update_remote/comment_4_221e01e024595f444e629db510eb60be._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2023-05-01T17:02:17Z"
content="""
One way is to run this on your system:
git-annex drop foo.h5 --from cluster
If you really have a reason to want to run `git-annex drop` on the cluster
itself, it needs to be able to connect back to your system in order to to
verify that your system still has a copy of the file it's dropping.
Imagine what would happen if you ran `git-annex drop` of the same file on
your system and on the cluster at the same time, if that check were not
done. The file would be dropped from both places and so you'd lose data.
You can use `git-annex drop --force` on the cluster if you're sure that
your system still has the content. But it's probably going to be better to
just use `git-annex drop --from cluster` run on your system, which avoids
the potential for a mistake causing data loss.
"""]]