Veritas™ File System 5.0.1 Administrator's Guide

Storage Checkpoint quotas
VxFS provides options to the fsckptadm command interface to administer Storage
Checkpoint quotas. Storage Checkpoint quotas set the following limits on the
number of blocks used by all Storage Checkpoints of a primary file set:
An absolute limit that cannot be exceeded. If a hard limit is exceeded,
all further allocations on any of the Storage Checkpoints fail, but
existing Storage Checkpoints are preserved.
hard limit
Must be lower than the hard limit. If a soft limit is exceeded, no new
Storage Checkpoints can be created. The number of blocks used must
return below the soft limit before more Storage Checkpoints can be
created. An alert and console message are generated.
soft limit
In case of a hard limit violation, various solutions are possible, enacted by
specifying or not specifying the -f option for the fsckptadm utility.
See the fsckptadm(1M) manual page.
Specifying or not specifying the -f option has the following effects:
■ If the -f option is not specified, one or many removable Storage Checkpoints
are deleted to make space for the operation to succeed. This is the default
solution.
■ If the -f option is specified, all further allocations on any of the Storage
Checkpoints fail, but existing Storage Checkpoints are preserved.
Note: Sometimes if a file is removed while it is opened by another process, the
removal process is deferred until the last close. Because the removal of a file
may trigger pushing data to a “downstream” Storage Checkpoint (that is, the
next older Storage Checkpoint), a fileset hard limit quota violation may occur.
In this scenario, the hard limit is relaxed to prevent an inode from being marked
bad. This is also true for some asynchronous inode operations.
107Storage Checkpoints
Storage Checkpoint quotas