Description of problem: The rebalance logs contains messages like the following: [2015-05-06 23:39:00.532273] I [dht-rebalance.c:1936:gf_defrag_get_entry] 0-patchy-dht: linkfile. Hence skip for file: /level05/level15/level25/level35/level45/level55/level65/level75/554aa5eb%%8LA99X6NJ6 [2015-05-06 23:39:00.532523] I [dht-rebalance.c:1936:gf_defrag_get_entry] 0-patchy-dht: linkfile. Hence skip for file: /level05/level15/level25/level35/level45/level55/level65/level75/554aa5eb%%GBWHI63XCE [2015-05-06 23:39:00.532784] I [dht-rebalance.c:1936:gf_defrag_get_entry] 0-patchy-dht: linkfile. Hence skip for file: /level05/level15/level25/level35/level45/level55/level65/level75/554aa5eb%%1FGZKJ6C69 [2015-05-06 23:39:00.533025] I [dht-rebalance.c:1936:gf_defrag_get_entry] 0-patchy-dht: linkfile. Hence skip for file: /level05/level15/level25/level35/level45/level55/level65/level75/554aa5eb%%QBBFUHYYAB [2015-05-06 23:39:00.533266] I [dht-rebalance.c:1936:gf_defrag_get_entry] 0-patchy-dht: linkfile. Hence skip for file: /level05/level15/level25/level35/level45/level55/level65/level75/554aa5eb%%PRCG2TLTCK [2015-05-06 23:39:00.533506] I [dht-rebalance.c:1936:gf_defrag_get_entry] 0-patchy-dht: linkfile. Hence skip for file: /level05/level15/level25/level35/level45/level55/level65/level75/554aa5eb%%PM6V2AE0RB [2015-05-06 23:39:00.533919] I [dht-rebalance.c:2267:gf_defrag_process_dir] 0-patchy-dht: Migration operation on dir /level05/level15/level25/level35/level45/level55/level65/level75 took 0.01 secs Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: These files are linkfiles only on this particular local subvolume. As the log message does not indicate the subvol on which the linkfile was found, it looks like dht is skipping the file. It would be better to : 1. Move the log level to DEBUG 2. Reword the message : Skipping linkfile: /level05/level15/level25/level35/level45/level55/level65/level75/554aa5eb%%PRCG2TLTCK 3. Include the subvol information if available Additional info:
REVIEW: http://review.gluster.org/10756 (dht/rebalance: Change log_level to DEBUG) posted (#1) for review on master by Susant Palai (spalai)
COMMIT: http://review.gluster.org/10756 committed in master by Shyamsundar Ranganathan (srangana) ------ commit ef37da74d4a8595cf53cf6dfe680fe080b7c8704 Author: Susant Palai <spalai> Date: Tue May 12 12:56:37 2015 +0530 dht/rebalance: Change log_level to DEBUG Change-Id: I646367581d8ee8a9e5966ee302b19273a0c780ff BUG: 1220329 Signed-off-by: Susant Palai <spalai> Reviewed-on: http://review.gluster.org/10756 Reviewed-by: N Balachandran <nbalacha> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Shyamsundar Ranganathan <srangana>
Fix for this bug is already made in a GlusterFS release. The cloned BZ has details of the fix and the release. Hence closing this mainline BZ.
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user