User Category Permission
Technicians Disallowed
Locking a Volume
Locks a volume so that it is read-only.
vol_lock vol=VolName
Parameters:
Name Type Description Mandatory
vol Object name Name of the volume to
lock.
Y
This command locks a volume so that hosts cannot write to it.
A volume that is locked is write-protected, so that hosts can read the data stored
on it, but cannot change it. In addition, a locked volume cannot be formatted or
resized. In general, locking a volume prevents any operation (other than deletion)
that changes the volume's image.
This command succeeds when the volume's lock state is already set to the one the
user is trying to apply, while leaving it in the same lock state.
The lock states of master volumes are set to unlocked when they are created.
The lock states of snapshots are set to locked when they are created.
In addition to the lock state, snapshots also have a modification state. The
modification state is a read-only state (which cannot be changed by the user
explicitly) and it is initially set to unmodified when the snapshot is created. The first
time a snapshot lock state is set to unlocked, the modification state of the snapshot
is changed to modified, and it is never changed thereafter.
If applied on a volume that is part of an IBM Hyper-Scale Mobility relation, the
command has to be acknowledged by both source and destination volumes.
Otherwise, a completion code is returned (see below).
Example:
vol_lock vol=DBVolume
Output:
Command executed successfully.
Access Control:
User Category Permission Condition
Storage administrator Allowed N/A
Storage integration administrator Allowed N/A
52 IBM XIV Storage System User Manual
To Next Page
Loading...
Need help?
General
