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

comment

Browse source
This commit is contained in:
Joey Hess 2022-09-13 13:08:41 -04:00
parent 0648b6337b
commit 4232eb1c1f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 17 additions and 0 deletions

17
doc/forum/__34__best__34___portable_filesystem_for_external_drive__63__/comment_2_abb716dc8b39e1b20d8725d83a7cc662._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2022-09-13T16:52:30Z"
content="""
Locking is not a concern. git-annex can lock files on a FAT
filesystem as well as on any other. (Network filesystems tend to be the
ones with problems with locking.) Lacking permissions do mean that a `rm -rf`
is more likely to delete annex objects, but a removable drive has a real
risk of accidentially being reformatted, or physically damaged, and you can
untrust it if any of those risks are too large.
I do think that a bare repo on a removable drive can work well,
if the point of the drive is to sneakernet data back and forth, or offload
storage. Keep your local clone on the best available filesystem the OS
provides and work in there. Used in this way, FAT is no worse than S3.
"""]]