Verify the Linux atomic-write path before relying on managed-disk torn-write protection

Source facts

Azure managed disks provide atomic protection for 8-KiB and 16-KiB writes aligned to their respective block offsets. The documented Linux path requires kernel 6.13 or newer, an NVMe controller, and operating-system and filesystem support for large atomic writes. Microsoft’s procedure checks NVMe namespace capabilities and kernel parameters, then configures direct atomic I/O matching the filesystem block size. Microsoft Learn.

Applicability

Evaluate a specific application and supported Linux storage stack, not merely the Azure disk resource. Identify the kernel, controller, filesystem, application I/O method, and write alignment. Treat changes to database protection behavior as a separate application-owner decision requiring its own vendor guidance.

DSE recommendation

Prove controller, kernel, filesystem, and application alignment support before changing an application’s existing write-protection behavior. Prepare a nonproduction disk for the documented checks and have the data owner approve any formatting operation. Keep capability observations separate from the application’s actual write path; a supported device is only one part of the proposed configuration.

Verification

Retain the namespace atomic-write parameters, kernel limits, filesystem layout, and representative application I/O settings. Run an approved integrity and performance test with the intended block size and alignment, recording both the configuration and observed result. Do not infer that an arbitrary unaligned write receives the same protection. Leave any unsupported layer or uncertain application behavior unresolved before considering removal of an existing safeguard.

Official references

Microsoft Learn: Prevent torn writes with Azure managed disks. Source reviewed September 9, 2026.