Red Hat Bugzilla – Bug 1466188
Add scripts to analyze quota xattr in backend and identify accounting issues
Last modified: 2017-09-05 13:35:13 EDT
This bug is for introducing scripts in order to identify Accounting issues in marker as discussed originally in http://nongnu.13855.n7.nabble.com/Scripts-to-help-RCA-quota-accounting-issues-td222941.html,
1. Script that does a du -h on the directory tree and a quota list on the hierarchy and interleaves the two. We can then identify which directory(s) in FS has caused the accounting to go bad and try to investigate what fops happened on those directories. Also, currently for accounting issues we set dirty xattr on the FS tree as a whole. But, if we knew the origin of the accounting mismatch then we can set dirty xattr on a few directories on the brick and let the correction propagate by itself.
2. Another issue is that since the xattr are in hexadecimal it becomes tedious to analyze. we need a script that can recursively collect xattr values and dump it human readable form for quick analysis
REVIEW: https://review.gluster.org/17649 (Scripts to identify quota accouting issues) posted (#1) for review on master by sanoj-unnikrishnan (firstname.lastname@example.org)
COMMIT: https://review.gluster.org/17649 committed in master by Raghavendra G (email@example.com)
Author: Sanoj Unnikrishnan <firstname.lastname@example.org>
Date: Thu Jun 29 15:39:35 2017 +0530
Scripts to identify quota accouting issues
The patch contains 2 scripts:
log_accounting.sh does a du -h on the FS hierarchy and a quota list
on the hierarchy and interleaves the two output. We can then identify
which directory(s) in FS has caused the accounting to go bad and try
to investigate what fops happened on those directories. We can also
limit the set of directories on which we need to set dirty xattr to
xattr_analysis.py reads all the xattr of a brick and dumps it a human
readable form to ease debugging.
Signed-off-by: Sanoj Unnikrishnan <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Smoke: Gluster Build System <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.12.0, please open a new bug report.
glusterfs-3.12.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.