Whamcloud - gitweb
LU-19021 ptlrpc: Add obd info to nodemap exports output 48/59248/4
authorMarc Vef <mvef@whamcloud.com>
Wed, 21 May 2025 11:35:33 +0000 (13:35 +0200)
committerOleg Drokin <green@whamcloud.com>
Sat, 7 Jun 2025 23:03:01 +0000 (23:03 +0000)
commit0c1c85c7ec39a9806824f0d5ade7bd3816e8db73
tree23d91e579f27ecc1c196fdd0a89c2386525ca515
parent1c6cc68314f4badaa6555e58bb5a79f389c0d2ab
LU-19021 ptlrpc: Add obd info to nodemap exports output

When clients connect to MDTs/OSTs, a new export is generated on the
server-side during obd_connect_*() with the client's UUID. For each
target, a separate export is created which is then added to the
nodemap's "nm_member_list", if applicable.

Currently, "lctl get_param nodemap.NM_NAME.exports" prints the UUID
and NID information for each entry in the "nm_member_list". Because
the obd device is not listed, duplicate entries appear to be shown for
each client, which can be confusing for the administrator.

This patch extends the nodemap.NM_NAME.exports output by also showing
the obd the client is connected to, e.g., MDT0000, MDT0001, etc, such
that the shown entries no longer appear as duplucate.

Signed-off-by: Marc Vef <mvef@whamcloud.com>
Change-Id: I681480f9258e57c522acc148f4096a8f40c71eab
Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/59248
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Reviewed-by: Sebastien Buisson <sbuisson@ddn.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
lustre/ptlrpc/nodemap_lproc.c