Description of problem:
[RFE] Please add a new sub-command to 'gluster volume remove-brick <vol> <peer>:<brick> status [failed|skipped]'.
This command will list failed or skipped entries if any. I think this will be useful. Now, the only way to find problematic files is search in logs.
Nithya - can you weigh in this request with your thoughts?
Would writing these entries to a separate file be acceptable? The command if added later could simply parse these files and display the entries.
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.
Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.