Veritas Storage Foundation 5.1 SP1 Advanced Features Administrator"s Guide (5900-1503, April 2011)

logging: type=REGION loglen=528 serial=0/0 mapalign=16
maplen=512 (enabled)
apprecov: seqno=0/0
recovery: mode=default
recov_id=0
device: minor=46000 bdev=212/46000 cdev=212/46000
path=/dev/vx/dsk/dgTestSol/drlvol
perms: user=root group=root mode=0600
guid: {d968de3e-1dd1-11b2-8fc1-080020d223e5}
Displaying offset and length information in units of 512 bytes
To display offset and length information in units of 512 bytes
■ Specify the -b option to the vxprint and vxdisk commands, as shown in these
examples:
# vxprint -bm
# vxdisk -b list
Specifying the -b option enables consistent output to be obtained on different
platforms. Without the -b option, the information is output in units of sectors.
The number of bytes per sector differs between platforms.
When the vxprint -bm or vxdisk -b list command is used, the output also
contains the b suffix, so that the output can be fed back to vxmake.
Default activation mode of shared disk groups
The default activation mode of shared disk groups involves a local in-kernel policy
that differs between platforms. This means that, regardless of the platform on
which the disk group was created, the importing platform will have
platform-specific behavior with respect to activation of shared disk groups.
Specifically, with the exception of HP-UX, importing a shared disk group results
in the volumes being active and enabled for shared-write. In the case of HP-UX,
the shared volumes will be inactive and require other actions to activate them for
shared-write operations.
Additional considerations when importing CDS disk groups
Before you attempt to use CDS to move disk groups between different operating
systems, and if the configuration of the disks has changed since the target system
was last rebooted, you should consider the following points
Migrating data between platforms
Maintaining your system
484