This repository has been archived by the owner on Oct 22, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 55
OpenShift: setting up XFS volumes fails during xfs_io #1058
Labels
OpenShift
issues occuring on Red Hat OpenShift
Comments
There is a potential workaround: the work done my |
pohly
added a commit
to pohly/pmem-CSI
that referenced
this issue
Jan 2, 2022
On OpenShift, the xfs_io command that was used while creating XFS volumes hangs while getting loaded (kernel or container runtime bug?). This problem can be avoided by making the same ioctl calls as in that binary directly from the PMEM-CSI driver. Fixes: intel#1058
pohly
added a commit
to pohly/pmem-CSI
that referenced
this issue
Jan 3, 2022
On OpenShift, the xfs_io command that was used while creating XFS volumes hangs while getting loaded (kernel or container runtime bug?). This problem can be avoided by making the same ioctl calls as in that binary directly from the PMEM-CSI driver. Fixes: intel#1058
Corresponding upstream issue: https://bugzilla.redhat.com/show_bug.cgi?id=2034194 |
Reopening - we probably need to backport and do a v1.0.2. |
pohly
added a commit
to pohly/pmem-CSI
that referenced
this issue
Jan 12, 2022
On OpenShift, the xfs_io command that was used while creating XFS volumes hangs while getting loaded (kernel or container runtime bug?). This problem can be avoided by making the same ioctl calls as in that binary directly from the PMEM-CSI driver. Fixes: intel#1058 (cherry picked from commit 4f1a2d8)
This is contained in 1.0.2. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@kirin1994 ran into an issue when testing on OpenShift: volumes with XFS get created, but then the xfs_io command which sets the 2m extsize for huge pages hangs.
Invoking that binary in the PMEM-CSI DaemonSet container via
kubectl exec
without any parameters also hangs. Invoking it under strace shows that it gets stuck very early, probably even before it reachesmain()
. This looks like an issue with the kernel or container runtime.The text was updated successfully, but these errors were encountered: