Skip to content

Commit 30bddee

Browse files
committed
wording fixes
1 parent a03e0b4 commit 30bddee

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/azure-netapp-files/troubleshoot-capacity-pools.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,10 +34,10 @@ This article describes resolutions to issues you might have when managing capaci
3434
| Changing the capacity pool for a volume is not permitted. | You might not be authorized yet to use this feature. <br> The feature to move a volume to another capacity pool is currently in preview. If you are using this feature for the first time, you need to register the feature first and set `-FeatureName ANFTierChange`. See the registration steps in [Dynamically change the service level of a volume](dynamic-change-volume-service-level.md). |
3535
| The capacity pool size is too small for total volume size. | The error is a result of the destination capacity pool not having the available capacity for the volume being moved. <br> Increase the size of the destination pool, or choose another pool that is larger. See [Resize a capacity pool or a volume](azure-netapp-files-resize-capacity-pools-or-volumes.md). |
3636
| The pool change cannot be completed because a volume called `'{source pool name}'` already exists in the target pool `'{target pool name}'` | This error occurs because the volume with same name already exists in the target capacity pool. Select another capacity pool that does not have a volume with same name. |
37-
| Error changing volume's pool. Pool: `'{target pool name}'` not available or does not exit | Check the status of the destination capacity pool. If it's in a failed state (not "Succeeded") then try performing an update on it by adding a tag name and value pair, then save. See if the capacity comes into a healthy state. |
38-
| Cannot change the volume's pool because the selected pool is the same as the existing pool: `'{Pool Name}'` | Confirm you are moving the volume to the correct destination capacity pool and try again.
39-
| Cannot change QoS type form manual to auto | Once the QoS type is changed to manual, you cannot change it to auto. Given this, there are three options: <ul><li> Do not move the volume if it must be in a capacity pool with QoS type auto.</li><li> Create a new capacity pool with QoS type manual enabled, then you can move the volume to the new capacity pool. </li><li> Change the destination pool to QoS type manual from auto. Then perform the move. </li></ul> |
40-
| Cannot change a volume from a Double Encrypted Pool to a Single Encrypted Pool or from a Single Encrypted Pool to a Double Encrypted Pool | The destination pool must be of same encryption type as the source pool. Move the volumes to the same type of capacity pool. |
37+
| Error changing volume's pool. Pool: `'{target pool name}'` not available or does not exit | You cannot change a volume's capacity pool when the destination capacity pool is not healthy. Check the status of the destination capacity pool. If the pool is in a failed state (not "Succeeded"), try performing an update on the capacity pool by adding a tag name and value pair, then save. |
38+
| Cannot change the volume's pool because the selected pool is the same as the existing pool: `'{Pool Name}'` | Confirm you are moving the volume to the correct destination capacity pool and try again. |
39+
| Cannot change QoS type form manual to auto | Once the QoS type is changed to manual, you cannot change it to auto. Given this, there are three options: <ul><li> Do not move the volume if it must be in a capacity pool with QoS type auto.</li><li> Create a new capacity pool with QoS type manual enabled, then you can move the volume to the new capacity pool. </li><li> Change the destination pool to QoS type manual from auto. Then perform the move. </li></ul> For information about QoS, see [Storage hierarchy of Azure NetApp Files](azure-netapp-files-understand-storage-hierarchy.md#qos_types). |
40+
| Cannot change a volume from a Double Encrypted Pool to a Single Encrypted Pool or from a Single Encrypted Pool to a Double Encrypted Pool | The destination pool must be the same encryption type as the source pool. |
4141

4242
## Next steps
4343

0 commit comments

Comments
 (0)