Description of problem: When a brick is created from a thinly provisioned volume, the brick utilization does not show the actual utilization data. Version-Release number of selected component (if applicable): 3.0.0 How reproducible: Always
Rajesh, Could you provide more details on this bug?
We need to provide LV utilization, thin pool data and meta-data utilization for each brick. For thin provisioning just checking the brick utilization is not enough. Even though you have space in your brick the thin pool might get pool. Check lvs command for more details.
Fix: http://review.gluster.org/#/c/9115/ and http://review.gluster.org/#/c/9116/
Failed to verify this as the graph for thin-pool utilization is not shown correctly for existing bricks after gluster-nagios-addons package is updated on the server being monitored. For new bricks, added after the package is updated, the graph is seen correctly. Screenshot attached with the error seen in place of the thin-pool utilization graph.
Created attachment 960492 [details] screenshot
Please add doc text for this bug.
Done
Fix: http://review.gluster.org/#/c/9188/ and http://review.gluster.org/#/c/9202/
As a part of fix to the update problem, we run a script to migrate the data from old rrd file to new rrd file and we set RRD_STORAGE_TYPE to MULTIPLE so that different data sets are stored in different rrd files. After updating nagios-server-addons package, the graphs for brick utilization will take some time(till first set of data gets populated to new rrd file) to appear. Both gluster-nagios-addons and nagios-server-addons packages have to be updated for this fix to work correctly.
Verified as fixed in gluster-nagios-addons-0.1.14-1.el6rhs.x86_64 Tested by upgrading from 3.0.2 to 3.0.3 Graphs appear correctly. Alerts and notifications also work as expected for thin pool and brick utilization.
Hi Darshan, Can you please review the edited doc text for technical accuracy and sign off?
Looks good.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0039.html