LU-17392 build: compatibility updates for kernel 6.7 Linux commit v6.6-rc4-53-gc42d50aefd17 mm: shrinker: add infrastructure for dynamically allocating shrinker Users of struct shrinker must dynamically allocate shrinker objects to avoid run-time warnings. Provide a wrapper for older kernels to alloc+register shinkers and unregister+free. Use get_group_info() and put_group_info() wrappers instead of open coding the reference counting on group_info.usage Signed-off-by: Shaun Tancheff <shaun.tancheff@hpe.com> Change-Id: Ie07bdb7fe3eb6060bd84f95f860f1b53d120a605 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/53621 Tested-by: Maloo <maloo@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Jian Yu <yujian@whamcloud.com> Reviewed-by: James Simmons <jsimmons@infradead.org>
LU-17612 sec: return keyring errors to userspace In current code, Linux keyring errors, when using GSS Kerberos, are all masked under a generic ECONNREFUSED error. That makes it hard to understand the root cause of the problem for the I/O caller. Update the code to propagate errors from request_key() up to the application. struct ptlrpc_cli_ctx * gss_sec_lookup_ctx_kr(...) is modified to now returns a NULL pointer or -errval. This is tested by callers and propagated. NULL values are still converted to ECONNREFUSED. Test-Parameters: trivial Test-Parameters: kerberos=true testlist=sanity-krb5 Test-Parameters: testgroup=review-dne-selinux-ssk-part-2 Change-Id: I13792f141a961036bc9f7629a4a2db692e245c41 Signed-off-by: Aurelien Degremont <adegremont@nvidia.com> Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54296 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Reviewed-by: Sebastien Buisson <sbuisson@ddn.com>
LU-930 ptlrpc: remove spurious error messages Stop errors being printed when a disconnect RPC times out, since this error is ignored anyway, and adds no value to be printed. Remove -61 = -ENODATA error from seq_server_init() since this is an "expected" event for a new target and the error code is not useful. Test-Parameters: trivial Signed-off-by: Andreas Dilger <adilger@whamcloud.com> Change-Id: I0f695409617061d46a1b910108cda05f863ebbe5 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54285 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Arshad Hussain <arshad.hussain@aeoncomputing.com> Reviewed-by: Sebastien Buisson <sbuisson@ddn.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-17317 sec: fix sanity-sec test_28 Improve sanity-sec test_28 to verify that srpc_contexts is valid YAML output. Also remove the ctx information from the output, as printing out a kernel pointer is not ideal. Fixes: f6687bafcb ("LU-17317 sec: add srpc_serverctx proc file") Test-Parameters: trivial Test-Parameters: kerberos=true testlist=sanity-krb5 Test-Parameters: testgroup=review-dne-selinux-ssk-part-2 Signed-off-by: Sebastien Buisson <sbuisson@ddn.com> Change-Id: Ie48dc61adfd5017a2313981f27407c9d3b69dd71 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54280 Reviewed-by: Aurelien Degremont <adegremont@nvidia.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com>
LU-17555 ptlrpc: removed unused lm_repsize accessors ptlrpc_req_get_repsize() and ptlrpc_req_set_repsize() are unused. ptlrpc_req_set_repsize() is superseded by ptlrpc_request_set_replen() so remove the unused variants. Test-Parameters: trivial Signed-off-by: Shaun Tancheff <shaun.tancheff@hpe.com> Change-Id: Ib89a57c00605b110ec28040614aecba9826f5ffa Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54089 Reviewed-by: Arshad Hussain <arshad.hussain@aeoncomputing.com> Reviewed-by: James Simmons <jsimmons@infradead.org> Reviewed-by: Oleg Drokin <green@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com>
LU-17334 lmv: exclude newly added MDT in mkdir Exclude newly added MDT in QoS mkdir for 30 seconds in case connections between MDTs are not ready, which may cause lookup fail. Signed-off-by: Lai Siyao <lai.siyao@whamcloud.com> Change-Id: Ibb5e6eda29ddfff8f66708d72e33453a96f5e7ef Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/53860 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Hongchao Zhang <hongchao@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-14535 quota: get all quota info in LFS This patch adds option "-a" for LFS to get the quota info of all quota IDs. it iterates quota setting saved in global quota setting files "quota_master/md-0x0" and "quota_master/dt-0x0" from QMT and iterates the quota usage info saved in acct quota files in the backend FS (LDiskFS or ZFS) from QSDs, then merge the two kinds of quota info at client and print it in the similar way as "lfs quota -u|-g|-p". $lfs quota -a -u /mnt/lustre Filesystem /mnt/lustre, Disk usr quotas quota_id kbytes quota limit grace files quota limit grace root 9684 0 0 - 1019 0 0 - bin 4 0 102400 - 1 0 10240 - daemon 4 0 102400 - 1 0 10240 - adm 4 0 102400 - 1 0 10240 - lp 4 0 102400 - 1 0 10240 - sync 4 0 102400 - 1 0 10240 - shutdown 4 0 102400 - 1 0 10240 - halt 4 0 102400 - 1 0 10240 - mail 4 0 102400 - 1 0 10240 - $lfs quota -a -g /mnt/lustre Filesystem /mnt/lustre, Disk grp quotas quota_id kbytes quota limit grace files quota limit grace root 9684 0 0 - 1019 0 0 - bin 4 0 204800 - 1 0 20480 - daemon 4 0 204800 - 1 0 20480 - adm 4 0 204800 - 1 0 20480 - lp 4 0 204800 - 1 0 20480 - sync 4 0 204800 - 1 0 20480 - shutdown 4 0 204800 - 1 0 20480 - halt 4 0 204800 - 1 0 20480 - mail 4 0 204800 - 1 0 20480 - This patch also fixes an deadlock issue in qmt_pool_recalc, the rw_semaphore "qmt_pool_info.qpi_sarr.osts.op_rw_sem" has been acquired in qmt_pool_recalc (read mode), but it was acquired once more in qmt_seed_glbe_all (read mode) and will be stuck if there is a pending write mode lock acquisition from another thread. qsd_reint_qpool D Call Trace: schedule+0x29/0x70 rwsem_down_read_failed+0x105/0x1c0 call_rwsem_down_read_failed+0x18/0x30 down_read+0x20/0x40 qmt_seed_glbe_all+0x3a0/0x800 [lquota] qmt_site_recalc_cb+0x3c7/0x800 [lquota] cfs_hash_for_each_tight+0x11e/0x330 cfs_hash_for_each+0x10/0x20 [libcfs] qmt_pool_recalc+0x9fc/0x1310 [lquota] llog_process_th D Call Trace: schedule+0x29/0x70 rwsem_down_write_failed+0x215/0x3c0 call_rwsem_down_write_failed+0x17/0x30 down_write+0x2d/0x3d lu_tgt_pool_remove+0x36/0x1e0 [obdclass] qmt_pool_add_rem+0x655/0x920 [lquota] qmt_pool_rem+0x10/0x20 [lquota] lod_pool_remove_q+0xd6/0x1d0 [lod] class_process_config+0x16f2/0x2b20 class_config_llog_handler+0x839/0x1540 llog_process_thread+0x913/0x1c10 llog_process_thread_daemonize+0x9f/0xe0 Test-Parameters: testlist=sanity-quota env=SLOW=yes,ONLY=49,NUM_QIDS=20000 Change-Id: I08feb928fbf34635ec9c5c341de993c718798dc9 Signed-off-by: Hongchao Zhang <hongchao@whamcloud.com> Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/42098 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: James Simmons <jsimmons@infradead.org> Reviewed-by: Sergey Cheremencev <scherementsev@ddn.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
LU-17576 nodemap: remove nodemap_rbtree.c Remove nodemap_rbtree.c. This was a port of an in-progress rbtree patch to the kernel. Every kernel that Lustre supports should have the needed macro. The rest of the stuff in the file is unused. Signed-off-by: Timothy Day <timday@amazon.com> Change-Id: I25d6eea90a1e9b983fb0be690384e50c6808cb7b Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54136 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Sebastien Buisson <sbuisson@ddn.com> Reviewed-by: James Simmons <jsimmons@infradead.org>
LU-17217 obd: reserve server-side connection policy bits Reserve bits for new mechanism enabling server to refuse client connections based on arbitrary criterion that Lustre admins can define via policies. The policies envisioned currently are: ALLOW (allow connection to procede as normal) WARN (generate a warning on the client-side) SOFT_BLOCK (block mounting unless client overrides) HARD_BLOCK (block mounting entirely) In order to SOFT_BLOCK a client, servers need to be able to differentiate between clients that support scp and those that don't scp. Older clients would not have the mechanism to override a server-side SOFT_BLOCK, so they would HARD_BLOCK instead. We also need a bitmask for the client/server to communciate policy opinions (i.e. don't soft-block me). Therefore, this patch reserves: 1) OBD_CONNECT2_CONN_POLICY 2) 8 bits of obd_connect_data It also explicitly defines the use of some of the bits via an enum. Test-Parameters: trivial Signed-off-by: Timothy Day <timday@amazon.com> Change-Id: If717045728e516eece7c2d812f8ee6e7ebba9497 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/52793 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Sebastien Buisson <sbuisson@ddn.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-13048 mdd: allow release after a non-blocking migrate lfs setstripe -i0 file lfs hsm_archive file lfs migrate -n -i1 file lfs hsm_release file These actions lead to "Cannot send HSM request ...: Operation not permitted". This happens because of data version mismatch. This error is returned by mdt_hsm_release() when the data versions are not the same. This patch only corrects the non-blocking migrations. mdd_swap_layouts is updated to check and update the HSM archive version when possible. The new and old data versions are added as arguments to this function. If the old data version does not match the data version in the HSM attribute, we don't update the HSM attribute because we don't know what caused the inconsistency. During a swap between a volatile and a regular file, if both objects have an HSM xattr, mdd_swap_layouts was called from the MDT HSM layer (release and restore). In this case, we want to swap the HSM xattr (previously done using SWAP_LAYOUTS_MDS_HSM as a last argument to mdd_swap_layouts). If only the regular file has an HSM attribute, mdd_swap_layouts was called after a migration (blocking or not). In this case, we want to update the HSM archive version only if the file is not dirty and if the new data version is provided. Also, this patch removes the CL_LAYOUT event that was emitted for a release. Since a CL_HSM event with HE_RELEASE flag is also emitted, the CL_LAYOUT is unecessary. For "lfs swap_layouts", the operation is denied on 2 files with HSM xattr (HSM xattr swap will cause inconsistencies). With non-HSM file and archived file, the operation is allowed but the dirty flag is set on the HSM file. Add lustre_swab_close_data_special() to swab close_data fields inside the union (specific to some types of close). Add regression test sanity-hsm 607a, 607b and 607c. Test-Parameters: clientversion=2.15.4 testlist=sanity-hsm Test-Parameters: serverversion=2.15.4 testlist=sanity-hsm env=EXCEPT="114 409a" Test-Parameters: testlist=sanity-hsm env=ONLY=607,ONLY_REPEAT=15 Signed-off-by: Courrier Guillaume <guillaume.courrier@cea.fr> Signed-off-by: Etienne AUJAMES <eaujames@ddn.com> Change-Id: I6e90131235f96255b636eea366ad0cef5f4f0b19 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/49236 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: James Simmons <jsimmons@infradead.org> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-17484 gss: reply error for SEC_CTX_INIT on wrong node When a server receives a SEC_CTX_INIT request for a target that is not available (either stopping, or not set up yet, or moved to a failover node), the request gets dropped. This makes the client-side RPC time out, increasing the time it takes to establish a proper gss context with the target, because it slows down the HA mechanism that tries alternate failover NIDs. Instead of dropping the request reply for SEC_CTX_INIT, the server needs to send back a proper error reply. The client will then be able to immediately try alternate failover NIDs, speeding mount/reconnect process up, and avoiding potential eviction. Test-Parameters: trivial Test-Parameters: kerberos=true testlist=sanity-krb5 Test-Parameters: testgroup=review-dne-selinux-ssk-part-2 Signed-off-by: Sebastien Buisson <sbuisson@ddn.com> Change-Id: Id2cefaa7d54729a63c7be13b65d7ace579bcaa78 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/53970 Reviewed-by: Aurelien Degremont <adegremont@nvidia.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com>
LU-17379 ptlrpc: fix check for callback discard In ptlrpc_unregister_reply() decision about need to discard request-out callback is done too early, before LNetMDUnlink() invokes reply callback. Therefore at the monent of discard check rq_reply_unlinked is not set yet and discard is skipped always. Patch removes discard check from __ptlrpc_cli_wait_unlink() and does that after LNetMDUnlink() call right inside ptlrpc_unregister_reply(). That makes __ptlrpc_cli_wait_unlink() unused, so it was removed and only ptlrpc_cli_wait_unlink() remains Fixes: babf0232273 ("LU-13368 lnet: discard the callback") Signed-off-by: Mikhail Pershin <mpershin@whamcloud.com> Change-Id: I6448cafa8a0b81d7ba0172ad1709e75e592d4924 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/53937 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Serguei Smirnov <ssmirnov@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-17454 nodemap: allow mapping for root Allow an id mapping for root, to match what is implemented for regular users, with the following behavior: - if admin property is set, root remains root. - if admin property is not set, the idmap for '0' is taken into account. - if admin property is not set and there is no idmap for '0' and deny_unknown property is not set, root is squashed to the squash uid/gid. - if admin property is not set and there is no idmap for '0' and deny_unknown property is set, root is blocked. Note that map_mode remains ignored for root. Also, capabilities are not dropped for root when mapped, just like it is done for regular users. If admins want to drop root capabilities, root must be squashed. sanity-sec test_15 is updated to test root mapping. Signed-off-by: Sebastien Buisson <sbuisson@ddn.com> Change-Id: Id2e950b99e3b3ba27179408c647e1f7b7c49e32e Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/53870 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Patrick Farrell <pfarrell@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-17357 mgc: wait for sptlrpc config log The sptlrpc config log is mandatory to establish connections to targets with proper security context. So wait for its retrieval. Add sanity-sec test_68 to exercise this, and improve test_32 for mgssec. Signed-off-by: Sebastien Buisson <sbuisson@ddn.com> Change-Id: I5352e926dc6a9a68db1224629c68a42b74bee8a4 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/53423 Reviewed-by: Mikhail Pershin <mpershin@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com>
LU-17317 sec: add srpc_serverctx proc file GSS srpc contexts for client connections can already be dumped via proc file <mdc,osc>.*.srpc_contexts. This patch adds a new proc file to dump server side GSS srpc contexts, e.g.: mgs.MGS.gss.srpc_serverctx mdt.testfs-MDT0000.gss.srpc_serverctx obdfilter.testfs-OST0000.gss.srpc_serverctx The GSS context information is dumped as YAML, with one line per context, like this: - 0000000013221bdf: { peer_nid: 192.168.56.206@tcp, uid: 0, ctxref: 1, expire: 1707934985, delta: 3401, flags: [uptodate, cached], seq: 0, win: 2048, key: 00000000, keyref: 0, hdl: "0x5ae1a771fd57043:0x65a64972fda4e200", mech: "krb5 (aes256-cts-hmac-sha1-96)" } Because of this new syntax, sanity-sec test_28 needs to be fixed. Test-Parameters: trivial Test-Parameters: kerberos=true testlist=sanity-krb5 Test-Parameters: testgroup=review-dne-selinux-ssk-part-2 Signed-off-by: Sebastien Buisson <sbuisson@ddn.com> Change-Id: I37da9ffe6dd5884006b36271185a4d7155ead65b Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/53376 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Aurelien Degremont <adegremont@nvidia.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-16724 ptlrc: ptlrpc: extend sec bulk functionality Features such as client-side-data-compression and unaligned direct I/O need page/buffer pools for good performance. This patch extends sec bulk functionality to allocate different size buffers. Memory shrinking and other usefull features should still work as expected. Signed-off-by: Artem Blagodarenko <ablagodarenko@ddn.com> Change-Id: I929b4dfdcb0e8197f3804629b000af0d4bd6f2a0 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/52335 Reviewed-by: Oleg Drokin <green@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com>
LU-12273 lod: metadata overstriping This adds overstriping for MDTs, similar to overstriping for OSTs (added in LU-9846). This adds a new option to setdirstripe, -C, allowing creation of more than one stripe per MDT. It is also possible to place multiple stripes on the same MDT using specific striping with -m. This allows a single directory to more fully use the full capability of each MDT in the file system. Two limitations of note: 1. This requires > 1 MDT, otherwise the DNE subsystem is not initialized. 2. Due to recovery limitations, we allow a max of only 5 stripes per MDT. MDT overstriping increases mdtest-hard-write performance by up to 13%, mdtest-hard-stat by 93%, at the cost of a slight drop in mdtest-hard-read (7%), with no change in delete. 4 MDTs, 1 stripe/MDT: mdtest-hard-write 117.399467 kIOPS : time 339.496 seconds mdtest-hard-stat 727.020749 kIOPS : time 55.666 seconds mdtest-hard-read 245.556392 kIOPS : time 162.897 seconds mdtest-hard-delete 104.379111 kIOPS : time 382.710 seconds 4 MDTs, 4 stripes/MDTs: mdtest-hard-write 132.963290 kIOPS : time 309.093 seconds mdtest-hard-stat 1408.161148 kIOPS : time 30.107 seconds mdtest-hard-read 229.383910 kIOPS : time 179.576 seconds mdtest-hard-delete 103.284369 kIOPS : time 398.442 seconds Test-Parameters: testlist=sanity env=ONLY=300u serverversion=2.14.0 Signed-off-by: Patrick Farrell <pfarrell@whamcloud.com> Signed-off-by: Qian Yingjin <qian@ddn.com> Signed-off-by: Lai Siyao <lai.siyao@whamcloud.com> Change-Id: I11556b223029820bd335e87c7bf073970e03468d Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/35034 Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com> Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Oleg Drokin <green@whamcloud.com>
LU-6142 ptlrpc: Fix style issues for niobuf.c This patch fixes issues reported by checkpatch for file lustre/ptlrpc/niobuf.c Test-Parameters: trivial Signed-off-by: Arshad Hussain <arshad.hussain@aeoncomputing.com> Change-Id: I2b431ef591fe3e920e57ce173250e600dc3b5f1f Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54061 Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Timothy Day <timday@amazon.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com>
LU-6142 ptlrpc: Fix style issues for sec_config.c This patch fixes issues reported by checkpatch for file lustre/ptlrpc/sec_config.c Test-Parameters: trivial Signed-off-by: Arshad Hussain <arshad.hussain@aeoncomputing.com> Change-Id: I3cdf2d900f3e4628c928ed513732c7fbc564124c Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54060 Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Timothy Day <timday@amazon.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com>
LU-6142 ptlrpc: Fix style issues for import.c This patch fixes issues reported by checkpatch for file lustre/ptlrpc/import.c Test-Parameters: trivial Signed-off-by: Arshad Hussain <arshad.hussain@aeoncomputing.com> Change-Id: I81aedd7fdb485932645a085a20359919f5a1b935 Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54059 Reviewed-by: Andreas Dilger <adilger@whamcloud.com> Reviewed-by: Timothy Day <timday@amazon.com> Reviewed-by: Oleg Drokin <green@whamcloud.com> Tested-by: jenkins <devops@whamcloud.com> Tested-by: Maloo <maloo@whamcloud.com>