In the following circumstances, take the actions as indicated for the relevant situation:
(1) The operation of a backup and a replication for a GDS volume by using ACM fails.
Explanation
As the by-id file (a symbolic link file crated in the /dev/disk/by-id directory) managed by the udev function of Linux is sometimes re-created, it may not exist temporarily. In this case, if you perform a backup or a replication by using ACM, either of the following messages is output and the operation fails:
swst0642 Mirror volume cannot be set up in Backup Volume.
swst0740 The advanced copy function cannot be used. Error=2 (invalid logical volume name.)
swsrp0740 The advanced copy function cannot be used. Error=2 (invalid logical volume name.)
swsrp3682 The device information could not be acquired. Device Name=<DeviceName>, Error=2560, Detail=STX error occurred.[2 (invalid logical volume name.)]
Resolution
See the GDS log file (/var/opt/FJSVsdx/msglog/sdxbyid_link.log). Then, check if the message (INFO: by-id exists) was output to indicate the existence of the by-id file after the operation failed. After that, execute the operation again.
Example
The backup fails
# /opt/FJSVswsts/bin/swstbackup /dev/sfdsk/Class_name/dsk/Volume_name:/dev/disk/by-id/XXXX -Xdevmap Device-Map-File swst0740 The advanced copy function cannot be used. Error=2(invalid logical volume name.) |
Extracting the creation time of the by-id file specified by Step 1
# grep "/dev/disk/by-id/XXXX" /var/opt/FJSVsdx/msglog/sdxbyid_link.log 12/12/31 23:45:00: INFO: /dev/disk/by-id/XXXX exists : 13/01/01 12:34:00: INFO: /dev/disk/by-id/XXXX exists |
Comparing the time to execute Step 1 and the time to re-create the by-id file
Check the output result of Step 2. If the last message (INFO: by-id exists) was output later than the execution of Step 1 (12:34:00 13/01/01 in the example of Step 2), execute Step 4.
Performing the backup again
# /opt/FJSVswsts/bin/swstbackup /dev/sfdsk/Class_name/dsk/Volume_name:/dev/disk/by-id/XXXX -Xdevmap Device-Map-File /dev/sfdsk/Class_name/dsk/Volume_name:/dev/disk/by-id/XXXX swstbackup completed |
(2) When checking the execution status of a backup or a replication for a GDS volume by using ACM, "?????" is displayed in the Status field.
Explanation
As the by-id file (a symbolic link file crated in the /dev/disk/by-id directory) managed by the udev function of Linux is sometimes re-created, it may not exist temporarily. In this case, if you check the execution status of a backup or a replication by using ACM, "?????" is displayed in the Status field.
Resolution
See the GDS log file (/var/opt/FJSVsdx/msglog/sdxbyid_link.log). Then, check if the message (INFO: by-id exists) was output to indicate the existence of the by-id file after the operation failed. After that, display the execution status again.
(3) When performing "fetching device information on a Managed Server" of ACM, a form of a device name of the SDX object is changed from a by-id name to a by-path name or a compatible device name (sdX).
Explanation
As the by-id file (a symbolic link file crated in the /dev/disk/by-id directory) managed by the udev function of Linux is sometimes re-created, it may not exist temporarily. In this case, if you perform "fetching device information on a Managed Server" by the Web Console of ACM or stgxfwcmsetdev (device information collection / reflection command), a form of a device name of the SDX object is changed from a by-id name to a by-path name or a compatible device name (sdX).
A form of a device name in the normal state
/dev/sfdsk/Class_name/dsk/Volume_name:/dev/disk/by-id/XXXX
A form of a device name when a phenomenon occurs
/dev/sfdsk/Class_name/dsk/Volume_name:/dev/disk/by-path/XXXX
Or
/dev/sfdsk/Class_name/dsk/Volume_name:sdX
Resolution
See the GDS log file (/var/opt/FJSVsdx/msglog/sdxbyid_link.log). Then, check if the message (INFO: by-id exists) was output to indicate the existence of the by-id file after the operation failed. After that, perform the "fetching device information on a Managed Server" again.
