| Previous | Next |
| STATUS_VOLUME_NOT_CLUSTER_ALIGNED | STATUS_APPX_FILE_NOT_ENCRYPTED |
STATUS_NO_PHYSICALLY_ALIGNED_FREE_SPACE_FOUND
No free extent satisfies the physical-alignment requirement
The volume may have free capacity, but none of the available extents starts and ends on boundaries required by the device or operation. This is especially relevant for persistent memory, large mappings, RAID interleave, and other layouts with stronger alignment constraints.
Freeing a random small file may not help. Determine the exact alignment and extent size, then analyze whether consolidation can create a suitable region. If the underlying partition or namespace starts at the wrong offset, online optimization cannot correct the base geometry.
What to inspect
- Capture the requested size and alignment.
- Inspect namespace, partition, virtual-disk, and file-system offsets.
- Add or recreate capacity if consolidation cannot form an aligned extent.
References
- Microsoft: Plan Storage Spaces volumes
- Microsoft: Direct Access volumes
- Linux kernel: Direct Access for files
Looking for a different code? Search another status or error code.