VERITAS File SystemÖ 3.5 (HP OnlineJFS/JFS3.5) AdministratorÆs Guide (December 2002)

Chapter 5

Storage Checkpoints

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. Usually these operations do not fail because of insufficient space on the file

system, but these operations on a file system containing Storage Checkpoints can cause a data block copy

which, in turn, may require extent allocation. 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 (see rm (1)), from failing under an out-of-space (ENOSPC)

condition.

The kernel will follow these policies when automatically removing Storage Checkpoints:

Step 1. Remove as few Storage Checkpoints as possible to complete the operation.

Step 2. Never select a non-removable Storage Checkpoint.

Step 3. Select a nodata Storage Checkpoint only when data Storage Checkpoints no longer exist.

Step 4. Remove the oldest Storage Checkpoint first.