079

Article:HOWTO13962  |  Created: 2008-01-20  |  Updated: 2008-01-02  |  Article URL http://www.symantec.com/docs/HOWTO13962
Article Type
How To

Product(s)

Environment


079

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

Description:

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.

Recommended 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.


Legacy ID



314866


Article URL http://www.symantec.com/docs/HOWTO13962


Terms of use for this information are found in Legal Notices