Back to all scenarios
Scenario #332
Storage
Kubernetes v1.24, AWS EBS
PV Resize Fails After Node Reboot
After a node reboot, a PVC resize request remained pending, blocking pod start.
Find this helpful?
What Happened
VolumeExpansion was triggered via PVC patch. But after a node reboot, controller couldn't find the in-use mount point to complete fsResize.
Diagnosis Steps
- 1PVC status.conditions showed FileSystemResizePending.
- 2CSI node plugin logs showed missing device.
- 3Node reboot removed mount references prematurely.
Root Cause
Resize operation depends on volume being mounted at the time of filesystem expansion.
Fix/Workaround
• Reattached volume by starting pod temporarily on the node.
• Resize completed automatically.Lessons Learned
Filesystem resize requires node readiness and volume mount.
How to Avoid
- 1Schedule resizes during stable node windows.
- 2Use pvc-resize readiness gates in automation.