Hitachi Dynamic Link Manager, Руководство пользователя

Страница: 521 / 746

7. Utility Reference
497
#dlmcfgmgr -logfs
KAPL10938-I dlmcfgmgr Log File Size(KB) : 10240
#
Reference information
If you do not specify a parameter, the syntax of the
dlmcfgmgr
utility is displayed.
# /sbin/dlmcfgmgr
KAPL10319-W usage: /sbin/dlmcfgmgr [-s]
{ -r
| -o {special-file-name ... | all}
| -i {special-file-name ... | all}
| -v [-udev]
| -u {special-file-name ... | all}
| -logfs [log-file-size]}
#
Notes (common to OSs)
„
When an LDEV is allocated to a path and then another LDEV is allocated to the
same path (host port number, bus number, target ID, and host LU number), the
HDLM device name for the new LDEV might sometimes be the same as that for
the old LDEV. For example, when an LDEV is deallocated while a host is
running, another LDEV can be allocated to the same path. In this case, if an
application preserves the settings to use that HDLM device name, a program such
as a higher-level program product of HDLM accesses that HDLM device without
recognizing that the LDEV was changed. This might result in data corruption.
Check that the HDLM device name you previously used is nowhere to be found
before deallocating the LDEV.
„
You cannot execute multiple instances of the
dlmcfgmgr
utility at the same time.
„
You cannot execute the
dlmcfgmgr
utility while the
dlmstart
utility is
executing.
„
A logical device file name of the HDLM device file that can be specified with the
-i
,
-o
, or
-u
parameter of the
dlmcfgmgr
utility can consist of up to 4,095
characters. If a name is more than 4,096 characters long, the error message
KAPL10358-E is displayed.
„
If an LU is allocated and another LU is reallocated using the same host LU
number, HDLM does not handle them as different LUs. Therefore, restart the host
whenever a configuration change is made.
„
When two or more HDLM devices are specified with the
-s
parameter, the
confirmation message is not displayed each time the processing for each HDLM