Skip to content
This repository was archived by the owner on Oct 22, 2024. It is now read-only.

README.md: fix formatting #481

Merged
merged 1 commit into from
Nov 28, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -750,23 +750,23 @@ one with ext4-format and another with xfs-format file system.
PMEM-CSI can create a namespace in the *sector* (alias safe) mode instead of default *fsdax* mode. See [Persistent Memory Programming](https://pmem.io/ndctl/ndctl-create-namespace.html) for more details about namespace modes. The main difference in PMEM-CSI context is that a sector-mode volume will not get 'dax' mount option. The deployment examples do not describe sector mode to keep the amount of combinations smaller. Here are the changes to be made to deploy volumes in sector mode:

- add `nsmode: "sector"` line in parameters section in the storageclass definition file pmem-storageclass-XYZ.yaml:
```
```
parameters:
csi.storage.k8s.io/fstype: ext4
eraseafter: "true"
nsmode: "sector" <-- add this
```
```

* Only if using LVM device mode: Modify pmem-ns-init options to create sector-mode pools in addition to fsdax-mode pools. Add `-useforfsdax` and `-useforsector` options to pmem-ns-init arguments in pmem-csi-lvm.yaml (select the percentage values that fit your needs):
```
```
initContainers:
- args:
- -v=3
- -useforfsdax=60 <-- add this
- -useforsector=40 <-- add this
command:
- /go/bin/pmem-ns-init
```
```

This change can be made either by copying and editing a deployment
yaml file or on-the-fly with `kustomize` as explained in [Run
Expand Down