From: Felix Pusch Date: Sat, 29 Oct 2022 14:10:48 +0000 (+0200) Subject: LUDOC-11 misc: minor corrections X-Git-Url: https://git.whamcloud.com/?a=commitdiff_plain;h=e942f71118ffa303969843053140efc0fa84353e;p=doc%2Fmanual.git LUDOC-11 misc: minor corrections Signed-off-by: Felix Pusch Change-Id: I7782bc926d3c66f9246100754ac35bef73f90fad Reviewed-on: https://review.whamcloud.com/c/doc/manual/+/49053 Tested-by: jenkins Reviewed-by: Andreas Dilger --- diff --git a/ManagingStripingFreeSpace.xml b/ManagingStripingFreeSpace.xml index a029799..a84da3d 100644 --- a/ManagingStripingFreeSpace.xml +++ b/ManagingStripingFreeSpace.xml @@ -110,7 +110,7 @@ even if their I/Os do not overlap. This can be avoided if I/O can be stripe aligned so that each stripe is accessed by only one client. Since Lustre 2.13, the 'overstriping' feature is available, allowing more - than stripe per OST. This is particularly helpful for the case where + than one stripe per OST. This is particularly helpful for the case where thread count exceeds OST count, making it possible to match stripe count to thread count even in this case. @@ -384,7 +384,7 @@ lmm_stripe_offset: 0 command similar to: [client]# lfs getstripe /mnt/lustre This command produces output similar to: - /mnt/lustre + /mnt/lustre (Default) stripe_count: 1 stripe_size: 1M stripe_offset: -1 In this example, the default stripe count is 1 (data blocks are striped over a single OST), the default stripe size is 1 MB, and the objects are created @@ -744,8 +744,8 @@ $ lfs setstripe --component-add -E -1 -c 4 -o 6-7,0,5 \ filename The option --component-del is used to remove the component(s) specified by component ID or flags from an existing - file. This operation will result in any data stored in the deleted - component will be lost. + file. Any data stored in the deleted component will be lost after + this operation. The ID specified by -I option is the numerical unique ID of the component, which can be obtained by command lfs getstripe -I command, and the flag specified by @@ -754,8 +754,8 @@ $ lfs setstripe --component-add -E -1 -c 4 -o 6-7,0,5 \ lfs getstripe --component-flags. For now, we only have two flags init and ^init for instantiated and un-instantiated components respectively. - Deletion must start with the last component because hole is - not allowed. + Deletion must start with the last component because creation + of a hole in the middle of a file layout is not allowed. Example $ lfs getstripe -I /mnt/testfs/del_comp 1 @@ -864,10 +864,10 @@ $ lfs getstripe /mnt/testfs/pfldir/pflfile lfs setstripe --component-add/del can't be run - on a directory, because default layout in directory is likea config, + on a directory, because the default layout in directory is like a config, which can be arbitrarily changed by lfs setstripe, - while layout in file may have data (OST objects) attached. If you want - to delete default layout in a directory, run + while the layout of a file may have data (OST objects) attached. + If you want to delete the default layout in a directory, run lfs setstripe -d dirname to return the directory to the filesystem-wide defaults, like: @@ -1447,7 +1447,7 @@ STRIPE OPTIONS: lmm_pattern: raid0 lmm_layout_gen: 0 lmm_stripe_offset: -1 - + lcme_id: 3 lcme_mirror_id: 0 lcme_flags: 0 @@ -1458,7 +1458,7 @@ STRIPE OPTIONS: lmm_pattern: raid0 lmm_layout_gen: 0 lmm_stripe_offset: -1 - + lcme_id: 4 lcme_mirror_id: 0 lcme_flags: extension @@ -1589,7 +1589,7 @@ STRIPE OPTIONS: lmm_stripe_offset: 0 lmm_objects: - 0: { l_ost_idx: 0, l_fid: [0x100000000:0x5:0x0] } - + lcme_id: 2 lcme_mirror_id: 0 lcme_flags: extension @@ -1600,7 +1600,7 @@ STRIPE OPTIONS: lmm_pattern: raid0 lmm_layout_gen: 0 lmm_stripe_offset: -1 - + lcme_id: 3 lcme_mirror_id: 0 lcme_flags: 0 @@ -1611,7 +1611,7 @@ STRIPE OPTIONS: lmm_pattern: raid0 lmm_layout_gen: 0 lmm_stripe_offset: -1 - + lcme_id: 4 lcme_mirror_id: 0 lcme_flags: extension @@ -1661,7 +1661,7 @@ STRIPE OPTIONS: lmm_stripe_offset: 0 lmm_objects: - 0: { l_ost_idx: 0, l_fid: [0x100000000:0x5:0x0] } - + lcme_id: 3 lcme_mirror_id: 0 lcme_flags: init @@ -1674,7 +1674,7 @@ STRIPE OPTIONS: lmm_stripe_offset: 1 lmm_objects: - 0: { l_ost_idx: 1, l_fid: [0x100010000:0x8:0x0] } - + lcme_id: 4 lcme_mirror_id: 0 lcme_flags: extension @@ -1734,7 +1734,7 @@ STRIPE OPTIONS: lmm_stripe_offset: 1 lmm_objects: - 0: { l_ost_idx: 1, l_fid: [0x100010000:0x8:0x0] } - + lcme_id: 8 lcme_mirror_id: 0 lcme_flags: init @@ -1747,7 +1747,7 @@ STRIPE OPTIONS: lmm_stripe_offset: 0 lmm_objects: - 0: { l_ost_idx: 0, l_fid: [0x100000000:0x6:0x0] } - + lcme_id: 4 lcme_mirror_id: 0 lcme_flags: extension @@ -1819,7 +1819,7 @@ STRIPE OPTIONS: lmm_stripe_offset: 0 lmm_objects: - 0: { l_ost_idx: 0, l_fid: [0x100000000:0x6:0x0] } - + lcme_id: 4 lcme_mirror_id: 0 lcme_flags: extension @@ -2215,7 +2215,7 @@ testfs-OST0000_UUID 94181368 56330708 37850660 59% /mnt/lustre[OST:0] testfs-OST0001_UUID 94181368 56385748 37795620 59% /mnt/lustre[OST:1] testfs-OST0002_UUID 94181368 54352012 39829356 57% /mnt/lustre[OST:2] filesystem summary: 282544104 167068468 39829356 57% /mnt/lustre - + [client1] $ lfs df -hv UUID bytes Used Available Use% Mounted on testfs-MDT0000_UUID 8.7G 996.1M 7.8G 11% /mnt/lustre[MDT:0] @@ -2223,7 +2223,7 @@ testfs-OST0000_UUID 89.8G 53.7G 36.1G 59% /mnt/lustre[OST:0] f testfs-OST0001_UUID 89.8G 53.8G 36.0G 59% /mnt/lustre[OST:1] f testfs-OST0002_UUID 89.8G 51.8G 38.0G 57% /mnt/lustre[OST:2] f filesystem summary: 269.5G 159.3G 110.1G 59% /mnt/lustre - + [client1] $ lfs df -iH UUID Inodes IUsed IFree IUse% Mounted on testfs-MDT0000_UUID 2.21M 41.9k 2.17M 1% /mnt/lustre[MDT:0] @@ -2373,7 +2373,7 @@ File 4: OST6, OST7, OST0 Since Lustre 2.13 the ea_inode feature is enabled by default on all newly formatted ldiskfs MDT filesystems. - The maximum stripe count for a single file does not limit the + The maximum stripe count for a single file does not limit the maximum number of OSTs that are in the filesystem as a whole, only the maximum possible size and maximum aggregate bandwidth for the file. diff --git a/Revision.xml b/Revision.xml index 33886a7..5be44b4 100644 --- a/Revision.xml +++ b/Revision.xml @@ -20,7 +20,7 @@ tagging is removed), and within the text using a distinct box. - Which version amd I running? + Which version am I running? version which version of Lustre am I running? diff --git a/UnderstandingLustre.xml b/UnderstandingLustre.xml index 7da5245..e8c2137 100644 --- a/UnderstandingLustre.xml +++ b/UnderstandingLustre.xml @@ -714,7 +714,7 @@ Verifies the linkEA entry for each inode and regenerates it if invalid or missing. The linkEA - stores of the file name and parent FID. It is stored as an extended + stores the file name and parent FID. It is stored as an extended attribute in each inode. Thus, the linkEA can be used to reconstruct the full path name of a file from only the FID.