[Lustre-discuss] what are the meanings of collectl output for lustre
Cliff White
Cliff.White at Sun.COM
Mon Jan 12 08:04:22 PST 2009
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
More information about the lustre-discuss
mailing list