Home > Veritas Storage Foundation™ File System Manual Pages
Table of contents
fsckpt_cntl - perform control functions and Storage Checkpoint state changes
int fsckpt_cntl(void *fshandle, char *ckptname, int op, int flags);
performs control functions and state changes on the
Storage Checkpoint specified by
allows the application
to set or clear certain Storage Checkpoint state flags.
The state flags that can
be controlled are the same flags used when creating Storage Checkpoints with
argument defines the
argument specifies the Storage Checkpoint states and policies to
be used in the case of
The following flags are defined:
Nodata Storage Checkpoints are very useful for applications trying to
retrieve data blocks changed in the file system rather than the
Storage Checkpoint itself.
By consulting the Storage Checkpoint for changed blocks,
an application can open a
file and read the blocks changed,
thus generating a data stream containing current data which has changed
since the Storage Checkpoint was created.
Converts a Storage Checkpoint to nodata. A
Storage Checkpoint is
one that does not contain actual data.
Instead, it contains a collection of markers indicating
the location of all the changed blocks.
After a Storage Checkpoint is
to nodata, the image at
the time of creation is lost.
flag is not allowed.
Conversion to nodata is asynchronous by default.
Synchronous conversion waits for all files to be
converted before returning to the caller.
The caller can request synchronous conversion by specifying the
Multiple nodata Storage Checkpoints are allowed,
operation fails with the
error if there is an older
Storage Checkpoint which is not in the
operation will succeed and
mark the Storage Checkpoint for a delayed conversion to nodata.
The Storage Checkpoint will be in
The actual conversion to nodata takes place after
the Storage Checkpoint becomes the oldest existing Storage Checkpoint
(all older Storage Checkpoints were removed),
or if older Storage Checkpoints become nodata.
Disallows mounting of Storage Checkpoints.
Removes a Storage Checkpoint to free up file system space and
allow a writer to continue without getting
Storage Checkpoints are removed based on time
of creation, with the older Storage Checkpoints being
Storage Checkpoints are removed in this
order until enough space is freed up to guarantee that
applications do not receive an
When used with the
performs a synchronous conversion.
It does not return to the caller until all of
the Storage Checkpoint files are converted to nodata.
Nodata Storage Checkpoints are lightweight in nature, so the impact
on applications and the overhead on the file system is minimal.
returns zero on success, non-zero on failure.
User does not have permission to perform the operation.
Only privileged users can create Storage Checkpoints.
The Storage Checkpoint name
already exists in the file system Storage Checkpoint name space.
The function is being used incorrectly,
or the arguments to the function could not be validated.
This may occur when an application tries to use an
that was not created by the same process.
An I/O error occurred on the device.
The Storage Checkpoint could not be loaded.
The specified Storage Checkpoint
does not exist.
The system does not have a valid license to perform the operation.
The file system is mounted as read-only;
no updates are allowed on
the file system and the Storage Checkpoint cannot be modified.
Last updated: 01 April 2006
Copyright ©2009 Symantec Corporation
All rights reserved.