Red Hat Bugzilla – Bug 1275383
Data Tiering:Getting lookup failed on files in hot tier, when volume is restarted
Last modified: 2016-06-16 09:41:27 EDT
REVIEW: http://review.gluster.org/12430 (cluster/tier do not log error message on lookup heal for files on hot tier) posted (#1) for review on master by Dan Lambright (email@example.com)
A file may exist on the hot tier because it was created before fix-layout reached it, or because it was created before the volume was stopped earlier. In either case this is not an error and should not be flagged as such, change the log to INFO.
REVIEW: http://review.gluster.org/12430 (cluster/tier do not log error message on lookup heal for files on hot tier) posted (#2) for review on master by Dan Lambright (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/12430 committed in master by Dan Lambright (email@example.com)
Author: Dan Lambright <firstname.lastname@example.org>
Date: Mon Oct 26 14:19:24 2015 -0400
cluster/tier do not log error message on lookup heal for files on hot tier
On fix-layout heal files are scanned. Files found are exist on the hot or cold
subvolume. Those not found in the cold tier would exist on the hot. They
should not be flagged as an error.
Replace INFO with TRACE for common tier migration logs. Frequent migration
was growing the log files too quickly.
On migratation failures, do not acrue files towards cycle limit's budget.
Signed-off-by: Dan Lambright <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Joseph Fernandes
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 , 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.