Description of problem:
When orphaned or "broken" (i.e., partial layer files) are found on a worker node container directory, cri-o garbage collection halts, allowing the FS to fill up and crashes the node.
Version-Release number of selected component (if applicable):
4.4.4
How reproducible:
always
Steps to Reproduce:
1. start to deploy a pod and "yank the power cord" to create a partial layer file on a worker node
2. When rebooted, GC halts when it encounters a partial/broken/orphaned image layer
3.
Actual results:
Fail
Expected results:
Succeed
Additional info:
The only way that I am I am aware has been used to re-create the issue is by performing the following, during an image pull.
```
echo b >/proc/sysrq-trigger
```