|
< Previous | Next > |
| Product: File System Guides | |
| Manual: File System 4.1 Administrator's Guide | |
Kernel MessagesThis section lists the VxFS kernel error messages in numerical order. The Description subsection for each message describes the problem, the Action subsection suggests possible solutions. Global Message IDsWhen a VxFS kernel message displays on the system console, it is preceded by a numerical ID shown in the msgcnt field. This ID number increases with each 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.
NOTICE: msgcnt x: mesg 001: V-2-01: vx_nospace - mount_point file system full (n block extent)
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.
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_vxfs(1M) manual page).
WARNING: msgcnt x: mesg 002: V-2-02: vx_snap_strategy - mount_point file system write attempt to read-only file system
WARNING: msgcnt x: mesg 002: V-2-02: vx_snap_copyblk - mount_point file system write attempt to read-only file system
WARNING: msgcnt x: mesg 003: V-2-03: vx_mapbad - mount_point file system free extent bitmap in au aun marked bad
WARNING: msgcnt x: mesg 004: V-2-04: vx_mapbad - mount_point file system free inode bitmap in au aun marked bad
WARNING: msgcnt x: mesg 005: V-2-05: vx_mapbad - mount_point file system inode extended operation bitmap in au aun marked bad
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.
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.
WARNING: msgcnt x: mesg 006: V-2-06: vx_sumupd - mount_point file system summary update in au aun failed
WARNING: msgcnt x: mesg 007: V-2-07: vx_sumupd - mount_point file system summary update in inode au iaun failed
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.
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.
WARNING: msgcnt x: mesg 008: V-2-08: vx_direrr: function - mount_point file system dir inode dir_inumber dev/block device_ID/block dirent inode dirent_inumber error errno
WARNING: msgcnt x: mesg 009: V-2-09: vx_direrr: function - mount_point file system dir inode dir_inumber dirent inode dirent_inumber immediate directory error errno
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.
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.
WARNING: msgcnt x: mesg 010: V-2-10: vx_ialloc - mount_point file system inode inumber not free
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.
Unmount the file system and use fsck to run a full structural check.
NOTICE: msgcnt x: mesg 011: V-2-11: vx_noinode - mount_point file system out of inodes
The file system is out of inodes.
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 Online System Administration, and in the fsadm_vxfs(1M) online manual page.
WARNING: msgcnt x: mesg 012: V-2-12: vx_iget - mount_point file system invalid inode number inumber
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.
Unmount the file system and use fsck to run a full structural check.
WARNING: msgcnt x: mesg 013: V-2-13: vx_iposition - mount_point file system inode inumber invalid inode list extent
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.
Unmount the file system and use fsck to run a full structural check.
WARNING: msgcnt x: mesg 014: V-2-14: vx_iget - inode table overflow
All the system in-memory inodes are busy and an attempt was made to use a new inode.
Note: The tunable parameter vx_ninode is used to set the value of vxfs_ninode.
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 vx_ninode parameter in the kernel (see Kernel Tunables).
WARNING: msgcnt x: mesg 015: V-2-15: vx_ibadinactive - mount_point file system can't mark inode inumber bad
WARNING: msgcnt x: mesg 015: V-2-15: vx_ilisterr - mount_point file system can't mark inode inumber bad
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.
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.
WARNING: msgcnt x: mesg 016: V-2-16: vx_ilisterr - mount_point file system error reading inode inumber
An I/O error occurred while reading the inode list. The VX_FULLFSCK flag is set.
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.
WARNING: msgcnt x: mesg 017: V-2-17: vx_attr_getblk - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_attr_iget - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_attr_indadd - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_attr_indtrunc - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_attr_iremove - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_bmap - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_bmap_indirect_ext4 - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_delbuf_flush - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_dio_iovec - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_dirbread - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_dircreate - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_dirlook - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_doextop_iau - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_doextop_now - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_do_getpage - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_enter_ext4 - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_exttrunc - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_get_alloc - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_ilisterr - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_indtrunc - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_iread - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_iremove - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_iremove_attr - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_logwrite_flush - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_oltmount_iget - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_overlay_bmap - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_readnomap - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_reorg_trunc - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_stablestore - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_tranitimes - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_trunc - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_write_alloc2 - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_write_default - mount_point file system inode inumber marked bad in core
WARNING: msgcnt x: mesg 017: V-2-17: vx_zero_alloc - mount_point file system inode inumber marked bad in core
When inode information is no longer dependable, the kernel marks it bad in memory. This is followed by a message to mark it bad on disk as well unless the mount command ioerror option is set to disable, or there is subsequent I/O failure when updating the inode on disk. No further operations can be performed on the inode.
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.
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. The file system can be remounted without a full fsck unless the VX_FULLFSCK flag is set for the file system.
WARNING: msgcnt x: mesg 019: V-2-19: vx_log_add - mount_point file system log overflow
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.
Unmount the file system and use fsck to run a full structural check.
WARNING: msgcnt x: mesg 020: V-2-20: vx_logerr - mount_point file system log error errno
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.
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.
WARNING: msgcnt x: mesg 021: V-2-21: vx_fs_init - mount_point file system validation failure
When a VxFS 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.
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.
WARNING: msgcnt x: mesg 022: V-2-22: vx_mountroot - root file system remount failed
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.
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.
WARNING: msgcnt x: mesg 023: V-2-23: vx_unmountroot - root file system is busy and can't be unmounted cleanly
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.
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.
WARNING: msgcnt x: mesg 024: V-2-24: vx_cutwait - mount_point file system current usage table update error
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.
Unmount the file system and use fsck to run a full structural check.
WARNING: msgcnt x: mesg 025: V-2-25: vx_wsuper - mount_point file system
An I/O error occurred while writing the super-block during a resize operation. The file system is disabled.
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.
WARNING: msgcnt x: mesg 026: V-2-26: vx_snap_copyblk - mount_point primary file system read 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.
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.
WARNING: msgcnt x: mesg 027: V-2-27: vx_snap_bpcopy - mount_point snapshot file system write error
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.
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.
WARNING: msgcnt x: mesg 028: V-2-28: vx_snap_alloc - mount_point snapshot file system out of space
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.
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.
WARNING: msgcnt x: mesg 029: V-2-29: vx_snap_getbp - mount_point snapshot file system block map write error
WARNING: msgcnt x: mesg 030: V-2-30: vx_snap_getbp - mount_point snapshot file system block map read error
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.
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.
WARNING: msgcnt x: mesg 031: V-2-31: vx_disable - mount_point file system disabled
File system disabled, preceded by a message that specifies the reason. This usually indicates a serious disk problem.
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.
WARNING: msgcnt x: mesg 032: V-2-32: vx_disable - mount_point snapshot file system disabled
WARNING: msgcnt x: mesg 033: V-2-33: vx_check_badblock - mount_point file
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.
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.
WARNING: msgcnt x: mesg 034: V-2-34: vx_resetlog - mount_point file system can't reset log
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.
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.
WARNING: msgcnt x: mesg 035: V-2-35: vx_inactive - mount_point file system inactive of locked inode inumber
WARNING: msgcnt x: mesg 036: V-2-36: vx_lctbad - mount_point file system link count table lctnumber bad
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.
Unmount the file system and use fsck to run a full structural check.
WARNING: msgcnt x: mesg 037: V-2-37: vx_metaioerr - function - volume_name file system meta data [read|write] error in dev/block device_ID/block
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.
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.
WARNING: msgcnt x: mesg 038: V-2-38: vx_dataioerr - volume_name file system file data [read|write] error in dev/block device_ID/block
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 is accompanied by a message from the disk driver regarding the disk I/O error.
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.
WARNING: msgcnt x: mesg 039: V-2-39: vx_writesuper - file system super-block write error
An attempt to write the file system super block failed due to a disk I/O error. If the file system was being mounted at the time, the mount will fail. If the file system was mounted at the time and the full fsck flag was being set, the file system will probably be disabled and Message 031 will also be printed. If the super-block was being written as a result of a sync operation, no other action is taken.
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.
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 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.
WARNING: msgcnt x: mesg 040: V-2-40: vx_dqbad - mount_point file system user quota file update error for id id
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.
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.
WARNING: msgcnt x: mesg 041: V-2-41: vx_dqget - mount_point file system user quota file can't read quota for id id
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.
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.
WARNING: msgcnt x: mesg 042: V-2-42: vx_bsdquotaupdate - mount_point file system user_id disk limit reached
WARNING: msgcnt x: mesg 043: V-2-43: vx_bsdquotaupdate - mount_point file system user_id disk quota exceeded too long
WARNING: msgcnt x: mesg 044: V-2-44: vx_bsdquotaupdate - mount_point file system user_id disk quota exceeded
WARNING: msgcnt x: mesg 045: V-2-45: vx_bsdiquotaupdate - mount_point file system user_id inode limit reached
WARNING: msgcnt x: mesg 046: V-2-46: vx_bsdiquotaupdate - mount_point file system user_id inode quota exceeded too long
WARNING: msgcnt x: mesg 047: V-2-47: vx_bsdiquotaupdate - warning: mount_point file system user_id inode quota exceeded
WARNING: msgcnt x: mesg 048: V-2-48: vx_dqread - warning: mount_point file system external user quota file read failed
WARNING: msgcnt x: mesg 049: V-2-49: vx_dqwrite - warning: mount_point file system external user quota file write failed
To maintain reliable usage counts, VxFS maintains the user quotas files as structural files 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.
Determine the reason for the failure on the external quotas file and correct it. Recreate the quotas file.
WARNING: msgcnt x: mesg 056: V-2-56: vx_mapbad - mount_point file system extent allocation unit state bitmap number number marked bad
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.
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.
WARNING: msgcnt x: mesg 057: V-2-57: vx_esum_bad - mount_point file system extent allocation unit summary number number marked bad
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.
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.
WARNING: msgcnt x: mesg 058: V-2-58: vx_isum_bad - mount_point file system inode allocation unit summary number number marked bad
An I/O error occurred reading or writing an inode allocation unit summary.
The VX_FULLFSCK flag is set. If the VX_FULLFSCK flag cannot be set, the file system is disabled.
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.
WARNING: msgcnt x: mesg 059: V-2-59: vx_snap_getbitbp - mount_point snapshot file system bitmap write error
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.
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.
WARNING: msgcnt x: mesg 060: V-2-60: vx_snap_getbitbp - mount_point snapshot file system bitmap read error
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.
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.
WARNING: msgcnt x: mesg 061: V-2-61: vx_resize - mount_point file system remount failed
NOTICE: msgcnt x: mesg 062: V-2-62: vx_attr_creatop - invalid disposition returned by attribute driver
WARNING: msgcnt x: mesg 063: V-2-63: vx_fset_markbad - mount_point file system mount_point fileset (index number) marked bad
WARNING: msgcnt x: mesg 064: V-2-64: vx_ivalidate - mount_point file system inode number version number exceeds fileset's
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.
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.
NOTICE: msgcnt x: mesg 066: V-2-66: DMAPI mount event - buffer
WARNING: msgcnt x: mesg 067: V-2-67: mount of device_path requires HSM agent
WARNING: msgcnt x: mesg 069: V-2-69: memory usage specified by the vxfs:vxfs_ninode and vxfs:vx_bc_bufhwm parameters exceeds available memory; the system may hang under heavy load
The value of the system tunable parameters---vx_ninode and vx_bc_bufhwm---add up to a value that is more than 66% of the kernel virtual address space or more than 50% of the physical system memory. VxFS inodes require approximately one kilobyte each, so both values can be treated as if they are in units of one kilobyte.
To avoid a system hang, reduce the value of one or both parameters to less than 50% of physical memory or to 66% of kernel virtual memory. For more information on performance and tuning, see VxFS Performance: Creating, Mounting, and Tuning File Systems. Note: The tunable parameter vx_ninode is used to set the value of vxfs_ninode.
WARNING: msgcnt x: mesg 070: V-2-70: checkpoint checkpoint_name removed from file system mount_point
The file system ran out of space while updating a Storage Checkpoint. The Storage Checkpoint was removed to allow the operation to complete.
Increase the size of the file system. If the file system size cannot be increased, remove files to create sufficient space for new Storage Checkpoints. Monitor capacity of the file system closely to ensure it does not run out of space. See the fsadm_vxfs(1M) manual page more information.
NOTICE: msgcnt x: mesg 071: V-2-71: cleared data I/O error flag in mount_point file system
The user data I/O error flag was reset when the file system was mounted. This message indicates that a read or write error occurred (see Message Number 038) while the file system was previously mounted.
WARNING: msgcnt x: vxfs: mesg 072: could not failover for volume_name file system
This message is specific to the cluster file system. The message indicates a problem in a scenario where a node failure has occurred in the cluster and the newly selected primary node encounters a failure.
Save the system logs and core dump of the node along with the disk image (metasave) and contact your customer support organization. The node can be rebooted to join the cluster.
WARNING: msgcnt x: mesg 074: V-2-74: vx_rcfg - fileset_number fileset not found while remounting mount_point
This message is specific to the cluster file system. The message indicates a problem in a scenario where a node failure has occurred in the cluster and the newly selected primary node encounters a failure.
Save the core dump of the node and contact your customer support organization. The node can be rebooted to join the cluster.
WARNING: msgcnt x: mesg 075: V-2-75: replay fsck failed for mount_point file system
NOTICE: msgcnt x: mesg 076: V-2-76: checkpoint asynchronous operation on mount_point file system still in progress
An EBUSY message was received while trying to unmount a file system. The unmount failure was caused by a pending asynchronous fileset operation, such as a fileset removal or fileset conversion to a nodata Storage Checkpoint.
The operation may take a considerable length of time. You can do a forced unmount (see the umount_vxfs(1M) manual page), or simply wait for the operation to complete so file system can be unmounted cleanly.
WARNING: msgcnt x: mesg 077: V-2-77: vx_fshdchange - mount_point file system number fileset, fileset header: checksum failed
WARNING: msgcnt x: mesg 078: V-2-78: vx_ilealloc - mount_point file system mount_point fileset (index number) ilist corrupt
The inode list for the fileset was corrupted and the corruption was detected while allocating new inodes. The failed system call returns an ENOSPC error. Any subsequent inode allocations will fail unless a sufficient number of files are removed.
Unmount the file system and use fsck to run a full structural check.
WARNING: msgcnt x: mesg 017: V-2-79: vx_attr_getblk - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_attr_iget - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_attr_indadd - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_attr_indtrunc - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_attr_iremove - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_bmap - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_bmap_indirect_ext4 - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_delbuf_flush - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_dio_iovec - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_dirbread - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_dircreate - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_dirlook - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_doextop_iau - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_doextop_now - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_do_getpage - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_enter_ext4 - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_exttrunc - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_get_alloc - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_ilisterr - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_indtrunc - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_iread - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_iremove - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_iremove_attr - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_logwrite_flush - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_oltmount_iget - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_overlay_bmap - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_readnomap - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_reorg_trunc - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_stablestore - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_tranitimes - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_trunc - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_write_alloc2 - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_write_default - mount_point file system inode inumber marked bad on disk
WARNING: msgcnt x: mesg 017: V-2-79: vx_zero_alloc - mount_point file system inode inumber marked bad on disk
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.
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.
WARNING: msgcnt x: vxfs: mesg 080: Disk layout versions older than Version 4 will not be supported in the next release. It is advisable to upgrade to the latest disk layout version now. See vxupgrade(1M) for information on upgrading a VxFS file system and see the VxFS Release Notes for information on disk layout support.
Use the vxupgrade command to begin upgrading file systems using older disk layouts to Version 4. Consider the following when planning disk layout upgrades:
WARNING: msgcnt x: mesg 081: V-2-81: possible network partition detected
This message displays when CFS detects a possible network partition and disables the file system locally, that is, on the node where the message appears.
There are one or more private network links for communication between the nodes in a cluster. At least one link must be active to maintain the integrity of the cluster. If all the links go down, after the last network link is broken, the node can no longer communicate with other nodes in the cluster.
Check the network connections. After verifying that the network connections is operating correctly, unmount the disabled file system and mount it again.
WARNING: msgcnt x: mesg 082: V-2-82: volume_name file system is on shared volume. It may get damaged if cluster is in partitioned state.
If a cluster node is in a partitioned state, and if the file system is on a shared VxVM volume, this volume may become corrupted by accidental access from another node in the cluster.
These shared disks can also be seen by nodes in a different partition, so they can inadvertently be corrupted. So the second message 082 tells that the device mentioned is on shared volume and damage can happen only if it is a real partition problem. Do not use it on any other node until the file system is unmounted from the mounted nodes.
WARNING: msgcnt x: mesg 083: V-2-83: mount_point file system log is not compatible with the specified intent log I/O size
Either the specified mount logiosize size is not compatible with the file system layout, or the file system is corrupted.
Mount the file system again without specifying the logiosize option, or use a logiosize value compatible with the intent log specified when the file system was created. If the error persists, unmount the file system and use fsck to run a full structural check.
WARNING: msgcnt x: mesg 084: V-2-84: in volume_name quota on failed during assumption. (stage stage_number)
In a cluster file system, when the primary of the file system fails, a secondary file system is chosen to assume the role of the primary. The assuming node will be able to enforce quotas after becoming the primary.
If the new primary is unable to enforce quotas this message will be displayed.
Issue the quotaon command from any of the nodes that have the file system mounted.
WARNING: msgcnt x: mesg 085: V-2-85: Checkpoint quota - warning: file_system file system fileset quota hard limit exceeded
WARNING: msgcnt x: mesg 086: V-2-86: Checkpoint quota - warning: file_system file system fileset quota soft limit exceeded
WARNING: msgcnt x: mesg 087: V-2-87: vx_dotdot_manipulate: file_system file system inumber inode ddnumber dotdot inode error
WARNING: msgcnt x: mesg 088: V-2-88: quotaon on file_system failed; limits exceed limit
WARNING: msgcnt x: mesg 089: V-2-89: quotaon on file_system invalid; disk usage for group/user id uid exceeds sectors sectors
WARNING: msgcnt x: mesg 090: V-2-90: quota on file_system failed; soft limits greater than hard limits
WARNING: msgcnt x: mesg 091: V-2-91: vx_fcl_truncate - failure to punch hole at offset offset for bytes bytes in File Change Log file; error error_number
The vxfs kernel has experienced an error while trying to manage the space consumed by the File Change Log file. Because the space cannot be actively managed at this time, the FCL has been deactivated and has been truncated to 1 file system block, which contains the FCL superblock.
WARNING: msgcnt x: mesg 092: V-2-92: vx_mkfcltran - failure to map offset offset in File Change Log file
WARNING: msgcnt x: mesg 093: V-2-93: Disk layout versions older than Version 6 will not be supported for shared mounts in the next release. It is advisable to upgrade to the latest layout version now. See vxupgrade(1M) for information on upgrading a VxFS file system and see the VxFS Release Notes for information on disk layout support.
Upgrade your disk layout to Version 6 for shared mounts. This is not a mandatory action, but is recommended. Disk layout Versions 4 and 5 will still be supported for local mounts in the next release of the VxFS.
Use the vxupgrade command to begin upgrading file systems using older disk layouts to Version 6.
WARNING: msgcnt x: mesg 095: V-2-95: Setting vxfs_ifree_timelag to time since the specified value for vxfs_ifree_timelag is less than the recommended minimum value of time.
WARNING: msgcnt x: mesg 096: V-2-96: file_system file system fullfsck flag set - function_name.
WARNING: msgcnt x: mesg 097: V-2-97: VxFS failed to create new thread (error_number, function_address:argument_address)
VxFS failed to create a kernel thread due to resource constraints, which is often a memory shortage.
VxFS will retry the thread creation until it succeeds; no immediate action is required. Kernel resources, such as kernel memory, might be overcommitted. If so, reconfigure the system accordingly.
WARNING: msgcnt x: mesg 098: V-2-98: VxFS failed to initialize File Change Log for fileset fileset (index number) of mount_point file system
WARNING: msgcnt x: mesg 099: V-2-99: The specified value for vx_ninode is less than the recommended minimum value of min_value
Auto-tuning or the value specified by the system administrator resulted in a value lower than the recommended minimum for the total number of inodes that can be present in the inode cache. VxFS will ignore the newly tuned value and will keep the value specified in the message (VX_MINNINODE).
WARNING: msgcnt x: mesg 100: V-2-100: Inode inumber can not be accessed: file size exceeds OS limitations.
The specified inode's size is larger than the file size limit of the current operating system. The file cannot be opened on the current platform. This can happen when a file is created on one OS and the filesystem is then moved to a machine running an OS with a smaller file size limit.
If the file system is moved to the platform on which the file was created, the file can be accessed from there. It can then be converted to multiple smaller files in a manner appropriate to the application and the file's format, or simply be deleted if it is no longer required.
WARNING: msgcnt x: mesg 101: V-2-101: File Change Log on mount_point for file set index approaching max file size supported. File Change Log will be reactivated when its size hits max file size supported.
The size of the FCL file is approching the maximum file size supported. This size is platform specific. When the FCL file is reaches the maximum file size, the FCL will be deactivated and reactivated. All logging information gathered so far will be lost.
Take any corrective action possible to restrict the loss due to the FCL being deactivated and reactivated.
WARNING: msgcnt x: mesg 102: V-2-102: File Change Log of mount_point for file set index has been reactivated.
The size of FCL file reached the maximum supported file size and the FCL has been reactivated. All records stored in the FCL file, starting from the current fc_loff up to the maximum file size, have been purged. New records will be recorded in the FCL file starting from offset fs_bsize. The activation time in the FCL is reset to the time of reactivation. The impact is equivalent to File Change Log being deactivated and activated.
|
| ^ Return to Top | < Previous | Next > |
| Product: File System Guides | |
| Manual: File System 4.1 Administrator's Guide | |
|
VERITAS Software Corporation
www.veritas.com |