mirror of
https://github.com/gluster/glusterdocs.git
synced 2026-02-05 15:47:01 +01:00
c4a0f38df6
Problem: Currently gfid split-brains can be healed using the split-brain resolution CLI or by setting the favorite-child-ploicy to take care of that automatically. But the documentation still says GFID split-brains can not be healed automatically and needs to be done manually. Fix: Adding the steps to resolve the gfid mismatch using the split-brain resolution CLI and updating the other sections appropriately. The Automagic unsplit-brain section does not need any change as such. Signed-off-by: karthik-us <ksubrahm@redhat.com> Fixes: #692
Troubleshooting Guide
This guide describes some commonly seen issues and steps to recover from them.
If that doesn’t help, reach out to the Gluster community, in which case the guide also describes what information needs to be provided in order to debug the issue. At minimum, we need the version of gluster running and the output of gluster volume info.
Where Do I Start?
Is the issue already listed in the component specific troubleshooting sections?
- CLI and Glusterd Issues
- Heal related issues
- Resolving Split brains
- Geo-replication Issues
- Gluster NFS Issues
- File Locks
If that didn't help, here is how to debug further.
Identifying the problem and getting the necessary information to diagnose it is the first step in troubleshooting your Gluster setup. As Gluster operations involve interactions between multiple processes, this can involve multiple steps.
What Happened?
- An operation failed
- High Memory Usage
- A Gluster process crashed