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 2022-02-07 12:33:23 -04:00
parent 697114c234
commit e0d5c7a389
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/forum/Content_not_present_and_get_doesn__39__t_retrieve_it/comment_3_74055eed54696331af07ba1721055562._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2022-02-07T16:28:49Z"
content="""
You should not need to fsck regularly. The question is, what happened to
make those files that git-annex thinks are present go missing. One
possible way would be if there was an actual data corruption of files on
the drive.
`git-annex fsck` only mentions `.git/annex/bad/` when it discovers that a
file's content on disk has gotten corrupted. It then moves it to that
directory, and mentions that it has. So this makes me think your drive must
have data corruption.
"""]]