Skip to content

Latest commit

 

History

History
30 lines (27 loc) · 1.52 KB

csi-debug.md

File metadata and controls

30 lines (27 loc) · 1.52 KB

CSI driver debug tips

Case#1: volume create/delete issue

  • locate csi driver pod
$ kubectl get po -o wide -n kube-system | grep csi-smb-controller
NAME                                            READY   STATUS    RESTARTS   AGE     IP             NODE
csi-smb-controller-56bfddd689-dh5tk       5/5     Running   0          35s     10.240.0.19    k8s-agentpool-22533604-0
csi-smb-controller-56bfddd689-sl4ll       5/5     Running   0          35s     10.240.0.23    k8s-agentpool-22533604-1
  • get csi driver logs
$ kubectl logs `kubectl get po -n kube-system | grep csi-smb-controller | cut -d ' ' -f1` -c smb -n kube-system > csi-smb-controller.log

note: there could be multiple controller pods, if there are no helpful logs, try to get logs from other controller pods

Case#2: volume mount/unmount failed

  • locate csi driver pod and make sure which pod do tha actual volume mount/unmount
$ kubectl get po -o wide -n kube-system | grep csi-smb-node
NAME                                            READY   STATUS    RESTARTS   AGE     IP             NODE
csi-smb-node-cvgbs                        3/3     Running   0          7m4s    10.240.0.35    k8s-agentpool-22533604-1
csi-smb-node-dr4s4                        3/3     Running   0          7m4s    10.240.0.4     k8s-agentpool-22533604-0
  • get csi driver logs
$ kubectl logs csi-smb-node-cvgbs -c smb -n kube-system > csi-smb-node.log
  • get /var/log/messages and dmesg output when there is mount failure on Linux node