Veritas™ File System 5.0.1 Administrator's Guide

4
Remove the older and old Storage Checkpoints.
# fsckptadm remove older /mnt0
# fsckptadm remove old /mnt0
# fsckptadm list /mnt0
/mnt0
latest:
ctime = Mon 26 Jul 12:06:42 2004
mtime = Mon 26 Jul 12:06:42 2004
flags = nodata, largefiles
oldest:
ctime = Mon 26 Jul 11:56:41 2004
mtime = Mon 26 Jul 11:56:41 2004
flags = nodata, largefiles
Note: After you remove the older and old Storage Checkpoints, the latest
Storage Checkpoint is automatically converted to a nodata Storage Checkpoint
because the only remaining older Storage Checkpoint (oldest) is already a
nodata Storage Checkpoint:
Space management considerations
Several operations, such as removing or overwriting a file, can fail when a file
system containing Storage Checkpoints runs out of space. If the system cannot
allocate sufficient space, the operation will fail.
Database applications usually preallocate storage for their files and may not
expect a write operation to fail. If a file system runs out of space, the kernel
automatically removes Storage Checkpoints and attempts to complete the write
operation after sufficient space becomes available. The kernel removes Storage
Checkpoints to prevent commands, such as rm. from failing under an out-of-space
(ENOSPC) condition.
See the rm(1M) manual page.
When the kernel automatically removes the Storage Checkpoints, it applies the
following policies:
■ Remove as few Storage Checkpoints as possible to complete the operation.
■ Never select a non-removable Storage Checkpoint.
■ Select a nodata Storage Checkpoint only when data Storage Checkpoints no
longer exist.
101Storage Checkpoints
Space management considerations