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

Diagnostic messages

This appendix includes the following topics:

■ File system response to problems

■ About kernel messages

■ Kernel messages

■ About unique message identifiers

■ Unique message identifiers

■ Dewey kernel messages

■ Dewey UMI messages

File system response to problems

When the file system encounters problems, it responds in one of the following

ways:

Inodes can be marked bad if an inode update or a directory-block

update fails. In these types of failures, the file system does not

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.

Marking an inode bad

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 transactions

Appendix