<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I had the same problem. You can collect this information on a per-OST basis, and do the summation yourself. If you're collecting other metrics already, it's easy to do. We use telegraf and grafana to harvest metrics.</div><div class="gmail_default" style="font-size:small">On each OSS, under /proc/fs/lustre/osd-*/*-OST*/quota_slave you'll find several files that contain the usage information (acct_group, acct_user, acct_project), and the limit information (limit_group, limit_user, limit_project). The files are organized by UID.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">For example:</div><div class="gmail_default" style="font-size:small">[root@oss0 quota_slave]# cat acct_user <br>usr_accounting:<br>- id: 298441<br> usage: { inodes: 44, kbytes: 4333438 }<br>- id: 0<br> usage: { inodes: 967, kbytes: 2593032 }<br>- id: 304420<br> usage: { inodes: 8517, kbytes: 4444538 }<br>- id: 1802<br> usage: { inodes: 53, kbytes: 45487123504 }<br>- id: 354496<br> usage: { inodes: 1096, kbytes: 1711806 }<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Kevin</div><div class="gmail_default" style="font-size:small">--</div><div class="gmail_default" style="font-size:small">Kevin Hildebrand</div><div class="gmail_default" style="font-size:small">University of Maryland<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Date: Thu, 11 Feb 2021 19:26:54 +0000<br>
From: "Vicker, Darby J. (JSC-EG111)[Jacobs Technology, Inc.]"<br>
<<a href="mailto:darby.vicker-1@nasa.gov" target="_blank">darby.vicker-1@nasa.gov</a>><br>
To: "<a href="mailto:barnet@icecube.wisc.edu" target="_blank">barnet@icecube.wisc.edu</a>" <<a href="mailto:barnet@icecube.wisc.edu" target="_blank">barnet@icecube.wisc.edu</a>>,<br>
"<a href="mailto:lustre-discuss@lists.lustre.org" target="_blank">lustre-discuss@lists.lustre.org</a>" <<a href="mailto:lustre-discuss@lists.lustre.org" target="_blank">lustre-discuss@lists.lustre.org</a>><br>
Subject: Re: [lustre-discuss] [EXTERNAL] Elegant way to dump<br>
quota/usage database?<br>
Message-ID: <<a href="mailto:391D5E58-4698-4213-96E4-F9BFA0EF37A1@nasa.gov" target="_blank">391D5E58-4698-4213-96E4-F9BFA0EF37A1@nasa.gov</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
FWIW, I've had the same need and I do exactly the brute force iteration you speak of for our LFS's to log user usage vs time. For our NFS server, we use ZFS and there is a nice one-liner to give that info in ZFS. I agree, it would be nice if there was a similar one-liner for lustre. <br>
<br>
?-----Original Message-----<br>
From: lustre-discuss <<a href="mailto:lustre-discuss-bounces@lists.lustre.org" target="_blank">lustre-discuss-bounces@lists.lustre.org</a>> on behalf of Steve Barnet <<a href="mailto:barnet@icecube.wisc.edu" target="_blank">barnet@icecube.wisc.edu</a>><br>
Reply-To: "<a href="mailto:barnet@icecube.wisc.edu" target="_blank">barnet@icecube.wisc.edu</a>" <<a href="mailto:barnet@icecube.wisc.edu" target="_blank">barnet@icecube.wisc.edu</a>><br>
Date: Thursday, February 11, 2021 at 12:07 PM<br>
To: "<a href="mailto:lustre-discuss@lists.lustre.org" target="_blank">lustre-discuss@lists.lustre.org</a>" <<a href="mailto:lustre-discuss@lists.lustre.org" target="_blank">lustre-discuss@lists.lustre.org</a>><br>
Subject: [EXTERNAL] [lustre-discuss] Elegant way to dump quota/usage database?<br>
<br>
Hey all,<br>
<br>
I would like to be able to dump the usage tracking and quota <br>
information for my lustre filesystems. I am currently running lustre 2.12<br>
<br>
lfs quota -u $user $filesystem<br>
<br>
works well enough for a single user. But I have been looking for a way <br>
to get that information for all users of the filesystem. So far, I have <br>
not stumbled across anything more elegant than a brute force iteration <br>
over my known users.<br>
<br>
While that works (mostly), it is clearly not great. Is there a better <br>
way to do this? Hoping I just missed something in the docs ...<br>
<br>
Thanks in advance for any pointers in this area.<br>
<br>
Best,<br>
<br>
---Steve<br>
<br>
<br>
</blockquote></div></div>