online-file-system-fault-diagnosis

Diagnose Linux file system issues causing IO latency, space exhaustion, and inode depletion.

3|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill online-file-system-fault-diagnosis-openeuler-mirror
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: online-file-system-fault-diagnosis
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/skills/online-file-system-fault-diagnosis
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill online-file-system-fault-diagnosis-openeuler-mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, df, iostat, lsof, dmesg, and includes scripts (resource) components.

What problem does it solve?

This skill addresses critical Linux file system failures such as disk space exhaustion, inode depletion, high IO latency, and file corruption, providing rapid root cause identification without manual log parsing.

Core Features & Use Cases

  • Automated Diagnostics: Collects and analyzes system metrics, kernel logs, and IO statistics to pinpoint the source of file system errors.
  • Scenario Identification: Automatically categorizes issues into common patterns like disk full, inode exhaustion, or IO bottlenecks.
  • Use Case: When a production server reports read-only file system errors or application IO timeouts, this skill performs a comprehensive health check to determine if the issue is hardware-related, resource-constrained, or a configuration error.

Quick Start

Use the online-file-system-fault-diagnosis skill to analyze the file system state for the current system and identify potential bottlenecks.

Frequently Asked Questions about online-file-system-fault-diagnosis

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

FAQPage Schema
How do I diagnose high IO latency on a Linux production server?

Diagnose high IO latency by collecting and analyzing system metrics, kernel logs via dmesg, and IO statistics using iostat to pinpoint the exact file system bottleneck.

Why does my Linux file system suddenly become read-only?

A Linux file system becomes read-only due to disk corruption, space exhaustion, or hardware faults, which can be identified through automated health checks and kernel log analysis.

How to troubleshoot inode depletion in a Linux file system?

Troubleshoot inode depletion by running an automated diagnostic that analyzes storage health metrics to categorize the issue into common patterns like inode exhaustion.

Can I perform non-intrusive file system diagnostics on a production server?

Yes, you can perform non-intrusive file system diagnostics on production servers using read-only data collection tools like df, iostat, lsof, and dmesg.

What is the best way to identify root causes of disk space exhaustion in Linux?

Identify root causes of disk space exhaustion by running comprehensive diagnostic scripts that collect system metrics and generate structured reports of storage health.

Does read-only file system diagnosis require installing additional kernel modules?

No, read-only file system diagnosis relies on standard built-in Linux command-line utilities like bash, df, lsof, and dmesg without requiring additional kernel modules.