Skip to main content
NetApp Knowledge Base

input output error on the mount point of an ontap-san XFS formatted Trident PV

  1. Last updated
  2. Save as PDF
Views:
86
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • Trident for Kubernetes and Openshift
  • ontap-san or ontap-san-economy driver
  • ONTAP 9
  • Persistent Volume (PV)

Issue

  • Trident ontap-san (iSCSI) XFs Volume became corrupted when the volume ran 100% full
  • When using XFS fsType PVs the following error may occur when trying to either mount or unmount (attach/detach to/from node): 

can't determine if directory /var/lib/kubelet/pods/<POD-UUID>/volumes/kubernetes.io~csi/<PVC-UUID>/mount exists; stat /var/lib/kubelet/pods/<POD-UUID>/volumes/kubernetes.io~csi/<PVC-UUID>/mount: input/output error

  • Replacing the PV is not possible due to the exiting one not being able to be cleaned up/deleted, since umount detaching through Trident doesn't work due to a stat error on the mount point.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.