LUDOC-469 hsm: correct description of NBR HSM policy

[doc/manual.git] / LazySizeOnMDT.xml

diff --git a/LazySizeOnMDT.xml b/LazySizeOnMDT.xml
index 8862f14..3192aed 100644 (file)
--- a/LazySizeOnMDT.xml
+++ b/LazySizeOnMDT.xml
@@ -24,9 +24,9 @@
     the MDTs. We expect this feature to be initially used by Lustre policy
     engines that scan the backend MDT storage, make decisions based on broad
     size categories, and do not depend on a totally accurate file size.
-    Examples include Lester, Robinhood, Zester, and DDN’s Lustre Integrated
-    Policy Engine (LiPE). Future improvements will allow the LSoM data to be
-    accessed by tools such as <literal>lfs find</literal>.</para>
+    Examples include Lester, Robinhood, Zester, and various vendor offerings.
+    Future improvements will allow the LSoM data to be accessed by tools such
+    as <literal>lfs find</literal>.</para>
   </section>
   <section xml:id="dbdoclet.enablelsom">
     <title><indexterm><primary>lsom</primary>
@@ -45,7 +45,7 @@
     <para>If it is necessary to access up-to-date LSoM data that has gone
     stale, it is possible to flush the xattr cache from the client by
     cancelling the MDC locks via
-    <literal>ldlm set_param ldlm.namespaces.*mdc*.lru_size=clear</literal>.
+    <literal>lctl set_param ldlm.namespaces.*mdc*.lru_size=clear</literal>.
     Otherwise, the file attributes will be dropped from the client cache if
     the file has not been accessed before the LDLM lock timeout.  The timeout
     is stored via