Closed shuaichang closed 11 months ago
So far, zfile spec lack a crc to verify its meta, i.e. header/trailer and index. The above issue happened when reading index through internet, and got correct length but incorrect data. And the incorrect data is cached by file cache, that will not be evict. Fix #263 enhance bound checking when building index, which will avoid 0-data error and most rand-data error. (For all overlaybd images) Adding crc for zfile is in schedule #262, which will totally avoid such issues. (For new version overlaybd images)
What happened in your environment?
Containerd failed to create container due to
level=error msg="CreateContainer within sandbox \"bcd2f25fed1429f65e063dfd689801744849a214d2219dcadd3d73c6f2745e95\" for &ContainerMetadata{Name:dbr-utils,Attempt:0,} failed" error="failed to create containerd container: failed to attach and mount for snapshot 103: failed to enable target for /sys/kernel/config/target/core/user_999999999/dev_103, failed:failed to create overlaybd device: unknown"
Overlaybd logs around the same
More logs:
What did you expect to happen?
No response
How can we reproduce it?
This issue seems to be reproduced when Blob storage returns 503s
What is the version of your Overlaybd?
0.6.15
What is your OS environment?
ubuntu
Are you willing to submit PRs to fix it?