![]() |
![]() |
![]() |
![]() |
![]() |
You can mount Storage Checkpoints using the mount
command with the mount option -o ckpt=ckpt_name
.
See the mount_vxfs
(1M) manual page.
Observe the following rules when mounting Storage Checkpoints:
-o
rw
option.
-o
remount
option.
A Storage Checkpoint is mounted on a special pseudo device. This pseudo device does not exist in the system name space; the device is internally created by the system and used while the Storage Checkpoint is mounted. The pseudo device is removed after you unmount the Storage Checkpoint. A pseudo device name is formed by appending the Storage Checkpoint name to the file system device name using the colon character (:
) as the separator.
For example, if a Storage Checkpoint named may_23
belongs to the file system residing on the special device /dev/vx/dsk/fsvol/vol1
, the Storage Checkpoint pseudo device name is:
may_23
as a read-only (default) Storage Checkpoint on directory /fsvol_may_23
, type:
# mount -t vxfs -o ckpt=may_23 /dev/vx/dsk/fsvol/vol1:may_23 \
/fsvol_may_23
Note
The
vol1
file system must already be mounted before the Storage Checkpoint can be mounted.
# mount -t vxfs -o ckpt=may_23,remount,rw \
/dev/vx/dsk/fsvol/vol1:may_23 /fsvol_may_23
To mount this Storage Checkpoint automatically when the system starts up, put the following entries in the /etc/fstab
file:
To mount a Storage Checkpoint of a cluster file system, you must also use the -o
cluster
option:
# mount -t vxfs -o cluster,ckpt=may_23
\
/dev/vx/dsk/fsvol/vol1:may_23 /fsvol_may_23
You can only mount a Storage Checkpoint cluster-wide if the file system that the Storage Checkpoint belongs to is also mounted cluster-wide. Similarly, you can only mount a Storage Checkpoint locally if the file system that the Storage Checkpoint belongs to is mounted locally.
You can unmount Storage Checkpoints using the umount
command.
See the umount
(1M) manual page.
Storage Checkpoints can be unmounted by the mount point or pseudo device name:
# umount /dev/vx/dsk/fsvol/vol1:may_23
Note
You do not need to run the
fsck
utility on Storage Checkpoint pseudo devices because pseudo devices are part of the actual file system.