<div dir="ltr"><div><div><div><tt>Hi Mathew,<br><br>If you are sure that "/mnt/raid6-storage/storage/<wbr>data/projects/MEOPAR/"<br></tt></div><tt>is the only directory with wrong accounting and its immediate sub directories have correct xattr values, Setting the dirty xattr and doing a stat after that should resolve the issue.<br></tt><pre>1) setxattr -n trusted.glusterfs.quota.dirty -v 0x3100 <tt>/mnt/raid6-storage/storage/<wbr>data/projects/MEOPAR/</tt></pre><tt>2) stat </tt><tt><tt>/mnt/raid6-storage/storage/<wbr>data/projects/MEOPAR/<br><br></tt> </tt></div><div><tt></tt></div><tt>Could you please share what kind of operations that happens on this directory, to help RCA the issue.<br></tt></div><div><tt><br>If you think this can be true elsewhere in filesystem as well,</tt><tt>use the following script to identify the same.<br><br>1) <a href="https://github.com/gluster/glusterfs/blob/master/extras/quota/xattr_analysis.py">https://github.com/gluster/glusterfs/blob/master/extras/quota/xattr_analysis.py</a><br>2) <a href="https://github.com/gluster/glusterfs/blob/master/extras/quota/log_accounting.sh">https://github.com/gluster/glusterfs/blob/master/extras/quota/log_accounting.sh</a><br></tt></div><div><tt><br></tt></div><div><tt>Regards,<br></tt></div><div><tt>Sanoj<br></tt></div><div><tt><br></tt><div><tt><br> <br></tt></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 28, 2017 at 12:39 PM, Raghavendra Gowdappa <span dir="ltr"><<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+sanoj<br>
<div><div class="h5"><br>
----- Original Message -----<br>
> From: "Matthew B" <<a href="mailto:matthew.has.questions@gmail.com">matthew.has.questions@gmail.<wbr>com</a>><br>
> To: <a href="mailto:gluster-devel@gluster.org">gluster-devel@gluster.org</a><br>
> Sent: Saturday, August 26, 2017 12:45:19 AM<br>
> Subject: [Gluster-devel] Quota Used Value Incorrect - Fix now or after upgrade<br>
><br>
> Hello,<br>
><br>
> I need some advice on fixing an issue with quota on my gluster volume. It's<br>
> running version 3.7, distributed volume, with 7 nodes.<br>
><br>
> # gluster --version<br>
> glusterfs 3.7.13 built on Jul 8 2016 15:26:18<br>
> Repository revision: git:// <a href="http://git.gluster.com/glusterfs.git" rel="noreferrer" target="_blank">git.gluster.com/glusterfs.git</a><br>
> Copyright (c) 2006-2011 Gluster Inc. < <a href="http://www.gluster.com" rel="noreferrer" target="_blank">http://www.gluster.com</a> ><br>
> GlusterFS comes with ABSOLUTELY NO WARRANTY.<br>
> You may redistribute copies of GlusterFS under the terms of the GNU General<br>
> Public License.<br>
><br>
> # gluster volume info storage<br>
><br>
> Volume Name: storage<br>
> Type: Distribute<br>
> Volume ID: 6f95525a-94d7-4174-bac4-<wbr>e1a18fe010a2<br>
> Status: Started<br>
> Number of Bricks: 7<br>
> Transport-type: tcp<br>
> Bricks:<br>
> Brick1: 10.0.231.50:/mnt/raid6-<wbr>storage/storage<br>
> Brick2: 10.0.231.51:/mnt/raid6-<wbr>storage/storage<br>
> Brick3: 10.0.231.52:/mnt/raid6-<wbr>storage/storage<br>
> Brick4: 10.0.231.53:/mnt/raid6-<wbr>storage/storage<br>
> Brick5: 10.0.231.54:/mnt/raid6-<wbr>storage/storage<br>
> Brick6: 10.0.231.55:/mnt/raid6-<wbr>storage/storage<br>
> Brick7: 10.0.231.56:/mnt/raid6-<wbr>storage/storage<br>
> Options Reconfigured:<br>
> changelog.changelog: on<br>
> geo-replication.ignore-pid-<wbr>check: on<br>
> geo-replication.indexing: on<br>
> nfs.disable: no<br>
> performance.readdir-ahead: on<br>
> features.quota: on<br>
> features.inode-quota: on<br>
> features.quota-deem-statfs: on<br>
> features.read-only: off<br>
><br>
> # df -h /storage/<br>
> Filesystem Size Used Avail Use% Mounted on<br>
> 10.0.231.50:/storage 255T 172T 83T 68% /storage<br>
><br>
><br>
> I am planning to upgrade to 3.10 (or 3.12 when it's available) but I have a<br>
> number of quotas configured, and one of them (below) has a very wrong "Used"<br>
> value:<br>
><br>
> # gluster volume quota storage list | egrep "MEOPAR "<br>
> /data/projects/MEOPAR 8.5TB 80%(6.8TB) 16384.0PB 17.4TB No No<br>
><br>
><br>
> I have confirmed the bad value appears in one of the bricks current xattrs,<br>
> and it looks like the issue has been encountered previously on bricks 04,<br>
> 03, and 06: (gluster07 does not have a trusted.glusterfs.quota.size.1 as it<br>
> was recently added)<br>
><br>
> $ ansible -i hosts gluster-servers[0:6] -u <user> --ask-pass -m shell -b<br>
> --become-method=sudo --ask-become-pass -a "getfattr --absolute-names -m . -d<br>
> -e hex /mnt/raid6-storage/storage/<wbr>data/projects/MEOPAR | egrep<br>
> '^trusted.glusterfs.quota.<wbr>size'"<br>
> SSH password:<br>
> SUDO password[defaults to SSH password]:<br>
><br>
> gluster02 | SUCCESS | rc=0 >><br>
> trusted.glusterfs.quota.size=<wbr>0x0000011ecfa56c00000000000005<wbr>cd6d000000000006d478<br>
> trusted.glusterfs.quota.size.<wbr>1=<wbr>0x0000010ad4a45200000000000001<wbr>2a0300000000000150fa<br>
><br>
> gluster05 | SUCCESS | rc=0 >><br>
> trusted.glusterfs.quota.size=<wbr>0x00000033b8e92200000000000004<wbr>cde8000000000006b1a4<br>
> trusted.glusterfs.quota.size.<wbr>1=<wbr>0x0000010dca277c00000000000001<wbr>297d0000000000015005<br>
><br>
> gluster01 | SUCCESS | rc=0 >><br>
> trusted.glusterfs.quota.size=<wbr>0x0000003d4d434800000000000005<wbr>7616000000000006afd2<br>
> trusted.glusterfs.quota.size.<wbr>1=<wbr>0x00000133fe211e00000000000005<wbr>d161000000000006cfd4<br>
><br>
> gluster04 | SUCCESS | rc=0 >><br>
> trusted.glusterfs.quota.size=<wbr>0xffffff396f3e9400000000000004<wbr>d7ea0000000000068c62<br>
> trusted.glusterfs.quota.size.<wbr>1=<wbr>0x00000106e6724800000000000001<wbr>138f0000000000012fb2<br>
><br>
> gluster03 | SUCCESS | rc=0 >><br>
> trusted.glusterfs.quota.size=<wbr>0xfffffd02acabf000000000000003<wbr>599000000000000643e2<br>
> trusted.glusterfs.quota.size.<wbr>1=<wbr>0x00000114e20f5e00000000000001<wbr>13b30000000000012fb2<br>
><br>
> gluster06 | SUCCESS | rc=0 >><br>
> trusted.glusterfs.quota.size=<wbr>0xffffff0c98de4400000000000005<wbr>36e40000000000068cf2<br>
> trusted.glusterfs.quota.size.<wbr>1=<wbr>0x0000013532664e00000000000005<wbr>e73f000000000006cfd4<br>
><br>
> gluster07 | SUCCESS | rc=0 >><br>
> trusted.glusterfs.quota.size=<wbr>0xfffffa3d7c1ba60000000000000a<wbr>9ccb000000000005fd2f<br>
><br>
> And reviewing the subdirectories of that folder on the impacted server you<br>
> can see that none of the direct children have such incorrect values:<br>
><br>
> [root@gluster07 ~]# getfattr --absolute-names -m . -d -e hex<br>
> /mnt/raid6-storage/storage/<wbr>data/projects/MEOPAR/*<br>
> # file: /mnt/raid6-storage/storage/<wbr>data/projects/MEOPAR/<dir1 ><br>
> ...<br>
> trusted.glusterfs.quota.<wbr>7209b677-f4b9-4d82-a382-<wbr>0733620e6929.contri=<wbr>0x000000fb68418200000000000000<wbr>74730000000000000dae<br>
> trusted.glusterfs.quota.dirty=<wbr>0x3000<br>
> trusted.glusterfs.quota.size=<wbr>0x000000fb68418200000000000000<wbr>74730000000000000dae<br>
><br>
> # file: /mnt/raid6-storage/storage/<wbr>data/projects/MEOPAR/<dir2 ><br>
> ...<br>
> trusted.glusterfs.quota.<wbr>7209b677-f4b9-4d82-a382-<wbr>0733620e6929.contri=<wbr>0x0000000416d5f400000000000000<wbr>0baa0000000000000441<br>
> trusted.glusterfs.quota.dirty=<wbr>0x3000<br>
> trusted.glusterfs.quota.limit-<wbr>set=<wbr>0x0000010000000000ffffffffffff<wbr>ffff<br>
> trusted.glusterfs.quota.size=<wbr>0x0000000416d5f400000000000000<wbr>0baa0000000000000441<br>
><br>
> # file: /mnt/raid6-storage/storage/<wbr>data/projects/MEOPAR/<dir3><br>
> ...<br>
> trusted.glusterfs.quota.<wbr>7209b677-f4b9-4d82-a382-<wbr>0733620e6929.contri=<wbr>0x000000110f2c4e00000000000002<wbr>a76a000000000006ad7d<br>
> trusted.glusterfs.quota.dirty=<wbr>0x3000<br>
> trusted.glusterfs.quota.limit-<wbr>set=<wbr>0x0000020000000000ffffffffffff<wbr>ffff<br>
> trusted.glusterfs.quota.size=<wbr>0x000000110f2c4e00000000000002<wbr>a76a000000000006ad7d<br>
><br>
><br>
> Can I fix this on the current version of gluster (3.7) on just the one brick<br>
> before I upgrade? Or would I be better off upgrading to 3.10 and trying to<br>
> fix it then?<br>
><br>
> I have reviewed information here:<br>
><br>
> <a href="http://lists.gluster.org/pipermail/gluster-devel/2016-February/048282.html" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>pipermail/gluster-devel/2016-<wbr>February/048282.html</a><br>
> <a href="http://lists.gluster.org/pipermail/gluster-users.old/2016-September/028365.html" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>pipermail/gluster-users.old/<wbr>2016-September/028365.html</a><br>
><br>
> It seems like since I am on Gluster 3.7 I can disable quotas and re-enable<br>
> and everything will get recalculated and increment the index on the<br>
> quota.size xattr. But with the size of the volume that will take a very long<br>
> time.<br>
><br>
> Could I simply mark the impacted directly as dirty on gluster07? Or update<br>
> the xattr directly as the sum of the size of dir1, 2, and 3?<br>
><br>
> Thanks,<br>
> -Matthew<br>
><br>
</div></div>> ______________________________<wbr>_________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
</blockquote></div><br></div>