{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/",
        "slug": "dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/"
        },
        "title": "Verify the Linux atomic-write path before relying on managed-disk torn-write protection",
        "summary": "Which layers must support aligned atomic writes before an application relies on Azure managed-disk protection?",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "continuity-recovery",
            "label": "Continuity & recovery",
            "alt": "Paired infrastructure paths converging on a stable recovered service.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "business-continuity",
                "name": "Business Continuity",
                "url": "https://update.dsesecurity.com/topic/business-continuity/"
            },
            {
                "slug": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-09-10T00:30:57+00:00",
        "modified_at": "2026-09-10T00:35:07+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 239,
        "potentially_affected": "Linux application teams evaluating atomic writes on Azure managed disks attached through NVMe controllers.",
        "dse_recommendation": "Prove controller, kernel, filesystem, and application alignment support before changing an application's existing write-protection behavior.",
        "primary_source": {
            "name": "Prevent torn writes with managed disks on Linux VMs - Azure Virtual Machines | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-torn-write-prevention",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<h2>Source facts</h2>\n<p>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&#8217;s procedure checks NVMe namespace capabilities and kernel parameters, then configures direct atomic I/O matching the filesystem block size. <a href=\"https://learn.microsoft.com/en-us/azure/virtual-machines/disks-torn-write-prevention\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>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.</p>\n<h2>DSE recommendation</h2>\n<p>Prove controller, kernel, filesystem, and application alignment support before changing an application&#8217;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&#8217;s actual write path; a supported device is only one part of the proposed configuration.</p>\n<h2>Verification</h2>\n<p>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.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/virtual-machines/disks-torn-write-prevention\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Prevent torn writes with Azure managed disks</a>. Source reviewed September 9, 2026.</p>",
        "content_text": "Source facts\nAzure 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.\nApplicability\nEvaluate 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.\nDSE recommendation\nProve 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.\nVerification\nRetain 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.\nOfficial references\nMicrosoft Learn: Prevent torn writes with Azure managed disks. Source reviewed September 9, 2026.",
        "content_markdown": "## Source facts\n\nAzure 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](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-torn-write-prevention).\n\n## Applicability\n\nEvaluate 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.\n\n## DSE recommendation\n\nProve 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.\n\n## Verification\n\nRetain 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.\n\n## Official references\n\n[Microsoft Learn: Prevent torn writes with Azure managed disks](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-torn-write-prevention). Source reviewed September 9, 2026."
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Verify the Linux atomic-write path before relying on managed-disk torn-write protection",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/",
                "headline": "Verify the Linux atomic-write path before relying on managed-disk torn-write protection",
                "description": "Which layers must support aligned atomic writes before an application relies on Azure managed-disk protection?",
                "abstract": "Which layers must support aligned atomic writes before an application relies on Azure managed-disk protection?",
                "articleBody": "Source facts\nAzure 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.\nApplicability\nEvaluate 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.\nDSE recommendation\nProve 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.\nVerification\nRetain 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.\nOfficial references\nMicrosoft Learn: Prevent torn writes with Azure managed disks. Source reviewed September 9, 2026.",
                "datePublished": "2026-09-10T00:30:57+00:00",
                "dateModified": "2026-09-10T00:35:07+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-059-verify-the-linux-atomic-write-path-before-relying-on-managed-disk-torn-write/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Verify the Linux atomic-write path before relying on managed-disk torn-write protection"
                },
                "articleSection": [
                    "Business Continuity",
                    "IT"
                ],
                "keywords": [
                    "Business Continuity",
                    "IT",
                    "Checklist",
                    "Information priority"
                ],
                "genre": "Checklist",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 239,
                "timeRequired": "PT2M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Prevent torn writes with managed disks on Linux VMs - Azure Virtual Machines | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-torn-write-prevention"
                }
            }
        ]
    }
}