Veritas File System 5.1 SP1 Administrator"s Guide (5900-1499, April 2011)

instance of the message to guarantee that the sequence of events is known when
analyzing file system problems.
Each message is also written to an internal kernel buffer that you can view in the
file /var/adm/syslog/syslog.log.
In some cases, additional data is written to the kernel buffer. For example, if an
inode is marked bad, the contents of the bad inode are written. When an error
message is displayed on the console, you can use the unique message ID to find
the message in /var/adm/syslog/syslog.log and obtain the additional
information.
Kernel messages
Some commonly encountered kernel messages are described on the following
table:
Table B-1
Kernel messages
Message and DefinitionMessage Number
NOTICE: msgcnt x: mesg 001: V-2-1: vx_nospace - mount_point file
system full (n block extent)
■ Description
The file system is out of space.
Often, there is plenty of space and one runaway process used up
all the remaining free space. In other cases, the available free space
becomes fragmented and unusable for some files.
■ Action
Monitor the free space in the file system and prevent it from
becoming full. If a runaway process has used up all the space, stop
that process, find the files created by the process, and remove
them. If the file system is out of space, remove files, defragment,
or expand the file system.
To remove files, use the find command to locate the files that are
to be removed. To get the most space with the least amount of
work, remove large files or file trees that are no longer needed. To
defragment or expand the file system, use the fsadm command.
See the fsadm_vxfs(1M) manual page.
001
147Diagnostic messages
Kernel messages