[lustre-discuss] lfs quota reports file usage but no files found via lfs find

Rasool Almasikoupaei rasool.almasikoupaei at uni-tuebingen.de
Tue Jan 27 10:51:11 PST 2026


I forgot to mention some subtle details:
- This is a ZFS-backed Lustre filesystem.
- There is nothing present in the /.lustre/ directory.

We have DoM enabled, and it seems the discrepancy comes from the MDTs:

/lfs quota -v -uh username /mnt/lustre/

Disk quotas for usr username (uid 101559):
      Filesystem            used    quota    limit   grace files   
quota   limit   grace
    /mnt/lustre/          970.1M       0k       0k       - 22       
0       0       -
    lustreFS-MDT0000_UUID 282.7M        -       0k -       6       
-       0       -
    lustreFS-MDT0001_UUID 188.1M        -       0k -       4       
-       0       -
    lustreFS-MDT0002_UUID 499.4M        -       0k       - 10       
-       0       -
    lustreFS-MDT0003_UUID     1k        -       0k -       2       
-       0       -
    lustreFS-OST0000_UUID     0k        -       0k -       -       
-       -       -
    lustreFS-OST0001_UUID     0k        -       0k -       -       
-       -       -
    .../

Before bringing down the filesystem and taking a look at what ZFS quota 
reports, it would be good to know
whether Lustre performs any manipulation or if it more or less directly 
reports what ZFS quota accounting returns.

Thanks,
Rasool

On 27/01/2026 11:20, Rasool Almasikoupaei via lustre-discuss wrote:
>
> Hi all,
>
> We are seeing a discrepancy between what /lfs quota/ reports and what 
> we can locate using /lfs find/ or the standard find command.
> For example:
>
> /lfs quota -uh username /mnt/lustre/
>
> Disk quotas for usr username (uid 101559):
>      Filesystem    used   quota   limit   grace   files quota   
> limit   grace
>    /mnt/lustre/  970.1M      0k      0k       - 22       0       0       -
>
> uid 101559 is using the default block quota setting
> uid 101559 is using the default file quota setting/
>
>
> However, neither /lfs find -user username/ nor the standard /find/ 
> command can locate these 22 files.
> Running /lfsck/ has no effect and produces the same result.
>
> We have observed this behavior on Lustre 2.15.6 and continue to see it 
> on 2.15.7 and 2.15.8.
> The example user’s access was revoked before any file search was 
> performed.
>
> Does anyone have an idea how to locate or clean up these ghosted 
> files, or how to fix the quota reporting discrepancy?
>
>
> Best,
> Rasool
>
>
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20260127/d3958cc5/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5095 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20260127/d3958cc5/attachment.p7s>


More information about the lustre-discuss mailing list