X-Git-Url: https://git.whamcloud.com/?a=blobdiff_plain;f=LustreOperations.xml;h=64ddbb4bbe1a9fa709dd8552424fe756862a81a3;hb=fa289da8d2a3a5f4f3028a2bbf0ba69ae8e91d2c;hp=aa46defcbc5d03bc573cca9ea953286b299de0d1;hpb=ff25c07facab19c2e373d662a343ee2a25955552;p=doc%2Fmanual.git diff --git a/LustreOperations.xml b/LustreOperations.xml index aa46def..64ddbb4 100644 --- a/LustreOperations.xml +++ b/LustreOperations.xml @@ -376,9 +376,9 @@ client# lfs mkdir –i This command will allocate the sub-directory remote_dir onto the MDT of index - mdtindex. For more information on adding additional MDTs + mdt_index. For more information on adding additional MDTs and - mdtindex see + mdt_index see . An administrator can allocate remote sub-directories to separate @@ -387,8 +387,13 @@ client# lfs mkdir –i will leave the namespace below it inaccessible. For this reason, by default it is only possible to create remote sub-directories off MDT0. To relax this restriction and enable remote sub-directories off any MDT, an - administrator must issue the command - lctl set_param mdt.*.enable_remote_dir=1. + administrator must issue the following command on the MGS: + mgs# lctl conf_param fsname.mdt.enable_remote_dir=1 + For Lustre filesystem 'scratch', the command executed is: + mgs# lctl conf_param scratch.mdt.enable_remote_dir=1 + To verify the configuration setting execute the following command on any + MDS: + mds# lctl get_param mdt.*.enable_remote_dir With Lustre software version 2.8, a new tunable is available to allow users with a specific group ID to create @@ -397,9 +402,13 @@ client# lfs mkdir –i parameter to the 'wheel' or 'admin' group ID allows users with that GID to create and delete remote and striped directories. Setting this parameter to -1 on MDT0 to permanently allow any - non-root users create and delete remote and striped directories. For - example: - lctl set_param -P mdt.*.enable_remote_dir_gid=-1 + non-root users create and delete remote and striped directories. + On the MGS execute the following command: + mgs# lctl conf_param fsname.mdt.enable_remote_dir_gid=-1 + For the Lustre filesystem 'scratch', the commands expands to: + mgs# lctl conf_param scratch.mdt.enable_remote_dir_gid=-1. + The change can be verified by executing the following command on every MDS: + mds# lctl get_param mdt.*.enable_remote_dir_gid
@@ -420,9 +429,11 @@ client# lfs mkdir –i striping metadata Creating a directory striped across multiple MDTs - Lustre 2.8 enables individual files in a given directory to - record their metadata on separate MDTs (a striped - directory). The result of this is that metadata requests for + The Lustre 2.8 DNE feature enables individual files in a given + directory to store their metadata on separate MDTs (a striped + directory) once additional MDTs have been added to the + filesystem, see . + The result of this is that metadata requests for files in a striped directory are serviced by multiple MDTs and metadata service load is distributed over all the MDTs that service a given directory. By distributing metadata service load over multiple MDTs, @@ -430,13 +441,16 @@ client# lfs mkdir –i performance. Prior to the development of this feature all files in a directory must record their metadata on a single MDT. This command to stripe a directory over - mdt_count MDTs is: - + mdt_count MDTs is: + -client# lfs setdirstripe -c +client# lfs mkdir -c mdt_count /mount_point/new_directory + The striped directory feature is most useful for distributing + single large directories (50k entries or more) across multiple MDTs, + since it incurs more overhead than non-striped directories.
@@ -629,7 +643,7 @@ lctl set_param -P -d </section> <section xml:id="dbdoclet.50438194_88217"> <title>Listing Parameters - To list Lustre or LNET parameters that are available to set, use + To list Lustre or LNet parameters that are available to set, use the lctl list_param command. For example: @@ -697,7 +711,7 @@ osc.myth-OST0004-osc-ffff8800376bdc00.cur_grant_bytes=33808384 --mgsnode= or --servicenode=). To display the NIDs of all servers in networks configured to work - with the Lustre file system, run (while LNET is running): + with the Lustre file system, run (while LNet is running): lctl list_nids @@ -727,12 +741,12 @@ client# mount -t lustre 192.168.10.1@tcp0:192.168.10.2@tcp0:/testfs \ /mnt/testfs mds0# umount /mnt/mdt mds1# mount -t lustre /dev/sda1 /mnt/test/mdt -mds1# cat /proc/fs/lustre/mds/testfs-MDT0000/recovery_status +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 @@ -841,9 +855,9 @@ tune2fs [-m reserved_blocks_percent] /dev/ Replacing an Existing OST or MDT To copy the contents of an existing OST to a new OST (or an old MDT to a new MDT), follow the process for either OST/MDT backups in - or - . For more information on - removing a MDT, see + or + . + For more information on removing a MDT, see .