Skip to content

Commit 5afb2fd

Browse files
committed
docs: Update 4.3 Docs
Signed-off-by: Bala Harish <161304963+balaharish7@users.noreply.github.com>
1 parent 0bdc88e commit 5afb2fd

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

docs/main/troubleshooting/troubleshooting-replicated-storage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -358,11 +358,11 @@ If you are trying to use `xfs` volumes and the cluster node hosts are running a
358358

359359
### io-engine Fails to Start Due to IOVA Allocation Error
360360

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.
362362

363363
**Workaround**
364364

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:
366366

367367
```
368368
--set openebs.mayastor.io_engine.envcontext=iova-mode=pa

docs/versioned_docs/version-4.3.x/troubleshooting/troubleshooting-replicated-storage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -358,11 +358,11 @@ If you are trying to use `xfs` volumes and the cluster node hosts are running a
358358

359359
### io-engine Fails to Start Due to IOVA Allocation Error
360360

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.
362362

363363
**Workaround**
364364

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:
366366

367367
```
368368
--set openebs.mayastor.io_engine.envcontext=iova-mode=pa

0 commit comments

Comments
 (0)