+++ This bug was initially created as a clone of Bug #1463114 +++
Description of problem:
As of now rebalance status just indicate the count of failed and skipped entries. This information should be more informative and should even give the list of files so that list can be used to manually operate and complete rebalancing.
Good to have list of files in a separate log file. Preferable would be to have file path and not gfid.
We should log in such a way that it can be consumed easily even if the list is long.
With this fix we should even create a way/script to consume the list and make the life of Admin easier. As of now doing it manually is a tough job.
So here we have 3 requirements :
1) Get the list of files failed or skipped with error messages
2) Automatically consume those file list to complete rebalance( This can be triggered manually)
3) If not able to consume list, list the file with some reason of failure
Skipped files are now logged in the rebalance log :
2017-08-11 05:33:01.464620] I [MSGID: 109126] [dht-rebalance.c:2681:gf_defrag_migrate_single_file] 0-vol1-dht: File migration skipped for /NEWFILE-1.
Users can search for the msgid  for the list of skipped files.
REVIEW: https://review.gluster.org/18021 (cluster/dht: Log files skipped by rebalance) posted (#1) for review on master by N Balachandran (email@example.com)
COMMIT: https://review.gluster.org/18021 committed in master by Raghavendra G (firstname.lastname@example.org)
Author: N Balachandran <email@example.com>
Date: Fri Aug 11 12:16:12 2017 +0530
cluster/dht: Log files skipped by rebalance
There was no easy way to find out which files were
skipped during a rebalance.
Rebalance now logs a message for every skipped file
using msgid 109126, making it easier to find
all files that were skipped.
Signed-off-by: N Balachandran <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: hari gowtham <email@example.com>
Reviewed-by: Raghavendra G <firstname.lastname@example.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.13.0, please open a new bug report.
glusterfs-3.13.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.