X-diagnosis-io

Name: X-diagnosis-io
Availability: InStock
Author: openEuler

Diagnose Linux block device and ext4 filesystem performance issues with X-diagnosis tools.

3|2|Updated Apr 24, 2026

Search Tags:#performance #diagnostics #filesystem #linux #storage #io

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill addresses the difficulty of diagnosing complex Linux storage performance issues and filesystem errors by providing a structured, tool-driven approach to identify bottlenecks and root causes.

Core Features & Use Cases

Kernel-Level IO Tracing: Uses specialized X-diagnosis tools to measure latency across block device layers (Q2G, G2I, I2D, D2C).
SCSI Error Analysis: Captures and parses SCSI command timeouts and errors to distinguish between hardware failure and driver issues.
Use Case: When a production database experiences intermittent IO stalls, this skill guides the user to identify whether the latency originates from the IO scheduler, the device driver, or the physical disk hardware.

Quick Start

Execute the X-diagnosis-io skill to perform a comprehensive IO latency analysis on the target device sdb.

Frequently Asked Questions about X-diagnosis-io

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

FAQPage Schema

How do I diagnose Linux IO latency across block device layers?▼

To diagnose Linux IO latency across block device layers, this skill uses specialized X-diagnosis tools to systematically measure latency stages like Q2G, G2I, I2D, and D2C, generating a comprehensive root cause report for performance degradation.

What is the best way to trace SCSI command timeouts and errors in Linux storage?▼

Tracing SCSI command timeouts in Linux storage involves capturing and parsing SCSI errors to distinguish between physical hardware failures and driver issues, which this skill automates to pinpoint the exact root cause of intermittent IO stalls.

How do I identify the root cause of high-frequency write amplification on ext4 filesystems?▼

Identifying high-frequency write amplification on ext4 filesystems requires systematic execution of file-level IO auditing and error tracing, allowing this skill to isolate whether the bottleneck originates from the IO scheduler, device driver, or physical disk.

Can I use automated diagnostics to find why my production database experiences intermittent IO stalls?▼

Yes, you can use automated diagnostic workflows to find why a production database experiences intermittent IO stalls by executing targeted latency tracking and error tracing to determine if the issue originates from the IO scheduler, driver, or hardware.

Does X-diagnosis-io require any specific dependencies to perform filesystem diagnostics?▼

X-diagnosis-io requires no external dependencies to perform automated Linux block device and ext4 filesystem diagnostics, utilizing its built-in scripts and references to execute specialized X-diagnosis workflows for storage performance issues.