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
Copy file name to clipboardExpand all lines: docs/main/troubleshooting/troubleshooting-replicated-storage.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -358,11 +358,11 @@ If you are trying to use `xfs` volumes and the cluster node hosts are running a
358
358
359
359
### io-engine Fails to Start Due to IOVA Allocation Error
360
360
361
-
When the io-engine fails to start with the error message `couldn't allocate memory due to IOVA exceeding limits of current DMA mask` it typically indicates that IOMMU is enabled on the host system.
361
+
When the io-engine fails to start with the error message `couldn't allocate memory due to IOVA exceeding limits of current DMA mask` it is likely that the host node has IOMMU enabled.
362
362
363
363
**Workaround**
364
364
365
-
Configure the io-engine to use physical address (PA) mode by setting the following Helm parameter during Replicated PV Mayastor installation:
365
+
Configure the io-engine to use physical address (PA) mode for DMA by setting the following Helm parameter during Replicated PV Mayastor installation:
Copy file name to clipboardExpand all lines: docs/versioned_docs/version-4.3.x/troubleshooting/troubleshooting-replicated-storage.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -358,11 +358,11 @@ If you are trying to use `xfs` volumes and the cluster node hosts are running a
358
358
359
359
### io-engine Fails to Start Due to IOVA Allocation Error
360
360
361
-
When the io-engine fails to start with the error message `couldn't allocate memory due to IOVA exceeding limits of current DMA mask` it typically indicates that IOMMU is enabled on the host system.
361
+
When the io-engine fails to start with the error message `couldn't allocate memory due to IOVA exceeding limits of current DMA mask` it is likely that the host node has IOMMU enabled.
362
362
363
363
**Workaround**
364
364
365
-
Configure the io-engine to use physical address (PA) mode by setting the following Helm parameter during Replicated PV Mayastor installation:
365
+
Configure the io-engine to use physical address (PA) mode for DMA by setting the following Helm parameter during Replicated PV Mayastor installation:
0 commit comments