Added INFO-level logging to track:
1. Every chunk write: offset, size, etag, target URL
2. Metadata update: total chunks count and calculated file size
3. File size calculation: breakdown of chunks size vs attr size
This will reveal:
- If chunks are being written with correct sizes
- If metadata file size matches sum of chunks
- If there's a mismatch causing the '78 bytes left' EOF
Example output expected:
✓ Wrote chunk to http://volume:8080/3,xxx at offset 0 size 1048576 bytes
✓ Wrote chunk to http://volume:8080/3,yyy at offset 1048576 size 524288 bytes
✓ Writing metadata with 2 chunks, total size: 1572864 bytes
Calculated file size: 1572864 (chunks: 1572864, attr: 0, #chunks: 2)
If we see size=X in write but size=X-78 in read, that's the smoking gun.