Hari Gowtham
2019-Jul-19 10:48 UTC
[Gluster-users] "du" and "df -hT" commands output mismatch
Hi Mauro, The fsck script is the fastest way to resolve the issue. The other way would be to disable quota and once the crawl for disable is done, we have to enable and set the limits again. In this way, the crawl happens twice and hence its slow. On Fri, Jul 19, 2019 at 3:27 PM Mauro Tridici <mauro.tridici at cmcc.it> wrote:> > Dear All, > > I?m experiencing again a problem with gluster file system quota. > The ?df -hT /tier2/CSP/sp1? command output is different from the ?du -ms? command executed against the same folder. > > [root at s01 manual]# df -hT /tier2/CSP/sp1 > Filesystem Type Size Used Avail Use% Mounted on > s01-stg:tier2 fuse.glusterfs 25T 22T 3.5T 87% /tier2 > > [root at s01 sp1]# du -ms /tier2/CSP/sp1 > 14TB /tier2/CSP/sp1 > > In the past, I used successfully the quota_fsck_new-6.py script in order to detect the SIZE_MISMATCH occurrences and fix them. > Unfortunately, the number of sub-directories and files saved in /tier2/CSP/sp1 grew so much and the list of SIZE_MISMATCH entries is very long. > > Is there a faster way to correct the mismatching outputs? > Could you please help me to solve, if it is possible, this issue? > > Thank you in advance, > Mauro > > > > > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users-- Regards, Hari Gowtham.
Mauro Tridici
2019-Jul-19 12:12 UTC
[Gluster-users] "du" and "df -hT" commands output mismatch
Hi Hari, thank you very much for the fast answer. I think that the we will try to solve the issue disabling and enabling quota. So, if I understand I have to do the following actions: - save on my notes the current quota limits; - disable quota using "gluster volume quota /tier2 disable? command; - wait a while for the crawl (question: how can I understand that crawl is terminated!? how logn should I wait?); - enable quota using "gluster volume quota /tier2 enable?; - set again the previous quota limits. Is this correct? Many thanks for your support, Mauro> On 19 Jul 2019, at 12:48, Hari Gowtham <hgowtham at redhat.com> wrote: > > Hi Mauro, > > The fsck script is the fastest way to resolve the issue. > The other way would be to disable quota and once the crawl for disable > is done, we have to enable and set the limits again. > In this way, the crawl happens twice and hence its slow. > > On Fri, Jul 19, 2019 at 3:27 PM Mauro Tridici <mauro.tridici at cmcc.it> wrote: >> >> Dear All, >> >> I?m experiencing again a problem with gluster file system quota. >> The ?df -hT /tier2/CSP/sp1? command output is different from the ?du -ms? command executed against the same folder. >> >> [root at s01 manual]# df -hT /tier2/CSP/sp1 >> Filesystem Type Size Used Avail Use% Mounted on >> s01-stg:tier2 fuse.glusterfs 25T 22T 3.5T 87% /tier2 >> >> [root at s01 sp1]# du -ms /tier2/CSP/sp1 >> 14TB /tier2/CSP/sp1 >> >> In the past, I used successfully the quota_fsck_new-6.py script in order to detect the SIZE_MISMATCH occurrences and fix them. >> Unfortunately, the number of sub-directories and files saved in /tier2/CSP/sp1 grew so much and the list of SIZE_MISMATCH entries is very long. >> >> Is there a faster way to correct the mismatching outputs? >> Could you please help me to solve, if it is possible, this issue? >> >> Thank you in advance, >> Mauro >> >> >> >> >> >> >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-users > > > > -- > Regards, > Hari Gowtham.-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190719/5ab560e3/attachment.html>