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:
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.
-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.
-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.