| 1 | | I tested latest git and ran the same tests again. At first it looked ok, the weirdness was gone (that suddenly all dir caps show up as unhealthy). But after having re-run the repair job a few times with one storage node down, some aliases always show up completely healthy, and others show the weird behaviour again; all files are shown healthy but for those few aliases all dir caps are shown unhealthy, get repaired, and still show unhealthy while their repair was claimed to be successful: |
| 2 | | |
| 3 | | {{{ |
| 4 | | *** test3 |
| 5 | | '<root>': not healthy |
| 6 | | repair successful |
| 7 | | 'test.txt': healthy |
| 8 | | done: 2 objects checked |
| 9 | | pre-repair: 1 healthy, 1 unhealthy |
| 10 | | 1 repairs attempted, 1 successful, 0 failed |
| 11 | | post-repair: 1 healthy, 1 unhealthy |
| 12 | | |
| 13 | | *** test4 |
| 14 | | '<root>': not healthy |
| 15 | | repair successful |
| 16 | | done: 1 objects checked |
| 17 | | pre-repair: 0 healthy, 1 unhealthy |
| 18 | | 1 repairs attempted, 1 successful, 0 failed |
| 19 | | post-repair: 0 healthy, 1 unhealthy |
| 20 | | }}} |
| | 1 | I tested latest git and ran the same tests again. I cannot reproduce the error anymore and no weirdness occurs. Looks like it is fixed. |
