LUDOC-297 protocol: Update protocol document

[doc/protocol.git] / glossary.txt

diff --git a/glossary.txt b/glossary.txt
index 92194fb..8bde019 100644 (file)
--- a/glossary.txt
+++ b/glossary.txt
@@ -5,10 +5,9 @@ Here are some common terms used in discussing Lustre, POSIX semantics,
 and the protocols used to implement them.
 
 [glossary]
-back end file system::
-Storage on a server in support of the object store or of metadata is
-stored on the back end file system. The two available file systems are
-currently ldiskfs and ZFS.
+Object Storage Device (OSD)::
+The OSD is the storage on a server that holds objects or metadata. The
+two kinds of file system available ofr OSDs are ldiskfs and ZFS.
 
 Client::
 A Lustre client is a computer taking advantage of the services
@@ -27,23 +26,24 @@ that allows the target to indicate to the requestor to increase its
 timeout value without otherwise indicating the request has progressed.
 
 export::
-The term for the per-client shared state information held by a server.
+The term for the per-client shared state information held by a
+server. See <<struct-obd-export>>.
 
 extent:: A range of offsets in a file.
 
 import::
-The term for the per-target shared state information held by a client.
+The term for the per-target shared state information held by a
+client. See <<struct_obd_import>>.
 
 Inodes and Extended Attributes::
 Metadata about a Lustre file is encoded in the extended attributes of
-an inode in the back-end file system on the MDT. Some of that
-information establishes the stripe layout of the file. The size of the
-stripe layout information may be different for each file. The amount
-of space reserved for layout information is a small as possible given
-the maximum stripe count on the file system. Clients, servers,
-and the distributed lock manager will all need to be aware of this
-size, which is communicated in the 'ocd_max_easize' filed of the
-<<obd_connect_data>> structure.
+an inode on the MDT. Some of that information establishes the stripe
+layout of the file. The size of the stripe layout information may be
+different for each file. The amount of space reserved for layout
+information is a small as possible given the maximum stripe count on
+the file system. Clients, servers, and the distributed lock manager
+will all need to be aware of this size, which is communicated in the
+'ocd_max_easize' fieled of the <<struct-obd-connect-data>> structure.
 
 LNet::
 A lower level protocol employed by PtlRPC to abstract the mechanisms