Back to all scenarios
Scenario #345
Storage
Kubernetes v1.22, Velero, AWS EBS
Read-Only PV Caused Write Failures After Restore
After restoring from backup, the volume was attached as read-only, causing application crashes.
Find this helpful?
What Happened
Backup included PVCs and PVs, but not associated VolumeAttachment states. Restore marked volume read-only to avoid conflicts.
Diagnosis Steps
- 1Pod logs: permission denied on writes.
- 2PVC events: attached in read-only mode.
- 3AWS console showed volume attachment flag.
Root Cause
Velero restored volumes without resetting VolumeAttachment mode.
Fix/Workaround
• Detached and reattached the volume manually as read-write.
• Updated Velero plugin to handle VolumeAttachment explicitly.Lessons Learned
Restores need to preserve attachment metadata.
How to Avoid
- 1Validate post-restore PVC/PV attachment states.
- 2Use snapshot/restore plugins that track attachment mode.