xiangyong ouyang
2008-Dec-01 17:29 UTC
[Lustre-discuss] what are the meanings of collectl output for lustre
hi all,
I''m running collectl to get profiling information about lustre.
I''m
using lustre "2.6.18-53.1.13.el5_lustre.1.6.4.3smp", and
collectl V3.1.1-5 (zlib:1.42,HiRes:1.86)
Basically I want to see the metadata information on both client and MDS.
On client side, I run: "collectl -sL --lustopts M":
# LUSTRE CLIENT DETAIL (/sec): METADATA
#Filsy KBRead Reads SizeKB KBWrite Writes SizeKB Open Close GAttr
SAttr Seek Fsync DrtHit DrtMis
datafs 0 0 0 0 0 0 3 0 0
0 0 0 0 0
datafs 0 0 0 50169 3915 12 0 3 0
0 0 0 3912 12543
datafs 0 0 0 0 0 0 0 0 0
0 0 0 0 0
What are the fileds "DrtHit" and "DrtMis" here?
But On MDS side, when I run
[wci70-oib:~/tools]collectl -sL
Error: -sL only applies to MDS services when used with --lustopts D
type ''collectl -h'' for help
Then I run:
[wci70-oib:~/tools]collectl -sL --lustopts D
Error: --lustopts D only applies to HP-SFS
type ''collectl -h'' for help
I want to see more detailed metadata information at MDS side, such as
locks, cache hit/miss. What are the options to do that on MDS?
Thanks very much!
Mark Seger
2008-Dec-01 18:24 UTC
[Lustre-discuss] what are the meanings of collectl output for lustre
xiangyong ouyang wrote:> hi all, > > I''m running collectl to get profiling information about lustre. I''m > using lustre "2.6.18-53.1.13.el5_lustre.1.6.4.3smp", and > collectl V3.1.1-5 (zlib:1.42,HiRes:1.86) >Just to be clear, collectl is an open source tool that I wrote, one function of which is to report lustre data that I wanted to report.> Basically I want to see the metadata information on both client and MDS. > > On client side, I run: "collectl -sL --lustopts M": > # LUSTRE CLIENT DETAIL (/sec): METADATA > #Filsy KBRead Reads SizeKB KBWrite Writes SizeKB Open Close GAttr > SAttr Seek Fsync DrtHit DrtMis > datafs 0 0 0 0 0 0 3 0 0 > 0 0 0 0 0 > datafs 0 0 0 50169 3915 12 0 3 0 > 0 0 0 3912 12543 > datafs 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 > > What are the fileds "DrtHit" and "DrtMis" here? >That said, I''ll defer to the lustre experts to define DrtHit/DrtMis, but if someone can offer better definitions than I have in http://collectl.sourceforge.net/Data-verbose.html, which shouldn''t be too hard, I''ll be happy to update my documentation.> But On MDS side, when I run > [wci70-oib:~/tools]collectl -sL > Error: -sL only applies to MDS services when used with --lustopts D > type ''collectl -h'' for help > > Then I run: > [wci70-oib:~/tools]collectl -sL --lustopts D > Error: --lustopts D only applies to HP-SFS > type ''collectl -h'' for help >In HP''s packaged version of Lustre, called HP-SFS, we had added additional disk-level statistics that were not part of the standard Lustre kit and that''s what this message is trying to say. Since you''re not running HP-SFS, you don''t get D. As for -sL with the MDS, the meaning of detail data in the lustre context is to report data at the filesystem level. In the case of the MDS, that data was not available and so -sL didn''t make sense. -mark> I want to see more detailed metadata information at MDS side, such as > locks, cache hit/miss. What are the options to do that on MDS? > Thanks very much! > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss >
Cliff White
2009-Jan-12 16:04 UTC
[Lustre-discuss] what are the meanings of collectl output for lustre
xiangyong ouyang wrote:> hi all, > > I''m running collectl to get profiling information about lustre. I''m > using lustre "2.6.18-53.1.13.el5_lustre.1.6.4.3smp", and > collectl V3.1.1-5 (zlib:1.42,HiRes:1.86) > > Basically I want to see the metadata information on both client and MDS. > > On client side, I run: "collectl -sL --lustopts M": > # LUSTRE CLIENT DETAIL (/sec): METADATA > #Filsy KBRead Reads SizeKB KBWrite Writes SizeKB Open Close GAttr > SAttr Seek Fsync DrtHit DrtMis > datafs 0 0 0 0 0 0 3 0 0 > 0 0 0 0 0 > datafs 0 0 0 50169 3915 12 0 3 0 > 0 0 0 3912 12543 > datafs 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 > > What are the fileds "DrtHit" and "DrtMis" here? > > But On MDS side, when I run > [wci70-oib:~/tools]collectl -sL > Error: -sL only applies to MDS services when used with --lustopts D > type ''collectl -h'' for help > > Then I run: > [wci70-oib:~/tools]collectl -sL --lustopts D > Error: --lustopts D only applies to HP-SFS > type ''collectl -h'' for help > > I want to see more detailed metadata information at MDS side, such as > locks, cache hit/miss. What are the options to do that on MDS? > Thanks very much!I would consult the Lustre manual. Some of this information is available under /proc on the MDS, you can also enable lock tracing through the Lustre debug flags. cliffw> _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss