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
{{ message }}
This repository has been archived by the owner on Oct 22, 2024. It is now read-only.
Being able to disable dax may also be useful for testing the LVM mode with a volume group that is backed by normal disks. Such a volume group then needs to be set up beforehand on each node (i.e. cannot rely on our init containers), but I know that this works because I have done it for the GCE example. The need for a simple LVM driver has come up as part of kubernetes/enhancements#1353.
The text was updated successfully, but these errors were encountered:
The PV must have the filesystem specified for Kubernetes < 1.20 to
apply the FSGroup support (a heuristic in
Kubernetes). external-provisioner >= 2.0.0 only adds that field if it
knows about the default FS.
Fixes: intel#644
(cherry picked from commit 2ba30ba)
pohly
added a commit
to pohly/pmem-CSI
that referenced
this issue
Nov 11, 2020
Another reason why disabling -o dax may be useful is to support apps which just want to do traditional file IO.
-o dax = -o dax=always (see https://www.kernel.org/doc/Documentation/filesystems/dax.txt) enables DAX for all files, whether the application wants that or not. Without it, we get the default behavior (-o dax=inode) where DAX is not enabled by default, but still can be enabled per file or directory via FS_XFLAG_DAX.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Being able to disable dax may also be useful for testing the LVM mode with a volume group that is backed by normal disks. Such a volume group then needs to be set up beforehand on each node (i.e. cannot rely on our init containers), but I know that this works because I have done it for the GCE example. The need for a simple LVM driver has come up as part of kubernetes/enhancements#1353.
The text was updated successfully, but these errors were encountered: