A.2.31 Upgrading Instructions

PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Linux)

Contents

Appendix A General Notes

> A.2 Important Points

A.2.31 Upgrading Instructions

Device Special File Incompatibility (GDS)

The following incompatibility exists between PRIMECLUSTER GDS 4.1A30 or before and 4.1A40.

PRIMECLUSTER GDS 4.1A30 or before

Device special files for volumes and temporarily detached slices are either the block device type or the character (raw) type.

Device special files for volumes

Block          : /dev/sfdsk/Class Name/dsk/Volume Name
Character (raw): /dev/sfdsk/Class Name/rdsk/Volume Name

Device special files for temporarily detached slices

Block          : /dev/sfdsk/Class Name/dsk/Disk Name.Volume Name
Character (raw): /dev/sfdsk/Class Name/rdsk/Disk Name.Volume Name

PRIMECLUSTER GDS 4.1A40

Device special files for volumes and temporarily detached slices are all block device special files.
- Device special files for volumes
```
Block         : /dev/sfdsk/Class Name/dsk/Volume Name
```
- Device special files for temporarily detached slices
```
Block         : /dev/sfdsk/Class Name/dsk/Disk Name.Volume Name
```
To use a volume or a temporarily detached slice as a character (raw) device, bind the raw device with the raw(8) command. For details, see "Raw Device Binding."

GDS Management View Information Message Incompatibility (GDS)

Based on the device special file incompatibility, the following incompatibility exists between information messages for slice detachment completion displayed from GDS Management View.

PRIMECLUSTER GDS 4.1A30 or before

5202 The slice was detached. The following access path is available.
Access path: /dev/sfdsk/classname/rdsk/slicename
PRIMECLUSTER GDS 4.1A40

5202 The slice was detached. The following access path is available.
Access path: /dev/sfdsk/classname/dsk/slicename

Command Information Message Incompatibility (GDS)

Based on the device special file incompatibility, the incompatibilities between command information messages below exist. All message lines are displayed in GDS 4.1A30 or before, but the italic text strings (the second lines of the following messages) are not displayed in GDS 4.1A40.

INFO: volume: started volume on node node
      /dev/sfdsk/class/rdsk/volume
      /dev/sfdsk/class/dsk/volume

INFO: disk.volume: enabled slice
      /dev/sfdsk/class/rdsk/disk.volume
      /dev/sfdsk/class/dsk/disk.volume

INFO: disk.volume: started slice on node node
      /dev/sfdsk/class/rdsk/disk.volume
      /dev/sfdsk/class/dsk/disk.volume

INFO: disk.volume: current node node took over and started slice
      /dev/sfdsk/class/rdsk/disk.volume
      /dev/sfdsk/class/dsk/disk.volume

INFO: volume: started volume on node node,...
      /dev/sfdsk/class/rdsk/volume
      /dev/sfdsk/class/dsk/volume

Command Error Message Incompatibility (GDS)

The following incompatibility exists between PRIMECLUSTER GDS 4.1A30 and 4.1A40.

4.1A30	4.1A40
ERROR: group: group other than switch group exists in class	ERROR: class includes a group that cannot exist together with a switch group

sdxproxy Command's -e delay Option Incompatibility (GDS Snapshot)

The following incompatibility exists between PRIMECLUSTER GDS Snapshot 4.1A20 and 4.1A30 or later.

PRIMECLUSTER GDS Snapshot 4.1A20

Even if delay time that is out of range of 0 to 1000 in milliseconds is specified with the -e delay option of the sdxproxy command, the sdxproxy command does not result in an error and the specified delay time will be in effect.
PRIMECLUSTER GDS Snapshot 4.1A30 or later

If delay time that is out of range of 0 to 1000 in milliseconds is specified with the -e delay option of the sdxproxy command, the sdxproxy command results in an error and the following error message is output. msec indicates the delay time specified with -e delay=msec.

ERROR: msec: invalid delay value

Contents