From 94a7200a3ff84a5444b0ead0c54f3c0a5fe83013 Mon Sep 17 00:00:00 2001 From: Joseph Gmitter Date: Fri, 4 Nov 2016 10:18:18 -0400 Subject: [PATCH] LUDOC-11 misc: Trivial updates to correct spelling errors Trivial updates that correct spelling errors found while reviewing a rendered version of the manual (some errors are created by running an xml tag into the next word without a space). Signed-off-by: Joseph Gmitter Change-Id: Id7709e4fcc776b659213c1298693972e7a0dc8de Reviewed-on: http://review.whamcloud.com/23580 Tested-by: Jenkins Reviewed-by: Andreas Dilger --- BackupAndRestore.xml | 2 +- BenchmarkingTests.xml | 2 +- ConfiguringFailover.xml | 2 +- ConfiguringLNET.xml | 4 ++-- ConfiguringLustre.xml | 2 +- ConfiguringQuotas.xml | 12 ++++++------ InstallingLustre.xml | 10 +++++----- LustreHSM.xml | 2 +- LustreMonitoring.xml | 4 ++-- LustreNodemap.xml | 2 +- LustreOperations.xml | 2 +- LustreProc.xml | 2 +- LustreProgrammingInterfaces.xml | 2 +- ManagingSecurity.xml | 2 +- ManagingStripingFreeSpace.xml | 4 ++-- SettingUpLustreSystem.xml | 6 +++--- SystemConfigurationUtilities.xml | 4 ++-- TroubleShootingRecovery.xml | 2 +- UnderstandingFailover.xml | 4 ++-- UnderstandingLustre.xml | 12 ++++++------ UnderstandingLustreNetworking.xml | 2 +- UpgradingLustre.xml | 8 ++++---- 22 files changed, 46 insertions(+), 46 deletions(-) diff --git a/BackupAndRestore.xml b/BackupAndRestore.xml index fe280c9..7ea2c8a 100644 --- a/BackupAndRestore.xml +++ b/BackupAndRestore.xml @@ -172,7 +172,7 @@ xml:id="backupandrestore"> Verify that the Lustre file system (source) and the replica file system (target) are identical - beforeregistering the changelog user. If the + before registering the changelog user. If the file systems are discrepant, use a utility, e.g. regular rsync(not lustre_rsync), to make them identical. diff --git a/BenchmarkingTests.xml b/BenchmarkingTests.xml index 635b7f4..953659b 100644 --- a/BenchmarkingTests.xml +++ b/BenchmarkingTests.xml @@ -52,7 +52,7 @@ ost-survey - Performs I/O against OSTs individually to allow - performance comparisons to detect if an OST is performing suboptimally due to hardware + performance comparisons to detect if an OST is performing sub-optimally due to hardware issues. diff --git a/ConfiguringFailover.xml b/ConfiguringFailover.xml index 1d57b20..222b621 100644 --- a/ConfiguringFailover.xml +++ b/ConfiguringFailover.xml @@ -123,7 +123,7 @@ information - When the target is formatted using the mkfs.lustrecommand, the failover + When the target is formatted using the mkfs.lustre command, the failover service node(s) for the target are designated using the --servicenode option. In the example below, an OST with index 0 in the file system testfs is formatted with two service nodes designated to serve as a diff --git a/ConfiguringLNET.xml b/ConfiguringLNET.xml index 27e434e..653f44e 100755 --- a/ConfiguringLNET.xml +++ b/ConfiguringLNET.xml @@ -373,7 +373,7 @@ lnetctl export > FILE.yaml at the first error. Below is the YAML syntax describing the various configuration elements which can be operated on via DLC. Not all - YAML elements are requied for all operations (add/delete/show). + YAML elements are required for all operations (add/delete/show). The system ignores elements which are not pertinent to the requested operation.
@@ -675,7 +675,7 @@ tcp0 192.168.0.*; o2ib0 132.6.[1-3].[2-8/2]"' The LNET module routes parameter is used to identify routers in a Lustre configuration. These parameters are set in modprobe.conf on each Lustre node. - Routes are typicall set to connect to segregated subnetworks + Routes are typically set to connect to segregated subnetworks or to cross connect two different types of networks such as tcp and o2ib The LNET routes parameter specifies a colon-separated list of diff --git a/ConfiguringLustre.xml b/ConfiguringLustre.xml index 3326556..7ff40d1 100644 --- a/ConfiguringLustre.xml +++ b/ConfiguringLustre.xml @@ -67,7 +67,7 @@ xml:id="configuringlustre"> - Setlnet + Set lnet module parameters to specify how Lustre Networking (LNET) is to be configured to work with a Lustre file system and test the LNET configuration.LNET will, by default, use the first TCP/IP diff --git a/ConfiguringQuotas.xml b/ConfiguringQuotas.xml index d63cb30..c68d719 100644 --- a/ConfiguringQuotas.xml +++ b/ConfiguringQuotas.xml @@ -365,7 +365,7 @@ group uptodate: glb[1],slv[1],reint[0] one can exceed the soft limit within the grace period if under the hard limit. Due to the distributed nature of a Lustre file system and the need to - mainain performance under load, those quota parameters may not be 100% + maintain performance under load, those quota parameters may not be 100% accurate. The quota settings can be manipulated via the lfs command, executed on a client, and includes several options to work with quotas: @@ -453,7 +453,7 @@ uses an IAM files while the ZFS OSD creates dedicated ZAPs. modified. This glimpse callback includes information about the identifier subject to the change. If the global index on the QMT is modified while a slave is disconnected, the index version is used to determine whether the - slave copy of the global index isn't uptodate any more. If so, the slave + slave copy of the global index isn't up to date any more. If so, the slave fetches the whole index again and updates the local copy. The slave copy of the global index is also exported via /proc and can be accessed via the following command: @@ -478,7 +478,7 @@ lctl get_param osd-*.*.quota_slave.limit* may experience unnecessary failures. The file system block quota is divided up among the OSTs within the file system. Each OST requests an allocation which is increased up to the quota limit. The quota allocation is then - quantizedto reduce the number of + quantized to reduce the number of quota-related request traffic. The Lustre quota system distributes quotas from the Quota Master Target (aka QMT). Only one QMT instance is supported for now and only runs @@ -493,7 +493,7 @@ lctl get_param osd-*.*.quota_slave.limit* responsible for releasing quota space above the new qunit value. The qunit size isn't shrunk indefinitely and there is a minimal value of 1MB for blocks and 1,024 for inodes. This means that the quota space rebalancing - process will stop when this mininum value is reached. As a result, quota + process will stop when this minimum value is reached. As a result, quota exceeded can be returned while many slaves still have 1MB or 1,024 inodes of spare quota space. If we look at the @@ -556,7 +556,7 @@ $ cp: writing `/mnt/testfs/foo`: Disk quota exceeded. Interoperability Quotas and Version Interoperability The new quota protocol introduced in Lustre software release 2.4.0 - is not compatiblewith previous + is not compatible with previous versions. As a consequence, all Lustre servers must be upgraded to release 2.4.0 for quota to be functional. Quota limits set on the Lustre file @@ -566,7 +566,7 @@ $ cp: writing `/mnt/testfs/foo`: Disk quota exceeded. tunefs.lustre --quota against all targets. It is worth noting that running tunefs.lustre --quota is - mandatoryfor all targets formatted with a + mandatory for all targets formatted with a Lustre software release older than release 2.4.0, otherwise quota enforcement as well as accounting won't be functional. Besides, the quota protocol in release 2.4 takes for granted that the diff --git a/InstallingLustre.xml b/InstallingLustre.xml index 87fb1c6..05d4207 100644 --- a/InstallingLustre.xml +++ b/InstallingLustre.xml @@ -122,9 +122,9 @@ xml:id="installinglustre"> Lustre server packages . The required packages for Lustre servers are listed in the table below, where - verrefers to the Linux kernel distribution + ver refers to the Linux kernel distribution (e.g., 2.6.32-358.6.2.el6) and - archrefers to the processor architecture + arch refers to the processor architecture (e.g., x86_64). These packages are available in the Lustre Releasesrepository. @@ -218,7 +218,7 @@ xml:id="installinglustre"> Lustre client packages . The required packages for Lustre clients are listed in the table below, where - verrefers to the Linux distribution (e.g., + ver refers to the Linux distribution (e.g., 2.6.18-348.1.1.el5). These packages are available in the Lustre Releasesrepository. @@ -267,7 +267,7 @@ xml:id="installinglustre"> The version of the kernel running on a Lustre client must be the same as the version of the lustre-client-modules- - verpackage being installed. If the + ver package being installed. If the kernel running on the client is not compatible, a kernel that is compatible must be installed on the client before the Lustre file system software is installed. @@ -545,7 +545,7 @@ rpm -qa|egrep "lustre|wc"|sort The version of the kernel running on a Lustre client must be the same as the version of the lustre-client-modules- - verpackage being installed. If not, a + ver package being installed. If not, a compatible kernel must be installed on the client before the Lustre client packages are installed. diff --git a/LustreHSM.xml b/LustreHSM.xml index a9c6877..7a093ae 100644 --- a/LustreHSM.xml +++ b/LustreHSM.xml @@ -463,7 +463,7 @@ information (lowest bits first): Robinhood is a Policy engine and reporting tool for large file -systems. It maintains a replicate of file system medatada in a database that +systems. It maintains a replicate of file system metadata in a database that can be queried at will. Robinhood makes it possible to schedule mass action on file system entries by defining attribute-based policies, provides fast find and du enhanced clones, and provides administrators with an overall diff --git a/LustreMonitoring.xml b/LustreMonitoring.xml index 75bac55..939e2c9 100644 --- a/LustreMonitoring.xml +++ b/LustreMonitoring.xml @@ -390,7 +390,7 @@ jobid_var=disable # lctl conf_param testfs.sys.jobid_var=SLURM_JOB_ID The lctl conf_param command to enable or disable jobstats should be run on the MGS as root. The change is persistent, and - will be propogated to the MDS, OSS, and client nodes automatically when + will be propagated to the MDS, OSS, and client nodes automatically when it is set on the MGS and for each new client mount. To temporarily enable jobstats on a client, or to use a different jobid_var on a subset of nodes, such as nodes in a remote cluster that @@ -636,7 +636,7 @@ Other Monitoring Options xltop - A continuous Lustre monitor with batch scheduler - integation. diff --git a/LustreNodemap.xml b/LustreNodemap.xml index be2ade0..e9e1b8c 100644 --- a/LustreNodemap.xml +++ b/LustreNodemap.xml @@ -77,7 +77,7 @@ is described using a dash to separate the range, for example, 192.168.20.[0-255]@tcp. - The range must be contiguous. The full LNET definiton for a + The range must be contiguous. The full LNET definition for a nidlist is as follows: diff --git a/LustreOperations.xml b/LustreOperations.xml index 55cf7bf..6e705b5 100644 --- a/LustreOperations.xml +++ b/LustreOperations.xml @@ -746,7 +746,7 @@ mds1# lctl get_param mdt.testfs-MDT0000.recovery_status Where multiple NIDs are specified separated by commas (for example, 10.67.73.200@tcp,192.168.10.1@tcp), the two NIDs refer to the same host, and the Lustre software chooses the - bestone for communication. When a pair of NIDs is + best one for communication. When a pair of NIDs is separated by a colon (for example, 10.67.73.200@tcp:10.67.73.201@tcp), the two NIDs refer to two different hosts and are treated as a failover pair (the Lustre diff --git a/LustreProc.xml b/LustreProc.xml index bcdf708..ca1c8d7 100644 --- a/LustreProc.xml +++ b/LustreProc.xml @@ -2172,7 +2172,7 @@ nid refs peer max tx min qos_prio_free puts more weighting on the amount of free space available on each OST and less on how stripes are distributed across OSTs. The default value is 91 percent. When the free space priority is set to 100, weighting is based - entirely on free space and location is no longer used by the striping algorthm. + entirely on free space and location is no longer used by the striping algorithm. reserved_mb_low - The low watermark used to stop diff --git a/LustreProgrammingInterfaces.xml b/LustreProgrammingInterfaces.xml index 459e41b..9765be2 100644 --- a/LustreProgrammingInterfaces.xml +++ b/LustreProgrammingInterfaces.xml @@ -25,7 +25,7 @@ RPC. For information about universal UID/GID requirements in a Lustre file system - ennvironment, see .
diff --git a/ManagingSecurity.xml b/ManagingSecurity.xml index 80bcc6f..b1dcccc 100644 --- a/ManagingSecurity.xml +++ b/ManagingSecurity.xml @@ -107,7 +107,7 @@ other::--- users. The root squash feature works by re-mapping the user ID (UID) and group ID (GID) of the root user to a UID and GID specified by the system administrator, via the Lustre configuration - management server (MGS). The root squash feature also enables the Lustre fle system + management server (MGS). The root squash feature also enables the Lustre file system administrator to specify a set of client for which UID/GID re-mapping does not apply.
<indexterm><primary>root squash</primary><secondary>configuring</secondary></indexterm>Configuring Root Squash diff --git a/ManagingStripingFreeSpace.xml b/ManagingStripingFreeSpace.xml index 7031bb4..a0a37a4 100644 --- a/ManagingStripingFreeSpace.xml +++ b/ManagingStripingFreeSpace.xml @@ -385,7 +385,7 @@ osc.lustre-OST0002-osc.ost_conn_uuid=192.168.20.1@tcp stops object allocation for the OST if available space is less than reserved or the OST has fewer than 32 free inodes. The MDT starts object allocation when available space is twice as big as the reserved space and the OST has more than 64 free inodes. Note, clients - could appened existing files no matter what object allocation state is. + could append existing files no matter what object allocation state is. The reserved space for each OST can be adjusted by the user. Use the lctl set_param command, for example the next command reserve 1GB space for all OSTs. @@ -572,7 +572,7 @@ File 4: OST6, OST7, OST0 of free space available on each OST and less on how stripes are distributed across OSTs. The default value is 91 (percent). When the free space priority is set to 100 (percent), weighting is based entirely on free space and location - is no longer used by the striping algorthm. + is no longer used by the striping algorithm. To change the allocator weighting to 100, enter this command on the MGS: lctl conf_param fsname-MDT0000.lov.qos_prio_free=100 diff --git a/SettingUpLustreSystem.xml b/SettingUpLustreSystem.xml index ac425aa..780ee99 100644 --- a/SettingUpLustreSystem.xml +++ b/SettingUpLustreSystem.xml @@ -215,7 +215,7 @@ file size. Starting in release 2.4, using the DNE remote directory feature it is possible to increase the metadata - capacity of a single filesystem by configuting additional MDTs into + capacity of a single filesystem by configuring additional MDTs into the filesystem, see for details. For example, if the average file size is 5 MB and you have @@ -344,7 +344,7 @@ mkfs.lustre. Decreasing the inode ratio tunable bytes-per-inode will create more inodes for a given MDT size, but will leave less space for extra per-file metadata. The - inode ratio must always be strictly larget than the MDT inode size, + inode ratio must always be strictly larger than the MDT inode size, which is 512 bytes by default. It is recommended to use an inode ratio at least 512 bytes larger than the inode size to ensure the MDT does not run out of space. @@ -373,7 +373,7 @@ for potential variations in future usage. This helps reduce the format and file system check time and makes more space available for data. The table below shows the default - bytes-per-inoderatio ("inode ratio") + bytes-per-inode ratio ("inode ratio") used for OSTs of various sizes when they are formatted. diff --git a/SystemConfigurationUtilities.xml b/SystemConfigurationUtilities.xml index aac3b92..d9e7d59 100644 --- a/SystemConfigurationUtilities.xml +++ b/SystemConfigurationUtilities.xml @@ -2097,7 +2097,7 @@ mount.lustre/mnt/chip. The Management Service is running on a node reachable from this client via the cfs21@tcp0 NID.mount -t lustre cfs21@tcp0:/chipfs /mnt/chip - Similiar to the above example, but mounting a + Similar to the above example, but mounting a subdirectory under chipfs as a fileset. mount -t lustre cfs21@tcp0:/chipfs/v1_0 /mnt/chipv1_0 @@ -2727,7 +2727,7 @@ lr_reader mount.It is important to note that invocation of the subdirectory mount is voluntary by the client and not does prevent access to files that are - visibile in multiple subdirectory mounts via hard links. Furthermore, it + visible in multiple subdirectory mounts via hard links. Furthermore, it does not prevent the client from subsequently mounting the whole file system without a subdirectory being specified.
diff --git a/TroubleShootingRecovery.xml b/TroubleShootingRecovery.xml index fde2b4e..f149e5b 100644 --- a/TroubleShootingRecovery.xml +++ b/TroubleShootingRecovery.xml @@ -1241,7 +1241,7 @@ lctl get_param -n obdfilter. Repaired Unmatched Pairs total number - of unmatched MDT and OST-object paris have been + of unmatched MDT and OST-object pairs have been repaired in the scanning-phase1 diff --git a/UnderstandingFailover.xml b/UnderstandingFailover.xml index 5317617..b91a616 100644 --- a/UnderstandingFailover.xml +++ b/UnderstandingFailover.xml @@ -105,14 +105,14 @@ xml:id="understandingfailover"> - Active/passivepair - In this + Active/passive pair - In this configuration, the active node provides resources and serves data, while the passive node is usually standing by idle. If the active node fails, the passive node takes over and becomes active. - Active/activepair - In this + Active/active pair - In this configuration, both nodes are active, each providing a subset of resources. In case of a failure, the second node takes over resources from the failed node. diff --git a/UnderstandingLustre.xml b/UnderstandingLustre.xml index a9d831f..97884e1 100644 --- a/UnderstandingLustre.xml +++ b/UnderstandingLustre.xml @@ -738,7 +738,7 @@ xml:id="understandinglustre"> Verifies the linkEA entry for each and regenerates the linkEA if it is invalid or missing. The - linkEAconsists of the file name and + linkEA consists of the file name and parent FID. It is stored as an extended attribute in the file itself. Thus, the linkEA can be used to reconstruct the full path name of a file. @@ -753,7 +753,7 @@ xml:id="understandinglustre"> the OST(s) that contain the file data. If the MDT file points to one object, all the file data is stored in that object. If the MDT file points to more than one object, the file data is - stripedacross the objects using RAID 0, + striped across the objects using RAID 0, and each object is stored on a different OST. (For more information about how striping is implemented in a Lustre file system, see . @@ -795,23 +795,23 @@ xml:id="understandinglustre"> The - network bandwidthequals the aggregated bandwidth + network bandwidth equals the aggregated bandwidth of the OSSs to the targets. The - disk bandwidthequals the sum of the disk + disk bandwidth equals the sum of the disk bandwidths of the storage targets (OSTs) up to the limit of the network bandwidth. The - aggregate bandwidthequals the minimum of the disk + aggregate bandwidth equals the minimum of the disk bandwidth and the network bandwidth. The - available file system spaceequals the sum of the + available file system space equals the sum of the available space of all the OSTs. diff --git a/UnderstandingLustreNetworking.xml b/UnderstandingLustreNetworking.xml index 17f620b..f85bd6c 100644 --- a/UnderstandingLustreNetworking.xml +++ b/UnderstandingLustreNetworking.xml @@ -84,7 +84,7 @@ verify that data has been transmitted while the LND layer is connection oriented and typically does verify data transmission. LNETs are uniquely identified by a label comprised of a string corresponding to an LND and - a number, such as tcp0, o2ib0, or o2ib1, that uniquely indentifies each LNET. Each node on an + a number, such as tcp0, o2ib0, or o2ib1, that uniquely identifies each LNET. Each node on an LNET has at least one network identifier (NID). A NID is a combination of the address of the network interface and the LNET label in the form:address@LNET_label. diff --git a/UpgradingLustre.xml b/UpgradingLustre.xml index 637785f..406b281 100644 --- a/UpgradingLustre.xml +++ b/UpgradingLustre.xml @@ -5,7 +5,7 @@ xml:id="upgradinglustre"> Upgrading a Lustre File System This chapter describes interoperability between Lustre software releases. It also provides procedures for upgrading from Lustre software - release 1.8 to Lustre softeware release 2.x , from a Lustre software release + release 1.8 to Lustre software release 2.x , from a Lustre software release 2.x to a more recent Lustre software release 2.x (major release upgrade), and from a a Lustre software release 2.x.y to a more recent Lustre software release 2.x.y (minor release upgrade). It includes the following @@ -186,7 +186,7 @@ xml:id="upgradinglustre"> not installed, configured, or administered properly. If a full backup of the file system is not practical, a device-level backup of the MDT file system is recommended. See - for a procedure. + for a procedure. @@ -391,7 +391,7 @@ conf_param $FSNAME.quota.ost=$QUOTA_TYPE The mounting order described in the steps above must be followed - for the intial mount and registration of a Lustre file system after an + for the initial mount and registration of a Lustre file system after an upgrade. For a normal start of a Lustre file system, the mounting order is MGT, OSTs, MDT(s), clients. @@ -424,7 +424,7 @@ conf_param $FSNAME.quota.ost=$QUOTA_TYPE not installed, configured, or administered properly. If a full backup of the file system is not practical, a device-level backup of the MDT file system is recommended. See - for a procedure. + for a procedure. -- 1.8.3.1