Back to all scenarios
Scenario #358
Storage
Kubernetes v1.24, ext4 vs xfs
Filesystem Type Mismatch During Volume Attach
A pod failed to start because the PV expected ext4 but the node formatted it as xfs.
Find this helpful?
What Happened
Pre-provisioned disk had xfs, but StorageClass defaulted to ext4.
Diagnosis Steps
- 1Attach logs: mount failed: wrong fs type.
- 2blkid on node showed xfs.
Root Cause
Filesystem mismatch between PV and node assumptions.
Fix/Workaround
• Reformatted disk to ext4.
• Aligned StorageClass with PV fsType.Lessons Learned
Filesystem types must match across the stack.
How to Avoid
- 1Explicitly set fsType in StorageClass.
- 2Document provisioner formatting logic.