We saw a case where the recovery stats reported `recovered_bytes` greater than `length_in_bytes` for one file:

```
GET /_recovery?detailed

200 OK
...
{
  "name": "_buk.fdt",
  "length_in_bytes": 26891307173,
  "reused": false,
  "recovered_in_bytes": 35324928266,
  "recovered_from_snapshot_in_bytes": 8433621093
}
...
```

NB `35324928266 == 26891307173 + 8433621093`

This causes Elasticsearch to compute a negative value for the reserved space on the target node of this recovery, which prevents stats APIs from working. This appears to be caused by a network-level failure which triggers a retry without first cancelling an ongoing download of a different file with the same name from the snapshot repository.

---

### Workaround

Restart the target node to clear these stats.
server/src/main/java/org/elasticsearch/indices/recovery/RecoveryState.java
builder.humanReadableField(
                Fields.RECOVERED_FROM_SNAPSHOT_IN_BYTES,
                Fields.RECOVERED_FROM_SNAPSHOT,
                new ByteSizeValue(recoveredFromSnapshot)
            );
            builder.endObject();
            return builder;
        }
        @Override
        public boolean equals(Object obj) {
            if (obj instanceof FileDetail other) {
                return name.equals(other.name)
                    && length == other.length()
                    && reused == other.reused()
                    && recovered == other.recovered
                    && recoveredFromSnapshot == other.recoveredFromSnapshot;
            }
            return false;
        }
        @Override
        public int hashCode() {
            int result = name.hashCode();
            result = 31 * result + Long.hashCode(length);
            result = 31 * result + Long.hashCode(recovered);
            result = 31 * result + Long.hashCode(recoveredFromSnapshot);
            result = 31 * result + (reused ? 1 : 0);
            return result;
        }
        @Override
        public String toString() {