Question & Answer
Question
What is the best practice of Manual Fix when I see the error in a pod ?
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.\n\t(i.e., without -a or -p options)
Answer
Manual Fix
A manual command execution can be tried from the Node
Steps:
===============================================
1. find pv attached NODE from PV
$ kubectl get pv PVNAME -o yaml | grep "ibm.io/nodename"
2.find device name from PV
$ kubectl get pv PVNAME -o yaml | grep "ibm.io/dm"
3. ssh to Node and execute fsck
$ runon.sh NODE sh (Use internal Tool: https://github.ibm.com/kubernetes-tools/runon )
$ fsck -y /dev/dm-xx (from step2)
$ fsck -y /dev/dm-xx (from step2)
===============================================
Wait for few minutes, kubernetes will retry Volume Mount again and POD should come to "running" state.
[{"Line of Business":{"code":"LOB61","label":"IBM Technology Lifecycle Services"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SGMV159","label":"IBM Support for Red Hat OpenStack Platform"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
12 August 2021
UID
ibm16365021