The strange thing with these reported ‘missing files’ is so far between the two S1s I have seen them appear in 13 different recordings but usually only in one recording per S1 per --check run. The next run may see the same recording list a different missing file. The same recording may list a missing file for that day & sometimes even the next couple of days, but then something changes on the wiz & a different recording starts listing a missing file & the previous recording stops listing a missing file. So far I haven’t pinned down what causes the change.prl wrote:... I haven't changed anything that I think might address the missing files problem. I have thought of making the code that checks whether there recording file is there (and whether its size is consistent with the trunc entries that reference it) retry a couple of times on failure. But it's something I can't reproduce here.
Because --check sits waiting for ages on the one recording before eventually reporting a missing file for that recording I thought it may be LAN problem. But every time I ping either wiz I get very good results.