You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Troubleshoot common problems with Azure Container Storage, including installation and storage pool issues.
4
4
author: khdownie
5
5
ms.service: azure-container-storage
@@ -8,7 +8,7 @@ ms.author: kendownie
8
8
ms.topic: how-to
9
9
---
10
10
11
-
# Troubleshoot Azure Container Storage Preview
11
+
# Troubleshoot Azure Container Storage preview
12
12
13
13
[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.
14
14
@@ -75,7 +75,7 @@ If you need a persistent volume, where the volume has a lifecycle independent of
75
75
76
76
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.
77
77
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.
79
79
80
80
```output
81
81
$ kubectl get pods
@@ -85,7 +85,7 @@ fiopod 0/1 Pending 0 17s
85
85
86
86
In this example, the pod `fiopod` is in `Pending` status.
87
87
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.
89
89
90
90
```output
91
91
$ kubectl describe pod fiopod
@@ -98,7 +98,7 @@ Events:
98
98
99
99
In this example, the pod shows the warning event on creating persistent volume claim `fiopod-ephemeralvolume`.
100
100
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.
In this example, the available capacity of temp disk for a single node is `75031990272` bytes or 69 GiB.
122
122
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).
0 commit comments