From Wiki-UX.info

Wiki-UX / File Systems / JFS kernel Messages
Jump to: navigation, search

JFS kernel Messages

Abstract

This article contains a listing of diagnose error messages generated by the JFS File System kernel. Each message is accompanied by an explanation and a suggestion on how to handle or correct the underlying problem. Most messages can appear in one of two forms.

The first form applies to the file system in general. The second form is specific to the structural fileset within the file system.

Messages of the second form contain the string (structural) to indicate that they occurred in the structural fileset.

Contents


File System Response to Problems

When the file system encounters problems, it responds in one of three ways:

  1. Mark an inode bad
  2. Disable transactions
  3. Disable the file system

Marking an Inode Bad

Inodes can be marked bad if an inode update or a directory-block update fails. In these types of failures, the file system doesn't know what information is on the disk, and considers all the information that it finds to be invalid. After an inode is marked bad, the kernel still permits access to the file name, but any attempt to access the data in the file or change the inode fails.

Disabling Transactions

If the file system detects an error while writing the intent log, it disables transactions. After transactions are disabled, the files in the file system can still be read or written, but no block or inode frees or allocations, structural changes, directory entry changes, or other changes to metadata are allowed.

Disabling the File System

If an error occurs that compromises the integrity of the file system, VxFS disables itself. If the intent log fails or an inode-list error occurs, the super-block is ordinarily updated (setting the VX_FULLFSCK flag) so that the next fsck does a full structural check. If this super-block update fails, any further changes to the file system can cause inconsistencies that are undetectable by the intent log replay.

To avoid this situation, the file system disables itself.


Recovering a Disabled File System

When the file system is disabled, no data can be written to the disk.

Although some minor file system operation still work, most simply return EIO. The only thing that can be done when the file system is disabled is to do a umount and run a full fsck.

Although a log replay may produce a clean file system, do a full structural check to be safe. To do a full structural check, enter:

# fsck -F vxfs -o full, nolog /dev/vg05/rlvol8

The file system usually becomes disabled because of disk errors. Disk failures that disabled a file system should be fixed as quickly as possible (see fsck_vxfs(1M)).

Kernel Messages

This section lists the VxFS kernel error messages in numerical order.

The Explanation sub-section for each message describes the problem, the Action sub-section suggests possible solutions.

Global Message IDs

Each time a VxFS kernel message is displayed on the system console, it is displayed along with a monatomically increasing message ID, shown in the msgcnt field. This ID guarantees that the sequence of events is known in order to help analyze file system problems.

Each message is also written to an internal kernel buffer and can be viewed in the file /var/adm/messages.

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 is written. When an error message is displayed on the console, you can use the unique message ID to find the message in /var/adm/messages and obtain the additional information.

Message: 001

NOTICE: msgcnt x: vxfs: mesg 001: vx_nospace - mount_point file system
full (n block extent)
 
Explanation
 
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 fsadm (see the fsadm(1M)
manual page).

Message: 002

WARNING: msgcnt x: vxfs: mesg 002:
 
vx_snap_strategy - mount_point file system write attempt to read-only
file system
 
WARNING: msgcnt x: vxfs: mesg 002: vx_snap_copyblk - mount_point file
system write attempt to read-only file system
 
Explanation
 
The kernel tried to write to a read-only file system. This is an
unlikely problem, but if it occurs, the file system is disabled.
 
Action
 
The file system was not written, so no action is required. Report this
as a bug to your customer support organization.

Message: 003, 004, 005

WARNING: msgcnt x: vxfs: mesg 003: vx_mapbad - mount_point
file system free extent bitmap in au aun marked bad
 
WARNING: msgcnt x: vxfs: mesg 004: vx_mapbad - mount_point file system
free inode bitmap in au aun marked bad
 
WARNING: msgcnt x: vxfs: mesg 005: vx_mapbad - mount_point file system
inode extended operation bitmap in au aun marked bad
 
Explanation
 
If there is an I/O failure while writing a bitmap, the map is marked
bad. The kernel considers the maps to be invalid, so does not do any
more resource allocation from maps. This situation can cause the file
system to report "out of space" or "out of inode" error messages even
though df may report an adequate amount of free space.  This error may
also occur due to bitmap inconsistencies. If a bitmap fails a
consistency check, or blocks are freed that are already free in the
bitmap, the file system has been corrupted. This may have occurred
because a user or process wrote directly to the device or used fsdb to
change the file system.  The VX_FULLFSCK flag is set. If the map that
failed was a free extent bitmap, and the VX_FULLFSCK flag can't be set,
then the file system is disabled.
 
Action
 
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk. If the problem is not related to an I/O failure, find
out how the disk became corrupted. If no user or process was writing to
the device, report the problem to your customer support organization.
Unmount the file system and use fsck to run a full structural check.

Message: 006, 007

WARNING: msgcnt x: vxfs: mesg 006: vx_sumupd -
mount_point file system summary update in au aun failed
 
WARNING: msgcnt x: vxfs: mesg 007: vx_sumupd - mount_point file system
summary update in inode au iaun failed
 
Explanation
 
An I/O error occurred while writing the allocation unit or inode
allocation unit bitmap summary to disk. This sets the VX_FULLFSCK flag
on the file system. If the VX_FULLFSCK flag can't be set, the file
system is disabled.
 
Action
 
Check the console log for I/O errors. If the problem was caused by a
disk failure, replace the disk before the file system is mounted for
write access, and use fsck to run a full structural check.

Message: 008, 009

WARNING: msgcnt x: vxfs: mesg 008: vx_direrr - mount_point file system
inode inumber block blkno error errno
 
WARNING: msgcnt x: vxfs: mesg 009: vx_direrr - mount_point file system
inode inumber immediate directory error errno
 
Explanation
 
A directory operation failed in an unexpected manner. The mount point,
inode, and block number identify the failing directory. If the inode is
an immediate directory, the directory entries are stored in the inode,
so no block number is reported. If the error is ENOENT or ENOTDIR, an
inconsistency was detected in the directory block. This inconsistency
could be a bad free count, a corrupted hash chain, or any similar
directory structure error. If the error is EIO or ENXIO, an I/O failure
occurred while reading or writing the disk block.  The VX_FULLFSCK flag
is set in the super-block so that fsck will do a full structural check
the next time it is run.
 
Action
 
Check the console log for I/O errors. If the problem was caused by a
disk failure, replace the disk before the file system is mounted for
write access. Unmount the file system and use fsck to run a full
structural check.

Message: 01

WARNING: msgcnt x: vxfs: mesg 010: vx_ialloc - mount_point file system
inode inumber not free
 
Explanation
 
When the kernel allocates an inode from the free inode bitmap, it
checks the mode and link count of the inode. If either is non-zero, the
free inode bitmap or the inode list is corrupted.  The VX_FULLFSCK flag
is set in the super-block so that fsck will do a full structural check
the next time it is run.
 
Action
 
Unmount the file system and use fsck to run a full structural check.

Message: 011

NOTICE: msgcnt x: vxfs: mesg 011: vx_noinode - mount_point file system
out of inodes
 
Explanation
 
The file system is out of inodes.
 
Action
 
Monitor the free inodes in the file system. If the file system is
getting full, create more inodes either by removing files or by
expanding the file system. File system resizing is described in Chapter
1, "The VERITAS File System," and in the fsadm(1M) online manual page.

Message: 012

WARNING: msgcnt x: vxfs: mesg 012: vx_iget - mount_point file system
invalid inode number inumber
 
Explanation
 
When the kernel tries to read an inode, it checks the inode number
against the valid range. If the inode number is out of range, the data
structure that referenced the inode number is incorrect and must be
fixed.  The VX_FULLFSCK flag is set in the super-block so that fsck
will do a full structural check the next time it is run.
 
Action
 
Unmount the file system and use fsck to run a full structural check.

Message: 013

WARNING: msgcnt x: vxfs: mesg 013: vx_iposition - mount_point file
system inode inumber invalid inode list extent
 
Explanation
 
For a Version 2 and above disk layout, the inode list is dynamically
allocated. When the kernel tries to read an inode, it must look up the
location of the inode in the inode list file. If the kernel finds a bad
extent, the inode can't be accessed. All of the inode list extents are
validated when the file system is mounted, so if the kernel finds a bad
extent, the integrity of the inode list is questionable. This is a very
serious error.  The VX_FULLFSCK flag is set in the super-block and the
file system is disabled.
 
Action
 
Unmount the file system and use fsck to run a full structural check.

Message: 014

WARNING: msgcnt x: vxfs: mesg 014: vx_iget - inode table overflow
 
Explanation
 
All the system in-memory inodes are busy and an attempt was made to use
a new inode.
 
Action
 
Look at the processes that are running and determine which processes
are using inodes. If it appears there are runaway processes, they might
be tying up the inodes. If the system load appears normal, increase the
vxfs_ninode parameter in the kernel (see "Internal Inode Table Size" in
Chapter 5, "Performance and Tuning").

Message: 015

WARNING: msgcnt x: vxfs: mesg 015: vx_ibadinactive - mount_point file
system can't mark inode inumber bad
 
WARNING: msgcnt x: vxfs: mesg 015: vx_ilisterr - mount_point file
system can't mark inode inumber bad
 
Explanation
 
An attempt to mark an inode bad on disk, and the super-block update to
set the VX_FULLFSCK flag, failed. This indicates that a catastrophic
disk error may have occurred since both an inode list block and the
super-block had I/O failures. The file system is disabled to preserve
file system integrity.
 
Action
 
Unmount the file system and use fsck to run a full structural check.
Check the console log for I/O errors. If the disk failed, replace it
before remounting the file system.

Message: 016

WARNING: msgcnt x: vxfs: mesg 016: vx_ilisterr - mount_point file
system error reading inode inumber
 
Explanation
 
An I/O error occurred while reading the inode list. The VX_FULLFSCK
flag is set.
 
Action
 
Check the console log for I/O errors. If the problem was caused by a
disk failure, replace the disk before the file system is mounted for
write access. Unmount the file system and use fsck to run a full
structural check.

Message: 017

'''Message: 017 WARNING: msgcnt x: vxfs: mesg 017: vx_attr_getblk
- mount_point file system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_attr_iget - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_attr_indadd - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_attr_indtrunc - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_attr_iremove - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_bmap - mount_point file system
inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_bmap_indirect_ext4 - mount_point
file system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_delbuf_flush - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_dio_iovec - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_dirbread - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_dircreate - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_dirlook - mount_point file system
inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_doextop_iau - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_doextop_now - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_do_getpage - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_enter_ext4 - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_exttrunc - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_get_alloc - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_ilisterr - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_ilock - mount_point file system
inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_indtrunc - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_iread - mount_point file system
inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_iremove - mount_point file system
inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_iremove_attr - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_logwrite_flush - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_oltmount_iget - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_overlay_bmap - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_readnomap - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_reorg_trunc - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_stablestore - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_tranitimes - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_trunc - mount_point file system
inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_write_alloc2 - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_write_default - mount_point file
system inode inumber marked bad
 
WARNING: msgcnt x: vxfs: mesg 017: vx_zero_alloc - mount_point file
system inode inumber marked bad
 
Explanation
 
When inode information is no longer dependable, the kernel marks it bad
on disk. The most common reason for marking an inode bad is a disk I/O
failure. If there is an I/O failure in the inode list, on a directory
block, or an indirect address extent, the integrity of the data in the
inode, or the data the kernel tried to write to the inode list, is
questionable. In these cases, the disk driver prints an error message
and one or more inodes are marked bad.  The kernel also marks an inode
bad if it finds a bad extent address, invalid inode fields, or
corruption in directory data blocks during a validation check. A
validation check failure indicates the file system has been corrupted.
This usually occurs because a user or process has written directly to
the device or used fsdb to change the file system.  The VX_FULLFSCK
flag is set in the super-block so fsck will do a full structural check
the next time it is run.
 
Action
 
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk. If the problem is not related to an I/O failure, find
out how the disk became corrupted. If no user or process is writing to
the device, report the problem to your customer support organization.
In either case, unmount the file system and use fsck to run a full
structural check.

Message: 018

WARNING: msgcnt x: vxfs: mesg 018: vx_idelxwri_done - <mount_point> file system
inode <inumber> had a write error at offset <off>
 
Explanation
 
This message prints when the file system encounters an error while
flushing non-synchronous extending write data.  Since the data for the
file couldn't be written, the file probably contains stale data. If
the file system was mounted with the blkclear mount option, then the
VX_AF_NOGROW flag is set on the file.  When this flag is set, further
attempts to extend the file fail.  The flag is cleared when the file is truncated.
 
Action
 
Check the console log for I/O errors.  If the problem was caused by a disk failure,
then the disk should be fixed as soon as possible. If the disk has failed, it
should be repaired before the file system is mounted for write access. Make sure
the fsck program does a full structural check at the next administrative period.
 
The ff utility should be used to determine the name of the file that failed. The
contents of the file should be checked, and if necessary restored from backup or recreated.

Message: 019

WARNING: msgcnt x: vxfs: mesg 019: vx_log_add - mount_point file system
log overflow
 
Explanation
 
Log ID overflow. When the log ID reaches VX_MAXLOGID (approximately one
billion by default), a flag is set so the file system resets the log ID
at the next opportunity. If the log ID has not been reset, when the log
ID reaches VX_DISLOGID (approximately VX_MAXLOGID plus 500 million by
default), the file system is disabled. Since a log reset will occur at
the next 60 second sync interval, this should never happen.
 
Action
 
Unmount the file system and use fsck to run a full structural check.

Message: 020

WARNING: msgcnt x: vxfs: mesg 020: vx_logerr - mount_point file system
log error errno
 
Explanation
 
Intent log failed. The kernel will try to set the VX_FULLFSCK and
VX_LOGBAD flags in the super-block to prevent running a log replay. If
the super-block can't be updated, the file system is disabled.
 
Action
 
Unmount the file system and use fsck to run a full structural check.
Check the console log for I/O errors. If the disk failed, replace it
before remounting the file system.

Message: 021

WARNING: msgcnt x: vxfs: mesg 021: vx_mountsetup - mount_point file system
validation failure
 
Explanation
 
When a VERITAS File System is mounted, the structure is read from disk.
If the file system is marked clean, the structure is correct and the
first block of the intent log is cleared.  If there is any I/O problem
or the structure is inconsistent, the kernel sets the VX_FULLFSCK flag
and the mount fails.  If the error isn't related to an I/O failure,
this may have occurred because a user or process has written directly
to the device or used fsdb to change the file system.
 
Action
 
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk. If the problem is not related to an I/O failure, find
out how the disk became corrupted. If no user or process is writing to
the device, report the problem to your customer support organization.
In either case, unmount the file system and use fsck to run a full
structural check.

Message: 022

WARNING: msgcnt x: vxfs: mesg 022: vx_mountroot - root file system
remount failed
 
Explanation
 
The remount of the root file system failed. The system will not be
usable if the root file system can't be remounted for read/write
access.  When a VERITAS root file system is first mounted, it is
mounted for read-only access. After fsck is run, the file system is
remounted for read/write access. The remount fails if fsck completed a
resize operation or modified a file that was opened before the fsck was
run.  It also fails if an I/O error occurred during the remount.
Usually, the system halts or reboots automatically.
 
Action
 
Reboot the system. The system either remounts the root cleanly or runs
a full structural fsck and remounts cleanly. If the remount succeeds,
no further action is necessary.  Check the console log for I/O errors.
If the disk has failed, replace it before the file system is mounted
for write access.  If the system won't come up and a full structural
fsck hasn't been run, reboot the system on a backup root and manually
run a full structural fsck. If the problem persists after the full
structural fsck and there are no I/O errors, contact your customer
support organization.

Message: 023

WARNING: msgcnt x: vxfs: mesg 023: vx_unmountroot - root file system is
busy and can't be unmounted cleanly
 
Explanation
 
There were active files in the file system and they caused the unmount
to fail.  When the system is halted, the root file system is unmounted.
This happens occasionally when a process is hung and it can't be killed
before unmounting the root.
 
Action
 
fsck will run when the system is rebooted. It should clean up the file
system. No other action is necessary.  If the problem occurs every time
the system is halted, determine the cause and contact your customer
support organization.

Message: 024

WARNING: msgcnt x: vxfs: mesg 024: vx_cutwait - mount_point file system
current usage table update error
 
Explanation
 
Update to the current usage table (CUT) failed.  For a Version 2 disk
layout, the CUT contains a fileset version number and total number of
blocks used by each fileset.  The VX_FULLFSCK flag is set in the
super-block. If the super-block can't be written, the file system is
disabled.
 
Action
 
Unmount the file system and use fsck to run a full structural check.

Message: 025

WARNING: msgcnt x: vxfs: mesg 025: vx_wsuper - mount_point file system
superblock update failed
 
Explanation
 
An I/O error occurred while writing the super-block during a resize
operation. The file system is disabled.
 
Action
 
Unmount the file system and use fsck to run a full structural check.
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk before the file system is mounted for write access.

Message: 026

WARNING: msgcnt x: vxfs: mesg 026: vx_snap_copyblk - mount_point
primary file system read error
 
Explanation
 
Snapshot file system error.  When the primary file system is written,
copies of the original data must be written to the snapshot file
system. If a read error occurs on a primary file system during the
copy, any snapshot file system that doesn't already have a copy of the
data is out of date and must be disabled.
 
Action
 
An error message for the primary file system prints. Resolve the error
on the primary file system and rerun any backups or other applications
that were using the snapshot that failed when the error occurred.

Message: 027

WARNING: msgcnt x: vxfs: mesg 027: vx_snap_bpcopy - mount_point
snapshot file system write error
 
Explanation
 
A write to the snapshot file system failed.
As the primary file system is updated, copies of the original data are
read from the primary file system and written to the snapshot file
system. If one of these writes fails, the snapshot file system is
disabled.
 
Action
 
Check the console log for I/O errors. If the disk has failed, replace
it. Resolve the error on the disk and rerun any backups or other
applications that were using the snapshot that failed when the error
occurred.

Message: 028

WARNING: msgcnt x: vxfs: mesg 028: vx_snap_alloc - mount_point snapshot
file system out of space
 
Explanation
 
The snapshot file system ran out of space to store changes.
During a snapshot backup, as the primary file system is modified, the
original data is copied to the snapshot file system. This error can
occur if the snapshot file system is left mounted by mistake, if the
snapshot file system was given too little disk space, or the primary
file system had an unexpected burst of activity. The snapshot file
system is disabled.
 
Action
 
Make sure the snapshot file system was given the correct amount of
space. If it was, determine the activity level on the primary file
system. If the primary file system was unusually busy, rerun the
backup. If the primary file system is no busier than normal, move the
backup to a time when the primary file system is relatively idle or
increase the amount of disk space allocated to the snapshot file
system.  Rerun any backups that failed when the error occurred.

Message: 029, 03

WARNING: msgcnt x: vxfs: mesg 029: vx_snap_getbp - mount_point snapshot
file system block map write error
 
WARNING: msgcnt x: vxfs: mesg 030: vx_snap_getbp - mount_point snapshot
file system block map read error
 
Explanation
 
During a snapshot backup, each snapshot file system maintains a block
map on disk. The block map tells the snapshot file system where data
from the primary file system is stored in the snapshot file system. If
an I/O operation to the block map fails, the snapshot file system is
disabled.
 
Action
 
Check the console log for I/O errors. If the disk has failed, replace
it. Resolve the error on the disk and rerun any backups that failed
when the error occurred.

Message: 031

WARNING: msgcnt x: vxfs: mesg 031: vx_disable - mount_point file system
disabled
 
Explanation
 
File system disabled, preceded by a message that specifies the reason.
This usually indicates a serious disk problem.
 
Action
 
Unmount the file system and use fsck to run a full structural check. If
the problem is a disk failure, replace the disk before the file system
is mounted for write access.

Message: 032

WARNING: msgcnt x: vxfs: mesg 032: vx_disable - mount_point snapshot
file system disabled
 
Explanation
 
Snapshot file system disabled, preceded by a message that specifies the
reason.
 
Action
 
Unmount the snapshot file system, correct the problem specified by the
message, and rerun any backups that failed due to the error.

Message: 033

WARNING: msgcnt x: vxfs: mesg 033: vx_check_badblock - mount_point file
system had an I/O error, setting VX_FULLFSCK
 
Explanation
 
When the disk driver encounters an I/O error, it sets a flag in the
super-block structure. If the flag is set, the kernel will set the
VX_FULLFSCK flag as a precautionary measure. Since no other error has
set the VX_FULLFSCK flag, the failure probably occurred on a data
block.
 
Action
 
Unmount the file system and use fsck to run a full structural check.
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk before the file system is mounted for write access.

Message: 034

WARNING: msgcnt x: vxfs: mesg 034: vx_resetlog - mount_point file
system can't reset log
 
Explanation
 
The kernel encountered an error while resetting the log ID on the file
system. This happens only if the super-block update or log write
encountered a device failure. The file system is disabled to preserve
its integrity.
 
Action
 
Unmount the file system and use fsck to run a full structural check.
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk before the file system is mounted for write access.

Message: 035

WARNING: msgcnt x: vxfs: mesg 035: vx_inactive - mount_point file
system inactive of locked inode inumber
 
Explanation
 
VOP_INACTIVE was called for an inode while the inode was being used.
This should never happen, but if it does, the file system is disabled.
 
Action
 
Unmount the file system and use fsck to run a full structural check.
Report as a bug to your customer support organization.

Message: 036

WARNING: msgcnt x: vxfs: mesg 036: vx_lctbad - mount_point file system
link count table lctnumber bad
 
Explanation
 
Update to the link count table (LCT) failed.  For a Version 2 and above
disk layout, the LCT contains the link count for all the structural
inodes. The VX_FULLFSCK flag is set in the super-block. If the
super-block can't be written, the file system is disabled.
 
Action
 
Unmount the file system and use fsck to run a full structural check.

Message: 038

WARNING: msgcnt x: vxfs: mesg 038: vx_dqbad - mount_point file system
quota file update error for id id.
 
Explanation
 
An update to the user quotas file failed for the user ID.
The quotas file keeps track of the total number of blocks and inodes
used by each user, and also contains soft and hard limits for each user
ID. The VX_FULLFSCK flag is set in the super-block. If the super-block
cannot be written, the file system is disabled.
 
Action
 
Unmount the file system and use fsck to run a full structural check.
Check the console log for I/O errors. If the disk has a hardware
failure, it should be repaired before the file system is mounted for
write access.

Message: 039

WARNING: msgcnt x: vxfs: mesg 039: vx_dqget - mount_point file system
user quota file can't read quota for id id
 
Explanation
 
A read of the user quotas file failed for the uid.
The quotas file keeps track of the total number of blocks and inodes
used by each user, and contains soft and hard limits for each user ID.
The VX_FULLFSCK flag is set in the super-block. If the super-block
cannot be written, the file system is disabled.
 
Action
 
Unmount the file system and use fsck to run a full structural check.
Check the console log for I/O errors. If the disk has a hardware
failure, it should be repaired before the file system is mounted for
write access.

Message: 04

WARNING: msgcnt x: vxfs: mesg 040: vx_bsdquotaupdate - mount_point file
system user id disk limit reached.
 
Explanation
 
The hard limit on blocks was reached. Further attempts to allocate
blocks for files owned by the user will fail.
 
Action
 
Remove some files to free up space.

Message: 041

WARNING: msgcnt x: vxfs: mesg 041: vx_bsdquotaupdate - mount_point file
system user id disk quota exceeded too long
 
Explanation
 
The soft limit on blocks was exceeded continuously for longer than the
soft quota time limit. Further attempts to allocate blocks for files
will fail.
 
Action
 
Remove some files to free up space.

Message: 042

WARNING: msgcnt x: vxfs: mesg 042: vx_bsdquotaupdate - mount_point file
system user id disk quota exceeded.
 
Explanation
 
The soft limit on blocks is exceeded. The soft limit can be exceeded
for a certain amount of time before allocations begin to fail. Once the
soft quota time limit has expired, further attempts to allocate blocks
for files will fail.
 
Action
 
Remove some files to free up space.

Message: 043

WARNING: msgcnt x: vxfs: mesg 043: vx_bsdiquotaupdate - mount_point
file system user id inode limit reached.
 
Explanation
 
The hard limit on inodes was exceeded. Further attempts to create files
owned by the user will fail.
 
Action
 
Remove some files to free inodes.

Message: 044

WARNING: msgcnt x: vxfs: mesg 044: vx_bsdiquotaupdate - mount_point
file system user id inode quota exceeded too long
 
Explanation
 
The soft limit on inodes has been exceeded continuously for longer than
the soft quota time limit. Further attempts to create files owned by
the user will fail.
 
Action
 
Remove some files to free inodes.

Message: 045

WARNING: msgcnt x: vxfs: mesg 045: vx_bsdiquotaupdate - warning:
mount_point file system user id inode quota exceeded
 
Explanation
 
The soft limit on inodes was exceeded. The soft limit can be exceeded
for a certain amount of time before attempts to create new files begin
to fail. Once the time limit has expired, further attempts to create
files owned by the user will fail.
 
Action
 
Remove some files to free inodes.

Message: 046, 047

WARNING: msgcnt x: vxfs: mesg 046: vx_dqread - warning: mount_point
file system external user quota file read failed
 
WARNING: msgcnt x: vxfs: mesg 047: vx_dqwrite - warning: mount_point
file system external user quota file write failed.
 
Explanation
 
To maintain reliable usage counts, VxFS maintains the user quotas file
as a structural file in the structural fileset. These files are updated
as part of the transactions that allocate and free blocks and inodes.
For compatibility with the quota administration utilities, VxFS also
supports the standard user visible quota files.  When quotas are turned
off, synced, or new limits are added, VxFS tries to update the external
quota files. When quotas are enabled, VxFS tries to read the quota
limits from the external quotas file. If these reads or writes fail,
the external quotas file is out of date.
 
Action
 
Determine the reason for the failure on the external quotas file and
correct it. Recreate the quotas file.

Message: 048

WARNING: msgcnt x: vxfs: mesg 048: vx_mapbad - mount_point file system
extent allocation unit state bitmap number number marked bad
 
Explanation
 
If there is an I/O failure while writing a bitmap, the map is marked
bad. The kernel considers the maps to be invalid, so does not do any
more resource allocation from maps. This situation can cause the file
system to report "out of space" or "out of inode" error messages even
though df may report an adequate amount of free space.  This error may
also occur due to bitmap inconsistencies. If a bitmap fails a
consistency check, or blocks are freed that are already free in the
bitmap, the file system has been corrupted. This may have occurred
because a user or process wrote directly to the device or used fsdb to
change the file system.  The VX_FULLFSCK flag is set. If the
VX_FULLFSCK flag can't be set, the file system is disabled.
 
Action
 
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk. If the problem is not related to an I/O failure, find
out how the disk became corrupted. If no user or process was writing to
the device, report the problem to your customer support organization.
Unmount the file system and use fsck to run a full structural check.

Message: 049

WARNING: msgcnt x: vxfs: mesg 049: vx_esum_bad - mount_point file
system extent allocation unit summary number number marked bad
 
Explanation
 
An I/O error occurred reading or writing an extent allocation unit summary.
The VX_FULLFSCK flag is set. If the VX_FULLFSCK flag can't be set, the
file system is disabled.
 
Action
 
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk. If the problem is not related to an I/O failure, find
out how the disk became corrupted. If no user or process was writing to
the device, report the problem to your customer support organization.
Unmount the file system and use fsck to run a full structural check.

Message: 05

WARNING: msgcnt x: vxfs: mesg 050: vx_isum_bad - mount_point file
system inode allocation unit summary number number marked bad
 
Explanation
 
An I/O error occurred reading or writing an inode allocation unit
summary.  The VX_FULLFSCK flag is set. If the VX_FULLFSCK flag can't be
set, the file system is disabled.
 
Action
 
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk. If the problem is not related to an I/O failure, find
out how the disk became corrupted. If no user or process was writing to
the device, report the problem to your customer support organization.
Unmount the file system and use fsck to run a full structural check.

Message: 051

WARNING: msgcnt x: vxfs: mesg 051: vx_snap_getbitbp - mount_point
snapshot file system bitmap write error
 
Explanation
 
An I/O error occurred while writing to the snapshot file system bitmap.
There is no problem with the snapped file system, but the snapshot file
system is disabled.
 
Action
 
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk. If the problem is not related to an I/O failure, find
out how the disk became corrupted. If no user or process was writing to
the device, report the problem to your customer support organization.
Restart the snapshot on an error free disk partition. Rerun any backups
that failed when the error occurred.

Message: 052

WARNING: msgcnt x: vxfs: mesg 052: vx_snap_getbitbp - mount_point
snapshot file system bitmap read error
 
Explanation
 
An I/O error occurred while reading the snapshot file system bitmap.
There is no problem with snapped file system, but the snapshot file
system is disabled.
 
Action
 
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk. If the problem is not related to an I/O failure, find
out how the disk became corrupted. If no user or process was writing to
the device, report the problem to your customer support organization.
Restart the snapshot on an error free disk partition. Rerun any backups
that failed when the error occurred.

Message: 053

WARNING: msgcnt x: vxfs: mesg 053: vx_resize - mount_point file system
remount failed
 
Explanation
 
During a file system resize, the remount to the new size failed. The
VX_FULLFSCK flag is set and the file system is disabled.  Action
 
Unmount the file system and use fsck to run a full structural check.
After the check, the file system shows the new size.

Message: 054

NOTICE: msgcnt x: vxfs: mesg 054: vx_attr_creatop - invalid disposition
returned by attribute driver
 
Explanation
 
A registered extended attribute intervention routine returned an
invalid return code to the VxFS driver during extended attribute
inheritance.
 
Action
 
Determine which vendor supplied the registered extended attribute
intervention routine and contact their customer support organization.

Message: 055

WARNING: msgcnt x: vxfs: mesg 055: vx_metaioerr - file system meta data
error
 
Explanation
 
A read or a write error occurred while accessing file system metadata.
The full fsck flag on the file system was set. The message specifies
whether the disk I/O that failed was a read or a write.  File system
metadata includes inodes, directory blocks, and the file system log. If
the error was a write error, it is likely that some data was lost. This
message should be accompanied by another file system message describing
the particular file system metadata affected, as well as a message from
the disk driver containing information about the disk I/O error.
 
Action
 
Resolve the condition causing the disk error. If the error was the
result of a temporary condition (such as accidentally turning off a
disk or a loose cable), correct the condition. Check for loose cables,
etc. Unmount the file system and use fsck to run a full structural
check (possibly with loss of data).  In case of an actual disk error,
if it was a read error and the disk driver remaps bad sectors on write,
it may be fixed when fsck is run since fsck is likely to rewrite the
sector with the read error. In other cases, you replace or reformat the
disk drive and restore the file system from backups. Consult the
documentation specific to your system for information on how to recover
from disk errors. The disk driver should have printed a message that
may provide more information.

Message: 056

WARNING: msgcnt x: vxfs: mesg 056: vx_dataioerr - file system file data
error
 
Explanation
 
A read or a write error occurred while accessing file data. The message
specifies whether the disk I/O that failed was a read or a write. File
data includes data currently in files and free blocks. If the message
is printed because of a read or write error to a file, another message
that includes the inode number of the file will print. The message may
be printed as the result of a read or write error to a free block,
since some operations allocate an extent and immediately perform I/O to
it. If the I/O fails, the extent is freed and the operation fails. The
message should be accompanied by a message from the disk driver
containing information about the disk I/O error.
 
Action
 
Resolve the condition causing the disk error. If the error was the
result of a temporary condition (such as accidentally turning off a
disk or a loose cable), correct the condition. Check for loose cables,
etc. If any file data was lost, restore the files from backups.
Determine the file names from the inode number (see the ncheck(1M)
manual page for more information.) If an actual disk error occurred,
make a backup of the file system, replace or reformat the disk drive,
and restore the file system from the backup. Consult the documentation
specific to your system for information on how to recover from disk
errors. The disk driver should have printed a message that may provide
more information.

Message: 057

WARNING: msgcnt x: vxfs: mesg 057: vx_fset_markbad - mount_point file
system mount_point fileset (index number) marked bad
 
Explanation
 
An error occurred while reading or writing a fileset structure.
VX_FULLFSCK flag is set. If the VX_FULLFSCK flag can't be set, the file
system is disabled.  Action
 
Unmount the file system and use fsck to run a full structural check.

Message: 058

WARNING: msgcnt x: vxfs: mesg 058: vx_ivalidate - mount_point file
system inode number version number exceeds fileset's
 
Explanation
 
During inode validation, a discrepancy was found between the inode
version number and the fileset version number. The inode may be marked
bad, or the fileset version number may be changed, depending on the
ratio of the mismatched version numbers.  VX_FULLFSCK flag is set. If
the VX_FULLFSCK flag can't be set, the file system is disabled.
 
Action
 
Check the console log for I/O errors. If the problem is a disk failure,
replace the disk. If the problem is not related to an I/O failure, find
out how the disk became corrupted. If no user or process is writing to
the device, report the problem to your customer support organization.
In either case, unmount the file system and use fsck to run a full
structural check.

Reference

This page was last modified on 17 July 2010, at 02:17. This page has been accessed 1,718 times.