Skip to content

Commit c9482cd

Browse files
author
Jill Grant
authored
Update troubleshoot-container-storage.md
Removed numbering as only one step should be a paragraph. Also fixed capitalization issues with H1 and title metadata.
1 parent c9e5065 commit c9482cd

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/storage/container-storage/troubleshoot-container-storage.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Troubleshoot Azure Container Storage Preview
2+
title: Troubleshoot Azure Container Storage preview
33
description: Troubleshoot common problems with Azure Container Storage, including installation and storage pool issues.
44
author: khdownie
55
ms.service: azure-container-storage
@@ -8,7 +8,7 @@ ms.author: kendownie
88
ms.topic: how-to
99
---
1010

11-
# Troubleshoot Azure Container Storage Preview
11+
# Troubleshoot Azure Container Storage preview
1212

1313
[Azure Container Storage](container-storage-introduction.md) is a cloud-based volume management, deployment, and orchestration service built natively for containers. Use this article to troubleshoot common issues with Azure Container Storage and find resolutions to problems.
1414

@@ -75,7 +75,7 @@ If you need a persistent volume, where the volume has a lifecycle independent of
7575

7676
An ephemeral volume is allocated on a single node. When you configure the size of ephemeral volumes for your pods, the size should be less than the available capacity of a single node's ephemeral disk. Otherwise, the pod creation will be in pending status.
7777

78-
1. Use the following command to check if your pod creation is in pending status.
78+
Use the following command to check if your pod creation is in pending status.
7979

8080
```output
8181
$ kubectl get pods
@@ -85,7 +85,7 @@ fiopod 0/1 Pending 0 17s
8585

8686
In this example, the pod `fiopod` is in `Pending` status.
8787

88-
1. Use the following command to check if the pod has the warning event for persistentvolumeclaim creation.
88+
Use the following command to check if the pod has the warning event for persistentvolumeclaim creation.
8989

9090
```output
9191
$ kubectl describe pod fiopod
@@ -98,7 +98,7 @@ Events:
9898

9999
In this example, the pod shows the warning event on creating persistent volume claim `fiopod-ephemeralvolume`.
100100

101-
1. Use the following command to check if the persistent volume claim fails to provision due to insufficient capacity.
101+
Use the following command to check if the persistent volume claim fails to provision due to insufficient capacity.
102102

103103
```output
104104
$ kubectl describe pvc fiopod-ephemeralvolume
@@ -108,7 +108,7 @@ $ kubectl describe pvc fiopod-ephemeralvolume
108108

109109
In this example, `Insufficient Storage` is shown as the reason for volume provisioning failure.
110110

111-
1. Run the following command to check the available capacity of a single node's ephemeral disk.
111+
Run the following command to check the available capacity of a single node's ephemeral disk.
112112

113113
```output
114114
$ kubectl get diskpool -n acstor
@@ -120,7 +120,7 @@ ephemeraldisk-temp-diskpool-xbtlj 75660001280 75031990272 628011008 5609
120120

121121
In this example, the available capacity of temp disk for a single node is `75031990272` bytes or 69 GiB.
122122

123-
1. Adjust the volume storage size below available capacity and re-deploy your pod. See [Deploy a pod with a generic ephemeral volume](use-container-storage-with-temp-ssd.md#3-deploy-a-pod-with-a-generic-ephemeral-volume).
123+
Adjust the volume storage size below available capacity and re-deploy your pod. See [Deploy a pod with a generic ephemeral volume](use-container-storage-with-temp-ssd.md#3-deploy-a-pod-with-a-generic-ephemeral-volume).
124124

125125
## See also
126126

0 commit comments

Comments
 (0)