Dear all,

a user has hit the inode quota limit:

     Filesystem    used   quota   limit   grace   files   quota   limit   grace
        /lustre  12.76T      0k      0k       -  635978* 636078  636178 
2d16h29m43s

Typical quota mathematics: 635978 > 636178, but it's distributed quota, very 
well.

We have three MDTs, the user most probably has files and directories on only 
one of them.
Let's check "-v":

# lfs quota -h -v -u User /lustre
        /lustre  12.76T      0k      0k       -  635978* 636078  636178 
2d16h29m43s
lustre-MDT0000_UUID
                     0k       -  15.28G       -       0       -       1       -
lustre-MDT0001_UUID
                 134.2M       -  16.04G       -  635978       -  636460       -
lustre-MDT0002_UUID
                     0k       -      0k       -       0       -   17150       -



What is the meaning of column #7 in the output for each MDT?

In the general result, it is the hard limit.

Here it is 1 on MDT0 - everything probably needs at least one inode on the root 
of the fs.
Seem the user's files are on MDT1, where the column reads  636460 - that is not 
what I set as the hard limit.
And on MDT2, the column reads 17150, but no files from the user there.
And the hard limit is also not the difference of these two values ;-)


Best regards,
Thomas



--
--------------------------------------------------------------------
Thomas Roth
Department: IT
Location: SB3 2.291
Phone: +49-6159-71 1453  Fax: +49-6159-71 2986

GSI Helmholtzzentrum für Schwerionenforschung GmbH
Planckstraße 1, 64291 Darmstadt, Germany, www.gsi.de

Commercial Register / Handelsregister: Amtsgericht Darmstadt, HRB 1528
Managing Directors / Geschäftsführung:
Professor Dr. Paolo Giubellino, Dr. Ulrich Breuer, Jörg Blaurock
Chairman of the Supervisory Board / Vorsitzender des GSI-Aufsichtsrats:
State Secretary / Staatssekretär Dr. Volkmar Dietz
_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Reply via email to