From 0daa7ba0b558ff22fa1c1e014e754cbd08366c00 Mon Sep 17 00:00:00 2001 From: Steffen Maier Date: Tue, 14 Mar 2017 14:17:29 +0100 Subject: [PATCH] lsluns: clarify discovery use case, relation to NPIV and to zfcp auto LUN scan Signed-off-by: Steffen Maier Reviewed-by: Jens Remus Signed-off-by: Michael Holzheu --- zconf/lsluns | 3 +++ zconf/lsluns.8 | 18 ++++++++++++++++++ 2 files changed, 21 insertions(+) diff --git a/zconf/lsluns b/zconf/lsluns index 0636cd3c..75c31eee 100755 --- a/zconf/lsluns +++ b/zconf/lsluns @@ -174,6 +174,9 @@ $PROGRAM_NAME [-c ] ... [-p ] ... [-h] [-v] List LUNs discovered in the Fibre Channel (FC) Storage Area Network (SAN). This causes extra SAN traffic for each target port WWPN. + Discovering LUNs only makes sense for NPIV-enabled FCP devices + without zfcp automatic LUN scan. zfcp automatic LUN scan is available + as of kernel version 2.6.37, if not disabled with zfcp.allow_lun_scan=0. $PROGRAM_NAME -a [-c ] ... [-p ] ... [-h] [-v] diff --git a/zconf/lsluns.8 b/zconf/lsluns.8 index bd03751f..da8d5b21 100644 --- a/zconf/lsluns.8 +++ b/zconf/lsluns.8 @@ -46,6 +46,24 @@ encryption, use other tools such as or .BR "lsscsi \-tv" . +.SS Details on lsluns without -a option + +.TP +Prerequisite +Discovering LUNs only makes sense for NPIV-enabled FCP devices +without zfcp automatic LUN scan. zfcp automatic LUN scan is available +as of kernel version 2.6.37, if not disabled with zfcp.allow_lun_scan=0. + +With available and enabled zfcp automatic LUN scan, +the kernel already performs LUN discovery. + +.TP +Temporary LUN Attachment +If not attached already, lsluns temporarily attaches LUN 0 +(or if this fails the WLUN 0xc101000000000000) during runtime. +Do not terminate lsluns with a signal. Signals interfere +with the removal of temporarily attached LUNs. + .SH OPTIONS .TP .BR \-a ", " \-\-active