From: Richard Henwood Date: Tue, 17 May 2011 21:49:00 +0000 (-0500) Subject: FIX: xrefs X-Git-Tag: workingxslt~26 X-Git-Url: https://git.whamcloud.com/?a=commitdiff_plain;h=dbda450e1bbe51cb176cf6d069dd7943508f73de;p=doc%2Fmanual.git FIX: xrefs --- diff --git a/LustreMonitoring.xml b/LustreMonitoring.xml index c0705ac..1d9b0a7 100644 --- a/LustreMonitoring.xml +++ b/LustreMonitoring.xml @@ -1,63 +1,39 @@ - + - Lustre Monitoring + Lustre Monitoring This chapter provides information on monitoring Lustre and includes the following sections: + - Lustre Changelogs - - - - - - Lustre Monitoring Tool - - - - - - CollectL - - - - - - Other Monitoring Options - - - - - -
- <anchor xml:id="dbdoclet.50438273_pgfId-1296751" xreflabel=""/> -
- 12.1 <anchor xml:id="dbdoclet.50438273_18711" xreflabel=""/>Lustre <anchor xml:id="dbdoclet.50438273_marker-1297383" xreflabel=""/>Changelogs + Lustre Changelogs + + + Lustre Monitoring Tool + + + CollectL + + + Other Monitoring Options + + + +
+ 12.1 Lustre <anchor xml:id="dbdoclet.50438273_marker-1297383" xreflabel=""/>Changelogs The changelogs feature records events that change the file system namespace or file metadata. Changes such as file creation, deletion, renaming, attribute changes, etc. are recorded with the target and parent file identifiers (FIDs), the name of the target, and a timestamp. These records can be used for a variety of purposes: Capture recent changes to feed into an archiving system. - - - Use changelog entries to exactly replicate changes in a file system mirror. - - - Set up "watch scripts" that take action on certain events or directories. - - - Maintain a rough audit trail (file/directory changes with timestamps, but no user information). - - - Changelogs record types are: @@ -289,26 +265,25 @@ p=parent_FID target_name
-
- 12.2 <anchor xml:id="dbdoclet.50438273_81684" xreflabel=""/>Lustre <anchor xml:id="dbdoclet.50438273_marker-1297386" xreflabel=""/>Monitoring Tool +
+ 12.2 Lustre <anchor xml:id="dbdoclet.50438273_marker-1297386" xreflabel=""/>Monitoring Tool The Lustre Monitoring Tool (LMT) is a Python-based, distributed system developed and maintained by Lawrence Livermore National Lab (LLNL)). It provides a ''top'' like display of activity on server-side nodes (MDS, OSS and portals routers) on one or more Lustre file systems. It does not provide support for monitoring clients. For more information on LMT, including the setup procedure, see: http://code.google.com/p/lmt/ LMT questions can be directed to: lmt-discuss@googlegroups.com
-
- 12.3 <anchor xml:id="dbdoclet.50438273_80593" xreflabel=""/>Collect<anchor xml:id="dbdoclet.50438273_marker-1297391" xreflabel=""/>L +
+ 12.3 Collect<anchor xml:id="dbdoclet.50438273_marker-1297391" xreflabel=""/>L CollectL is another tool that can be used to monitor Lustre. You can run CollectL on a Lustre system that has any combination of MDSs, OSTs and clients. The collected data can be written to a file for continuous logging and played back at a later time. It can also be converted to a format suitable for plotting. For more information about CollectL, see: http://collectl.sourceforge.net Lustre-specific documentation is also available. See: http://collectl.sourceforge.net/Tutorial-Lustre.html
-
- 12.4 <anchor xml:id="dbdoclet.50438273_44185" xreflabel=""/>Other Monitoring Options +
+ 12.4 Other Monitoring Options A variety of standard tools are available publically. Another option is to script a simple monitoring solution that looks at various reports from ipconfig, as well as the procfs files generated by Lustre.  
-