Limitations For Tru64 Unix; Example Of The Scu Command To Show Persistent Reserves - IBM TotalStorage DS6000 Attachment Manual

Figure 22. Example of the scu command to show persistent reserves
After removing the persistent reserve from a storage unit volume, you can use it as
a target LUN for FlashCopy or Remote Mirror and Copy.

Limitations for Tru64 UNIX

The following is a list of limitations for Tru64 UNIX for fibre-channel connections:
Boot Volumes
UFS file system
AdvFS file system
40
DS6000 Host Systems Attachment Guide
alpha1> scu -f /dev/rdisk/dsk47c show reservations
Persistent Reservation Header:
Generation Value: 50
Additional Length: 0
Reservation Descriptors:
Alpha2> scu -f /dev/rdisk/dsk47c show reservations
Persistent Reservation Header:
Generation Value: 50
Additional Length: 0
Reservation Descriptors:
IBM does not support FlashCopy or Remote Mirror and Copy on Tru64 boot
volumes (cluster boot volumes). Do not attempt to clear persistent reserves
on these LUNs.
The data will be inconsistent if you perform a FlashCopy on a target LUN
which is online. Take the LUN offline before you perform a FlashCopy.
It is not possible to access a FlashCopy target volume on the same host as
the source because of domain/fileset advfs concepts. You must unmount
the source volume before you can access the target volume.
From the command line, type the following commands:
1. # umount /source
2. # mkdir /etc/fdmns/t_domain (target domain)
3. # ln -s /dev/disk/dsk47c dsk47c (target volume)
4. # mkdir /target
5. # mount -t advfs dsk47c
6. # source /target (source is fileset of source volume)