blob: 57c80d7ca32b430201f77369052807ce33b5a5de (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
(checksum...) failed
fsck foo (fixing location log)
Only 1 of 2 trustworthy copies exist of foo
Back it up with git-annex copy.
> You've given me severely partial output, and no test case, but until
> it says "fsck foo", the output is pertaining to some other file than foo.
> As far as I can see, there is no bug here. --[[Joey]]
>> Sorry, I thought it would be obvious, but that's no excuse for not
>> providing additional explanation. The problem is that fsck tells me a
>> file's fsck has failed without printing extra details. In this case, the
>> checksum is OK while I don't have enough copies to satisfy the fsck. The
>> fact that I don't have enough copies is obviously relevant, but I would
>> still like to know if the checksums are OK. -- Richard
>>> I think you're misreading the truncated output you posted. The actual,
>>> full output would make much more sense. --[[Joey]]
>>>> No. I have a total of 14908 annex keys, 3333 of which are on a remote. The only message other than 'checksum OK' and the above is 'git-annex: 11577 failed'.
>>>> I checked several files manually, their checksums are OK so `git annex status` is reporting those files as completely failed when they "only" miss copies. -- Richard
|
