nfs-client-diagnosis

Name: nfs-client-diagnosis
Availability: InStock
Author: openEuler

Diagnose NFS client connectivity, performance, and locking issues using runtime metrics.

3|2|Updated Apr 24, 2026

Search Tags:#performance #troubleshooting #diagnosis #linux #rpc #nfs

Ready to run

npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill nfs-client-diagnosis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nfs-client-diagnosis
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/skills/nfs-client-diagnosis
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill nfs-client-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill resolves complex NFS client issues like mount failures, stale file handles, performance degradation, and lock contention by automating the collection and analysis of system state and protocol behavior.

Core Features & Use Cases

Dual-Track Analysis: Simultaneously performs system state reverse-analysis and NFS protocol forward-deduction to ensure high-confidence root cause identification.
Automated Evidence Collection: Gathers critical diagnostic data including mountstats, RPC statistics, NFSv4 state, and kernel logs.
Use Case: When a production application reports intermittent EIO errors or hangs on an NFS mount, this skill identifies whether the issue stems from network latency, server-side lease expiration, or client-side configuration mismatches.

Quick Start

Use the nfs-client-diagnosis skill to analyze the NFS mount failure on the server 192.168.1.100 for the export path /data/shared.

Frequently Asked Questions about nfs-client-diagnosis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I troubleshoot NFS client mount hangs and stale file handles in Linux?▼

Troubleshoot NFS client mount hangs and stale file handles by correlating system runtime metrics with NFS protocol specifications. Automated evidence collection uses standard Linux utilities like nfsstat, mountstats, and dmesg to perform cross-validated root cause analysis.

Why does my NFS client experience intermittent EIO errors or performance degradation?▼

Intermittent EIO errors and NFS performance degradation are diagnosed by applying dual-track analysis to mountstats and RPC statistics. This identifies whether the root cause is network latency, server-side lease expiration, or client-side configuration mismatches.

What is the best way to diagnose RPC timeouts and NFSv4 lock contention issues?▼

Diagnose RPC timeouts and NFSv4 lock contention by simultaneously performing system state reverse-analysis and NFS protocol forward-deduction. This dual-track approach ensures high-confidence root cause identification for complex client-side locking issues.

Do I need specific diagnostic utilities to analyze NFS client connectivity issues?▼

Analyzing NFS client connectivity requires access to standard Linux diagnostic utilities like nfsstat, mountstats, and dmesg. The skill automates the collection of these critical diagnostic data sources to validate system state against protocol behavior.

Can I use automated diagnosis to find the root cause of NFS client-side configuration mismatches?▼

Automated diagnosis finds NFS client-side configuration mismatches by gathering critical diagnostic data including mountstats, RPC statistics, and NFSv4 state. Cross-validated analysis correlates this evidence with kernel logs to isolate the exact configuration failure.