overlayfs-diagnosis

Name: overlayfs-diagnosis
Availability: InStock
Author: openEuler

Correlate system-level mounts with kernel mechanisms to diagnose OverlayFS failures.

3|2|Updated Apr 24, 2026

Search Tags:#troubleshooting #docker #filesystem #linux #kernel #overlayfs

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill resolves complex OverlayFS failures by simultaneously analyzing system-level symptoms and kernel-level mechanisms, eliminating the guesswork in troubleshooting container storage and filesystem mounting issues.

Core Features & Use Cases

Dual-Track Analysis: Correlates real-time system state (mounts, dmesg, logs) with kernel-level logic (copy-up, readdir, whiteout) to pinpoint root causes.
Automated Branching: Automatically recommends and executes specific diagnostic scripts based on detected error patterns like opaque whiteouts, inode exhaustion, or cross-device configuration errors.
Use Case: When a Docker container fails to start with a "no space left on device" error despite available disk space, this Skill identifies if the issue is actually an inode exhaustion within the overlay2 layer and provides targeted cleanup steps.

Quick Start

Use the overlayfs-diagnosis skill to analyze the current system state and identify the root cause of the overlay mount failure on the target directory.

Frequently Asked Questions about overlayfs-diagnosis

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

FAQPage Schema

Why does my Docker container fail to start with a no space left on device error when disk space is available?▼

A no space left on device error with available disk space often indicates inode exhaustion within the overlay2 layer. This Skill correlates system-level mount configurations with kernel-level mechanisms to pinpoint this exact root cause and provide targeted cleanup steps.

How do I troubleshoot OverlayFS mount point inconsistencies in Linux?▼

To troubleshoot OverlayFS mount point inconsistencies, this Skill applies dual-track analysis by correlating real-time system state like mounts and dmesg logs with kernel-level logic to isolate the root cause and generate structured remediation plans.

What is the best way to diagnose container storage driver performance degradation?▼

Diagnosing container storage driver performance degradation is best handled by correlating system-level symptoms with kernel-level behavioral mechanisms like copy-up and readdir. This approach eliminates guesswork and provides evidence-based fault isolation for Linux environments.

Can I use automated branching to identify opaque whiteouts and cross-device configuration errors in OverlayFS?▼

Yes, you can use automated branching to identify opaque whiteouts and cross-device configuration errors. This Skill automatically recommends and executes specific diagnostic scripts based on detected error patterns in the kernel and system state.

Does this dual-track OverlayFS diagnosis approach work without external dependencies?▼

Yes, this dual-track OverlayFS diagnosis works without external dependencies. It relies entirely on built-in scripts and references to analyze kernel-level behavioral mechanisms and system-level mount configurations for automated root cause analysis.

When should I not use an automated OverlayFS diagnostic tool for filesystem failures?▼

You should not use an automated OverlayFS diagnostic tool when the filesystem failure is unrelated to container storage drivers or mount point inconsistencies. This Skill is specifically designed for Linux overlayfs issues involving kernel-level copy-up, readdir, and whiteout mechanisms.