Update disks-shared.md #309
Conversation
In a recent support request, setting DiskIOPSReadOnly = 1 caused a boot failure due to read I/O stalling at the UEFI stage.
|
@NAO-MSFT : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 5a9e135: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@roygara - Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
@v-regandowner, is this still under the review? I'm not sure if roygara is an active user... |
|
@NAO-MSFT This is pending review by the product team, who must validate and approve any changes like these. That'll take some time, I'll respond when they get back to me. :) |
|
@roygara, thank you for taking my pull request :) |
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
|
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
|
The author has confirmed that they are still waiting for the product team. @MicrosoftDocs/public-repo-pr-review-team |
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
|
#keep-open |
github-actions
bot
removed
the
inactive
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
|
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
github-actions
bot
removed
the
inactive
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
There was a problem hiding this comment.
Pull request overview
This PR adds a caution warning about setting diskIOPSReadOnly values below 100 for shared Ultra Disks and Premium SSD v2 managed disks. The warning was prompted by a support request where setting DiskIOPSReadOnly = 1 caused VM boot failures due to read I/O stalling at the UEFI stage.
Changes:
- Added a CAUTION alert block warning against setting diskIOPSReadOnly below 100, noting the trade-off between cost reduction and VM startup performance impact
| Both shared Ultra Disks and shared Premium SSD v2 managed disks are priced based on provisioned capacity, total provisioned IOPS (diskIOPSReadWrite + diskIOPSReadOnly) and total provisioned Throughput MB/s (diskMB/sReadWrite + diskMB/sReadOnly). There's no extra charge for each additional VM mount. For example, a shared Ultra Disk with the following configuration (diskSizeGB: 1024, DiskIOPSReadWrite: 10000, DiskMB/sReadWrite: 600, DiskIOPSReadOnly: 100, DiskMB/sReadOnly: 1) is charged with 1024 GiB, 10100 IOPS, and 601 MB/s regardless of whether it's mounted to two VMs or five VMs. | ||
|
|
||
| >[!CAUTION] | ||
| >Avoid setting the diskIOPSReadOnly value below 100. Lower values may reduce costs but can negatively impact the startup performance of VMs attached to the disk. |
There was a problem hiding this comment.
According to Microsoft Learn coding guidelines, this content was substantially modified with the change, so it requires an 'ai-usage' front matter entry. Add either 'ai-usage: ai-generated' or 'ai-usage: ai-assisted' to the article's front matter (lines 1-11) to indicate AI assistance was used in creating this content.
| Both shared Ultra Disks and shared Premium SSD v2 managed disks are priced based on provisioned capacity, total provisioned IOPS (diskIOPSReadWrite + diskIOPSReadOnly) and total provisioned Throughput MB/s (diskMB/sReadWrite + diskMB/sReadOnly). There's no extra charge for each additional VM mount. For example, a shared Ultra Disk with the following configuration (diskSizeGB: 1024, DiskIOPSReadWrite: 10000, DiskMB/sReadWrite: 600, DiskIOPSReadOnly: 100, DiskMB/sReadOnly: 1) is charged with 1024 GiB, 10100 IOPS, and 601 MB/s regardless of whether it's mounted to two VMs or five VMs. | ||
|
|
||
| >[!CAUTION] | ||
| >Avoid setting the diskIOPSReadOnly value below 100. Lower values may reduce costs but can negatively impact the startup performance of VMs attached to the disk. |
There was a problem hiding this comment.
The parameter name 'diskIOPSReadOnly' should be formatted using code style (diskIOPSReadOnly) for consistency with Microsoft Writing Style Guide conventions for technical parameters and to match the formatting used in line 170 where disk parameters are referenced.
5 participants
In a recent support request, setting DiskIOPSReadOnly = 1 caused a boot failure due to read I/O stalling at the UEFI stage.