Skip to main content
NetApp Knowledge Base

How to fix file system errors with Trident or Kubernetes SAN PVs

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

Applies to

  • Kubernetes iSCSI PV
  • Trident ontap-san PVs

Issue

When an ONTAP volume containing a LUN fills up fully, and writes fail, the PV will be mounted readonly by the Kubernetes node's operating system.
If that happens, there may be file system corruption on the partition's XFS or ext4 file system, causing the error:
 
Also, attempting to repair the device after remounting r/w on the worker node, fails (for example):

sh-5.1# xfs_repair /dev/mapper/3600a09803831366437244e4f316e5443
xfs_repair: cannot open /dev/mapper/3600a09803831366437244e4f316e5443: Device or resource busy

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.