Error Message

Mar  6 05:15:10 xxxxxxxxxxvxfs: [ID 702911 kern.notice] NOTICE: msgcnt 6 mesg 001: V-2-1: vx_nospace - /dev/vx/dsk/xxxxxxx/xxxxxxx file system full (11 block extent)
 

As per VxFS design, Storage Checkpoints are not automatically removed under all file system full conditions. The Storage Checkpoints are removed automatically only under certain conditions and these conditions are relaxed in VxFS version 6.0 compared to VxFS 5.1 and below.

VxFS 5.1 and below
===============
In VxFS 5.1 and below, the design criteria dictate that automatic checkpoint removal is only triggered for filesystem operations which are not normally expected to fail with an ENOSPC error when there is no Storage Checkpoints created.   For example, logically one will not expect file removal (rm command) to fail if the filesystem is full.   So as per the VxFS 5.1 (and below) design, file removal will trigger the automatic checkpoint removal.   The same logic applies to other operations like directory removal (rmdir) and file truncation.   In VxFS 5.1 or below, creating a new file, extending an existing file will NOT trigger automatic checkpoint removal.

VxFS 6.0
========
With VxFS 6.0 the conditions for automatic checkpoint removal are relaxed.   In VxFS 6.0 automatic checkpoint removal is also triggered by file creation, directory creation (mkdir), renaming (mv), both symbolic and hard link creation and file writes that extends the file size.

Please note that even with VxFS 6.0 automatic checkpoint removal will not be triggered by the file system administrative commands like fsadm, fcladm, qiomkfile, fsckptadm. This is the same behavior as with previous VxFS versions.

If one wants to trigger the automatic checkpoint removal, please perform the relevant file system operation as described above for the corresponding VXFS versions.

Applies To

Veritas File System (VxFS)