Veritas File System 5.1 SP1 Administrator's Guide HP-UX 11i v3 HP Part Number: 5900-1499 Published: April 2011 Edition: 1.
© Copyright 2011 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents Technical Support ............................................................................................... 4 Chapter 1 Introducing Veritas File System ....................................... 15 About Veritas File System .............................................................. Logging ................................................................................ Extents ................................................................................ File system disk layouts ........
8 Contents Chapter 2 VxFS performance: creating, mounting, and tuning file systems ..................................................................... 33 Creating a VxFS file system ............................................................ Block size ............................................................................. Intent log size ........................................................................ Mounting a VxFS file system ..........................................................
Contents Failure to preserve extent attributes .......................................... 68 Chapter 4 Veritas File System I/O ....................................................... 69 About Veritas File System I/O ......................................................... Buffered and Direct I/O ................................................................. Direct I/O ............................................................................. Unbuffered I/O .........................................
10 Contents Volume availability ................................................................ 91 About volume sets ........................................................................ 92 Creating and managing volume sets .......................................... 92 Creating multi-volume file systems ................................................. 93 Example of creating a multi-volume file system ........................... 94 Converting a single volume file system to a multi-volume file system .
Contents Modifying Cached ODM settings for individual files .................... 118 Adding Cached ODM settings via the cachemap ......................... 119 Making the caching settings persistent across mounts ................ 120 Appendix A Quick Reference ................................................................. 121 Command summary .................................................................... Online manual pages ...................................................................
12 Contents V-2-1 .................................................................................. V-2-2 .................................................................................. V-2-3 .................................................................................. V-2-4 .................................................................................. V-2-5 .................................................................................. V-2-6 ...............................................
Contents V-2-61 ................................................................................ V-2-62 ................................................................................ V-2-63 ................................................................................ V-2-64 ................................................................................ V-2-66 ............................................................................... V-2-67 ........................................................
14 Contents V-2-110 .............................................................................. V-2-111 .............................................................................. V-2-112 .............................................................................. Dewey UMI messages .................................................................. V-3-20002 ........................................................................... V-3-20003 .......................................................
Chapter 1 Introducing Veritas File System This chapter includes the following topics: ■ About Veritas File System ■ Veritas File System features ■ Veritas File System performance enhancements ■ Using Veritas File System About Veritas File System A file system is simply a method for storing and organizing computer files and the data they contain to make it easy to find and access them.
16 Introducing Veritas File System About Veritas File System ■ File system disk layouts Logging A key aspect of any file system is how to recover if a system crash occurs. Earlier methods required a time-consuming scan of the entire file system. A better solution is the method of logging (or journaling) the metadata of files. VxFS logs new attribute information into a reserved area of the file system, whenever file system changes occur.
Introducing Veritas File System Veritas File System features Veritas File System features VxFS includes the following features: ■ Extent-based allocation Extents allow disk I/O to take place in units of multiple blocks if storage is allocated in consecutive blocks. ■ Extent attributes Extent attributes are the extent allocation policies associated with a file. ■ Fast file system recovery VxFS provides fast recovery of a file system from system failure.
18 Introducing Veritas File System Veritas File System features Clustered file systems are an extension of VxFS that support concurrent direct media access from multiple systems. ■ Improved database performance ■ Cross-platform data sharing Cross-platform data sharing allows data to be serially shared among heterogeneous systems where each system has direct access to the physical devices that hold the data. See the Veritas Storage Foundation Advanced Features Administrator's Guide.
Introducing Veritas File System Veritas File System features Extent-based allocation Disk space is allocated in 1024-byte sectors to form logical blocks. VxFS supports logical block sizes of 1024, 2048, 4096, and 8192 bytes. The default block size is the larger of 1K or the device's hardware sector size for file system sizes of up to 1 TB, and 8K for file system sizes 1 TB or larger. An extent is defined as one or more adjacent blocks of data within the file system.
20 Introducing Veritas File System Veritas File System features The extent descriptor fields are defined as follows: type Identifies uniquely an extent descriptor record and defines the record's length and format. offset Represents the logical file offset in blocks for a given descriptor. Used to optimize lookups and eliminate hole descriptor entries. starting block Is the starting file system block of the extent. number of blocks Is the number of contiguous blocks in the extent.
Introducing Veritas File System Veritas File System features The vxtunefs command allows the administrator to set or view the default indirect data extent size of a file system. See the vxtunefs(1M) manual page. Fast file system recovery Most file systems rely on full structural verification by the fsck utility as the only means to recover from a system failure.
22 Introducing Veritas File System Veritas File System features number of times the log wraps around. However, increasing the intent log size can lead to greater times required for a log replay if there is a system failure. Note: Inappropriate sizing of the intent log can have a negative impact on system performance. See the mkfs_vxfs(1M) and the fsadm_vxfs(1M) manual pages.
Introducing Veritas File System Veritas File System features The blkclear option and data integrity In environments where performance is more important than absolute data integrity, the preceding situation is not of great concern. However, VxFS supports environments that emphasize data integrity by providing the mount -o blkclear option that ensures uninitialized data does not appear in a file.
24 Introducing Veritas File System Veritas File System features Temporary file system mode On most UNIX systems, temporary file system directories, such as /tmp and /usr/tmp, often hold files that do not need to be retained when the system reboots. The underlying file system does not need to maintain a high degree of structural integrity for these temporary directories.
Introducing Veritas File System Veritas File System features and efficient backup strategies. Backup and restore applications can leverage a Storage Checkpoint, a disk- and I/O-efficient copying technology for creating periodic frozen images of a file system. Storage Checkpoints present a view of a file system at a point in time, and subsequently identifies and maintains copies of the original file system blocks.
26 Introducing Veritas File System Veritas File System features Treating regular VxFS files as raw devices has the following advantages for databases: ■ Commercial database servers such as Oracle Server can issue kernel supported asynchronous I/O calls (through the asyncdsk or Posix AIO interface) on these pseudo devices but not on regular files.
Introducing Veritas File System Veritas File System features webcrawlers, search and indexing engines, and replication software that typically scan an entire file system searching for modifications since a previous scan. FCL functionality is a separately licensed feature. See “About the File Change Log file” on page 82. Multi-volume support The multi-volume support (MVS) feature allows several volumes to be represented by a single logical object.
28 Introducing Veritas File System Veritas File System performance enhancements Partitioned directories Normally, a large volume of parallel threads performing access and updates on a directory that commonly exist in an file system suffers from exponentially longer wait times for the threads. This feature creates partitioned directories to improve the directory performance of file systems.
Introducing Veritas File System Veritas File System performance enhancements ■ Integration with VxVM™ ■ Support for large directories Note: VxFS reduces the file lookup time in directories with an extremely large number of files. About enhanced I/O performance VxFS provides enhanced I/O performance by applying an aggressive I/O clustering policy, integrating with VxVM, and allowing application specific parameters to be set on a per-file system basis. See “Enhanced I/O clustering” on page 29.
30 Introducing Veritas File System Using Veritas File System ■ Discovered Direct I/O All sizes above this value would be performed as direct I/O. ■ Maximum Direct I/O Size This value defines the maximum size of a single direct I/O. See the vxtunefs(1M) and tunefstab(4) manual pages. Using Veritas File System There are three main methods to use, manage, modify, and tune VxFS: ■ See “Veritas Enterprise Administrator Graphical User Interface” on page 30.
Introducing Veritas File System Using Veritas File System ■ Remove resource information for a cluster file system See the VEA online help. Veritas Operations Manager Symantec recommends use of Veritas Operations Manager to manage Storage Foundation and Cluster Server environments. Veritas Operations Manager provides a centralized management console for Veritas Storage Foundation and High Availability products.
32 Introducing Veritas File System Using Veritas File System ■ Making all small files contiguous ■ Consolidating free blocks for file system use This utility can run on demand and should be scheduled regularly as a cron job. About file system resizing A file system is assigned a specific size as soon as it is created; the file system may become too small or too large as changes in file system usage take place over time. VxFS is capable of increasing or decreasing the file system size while in use.
Chapter 2 VxFS performance: creating, mounting, and tuning file systems This chapter includes the following topics: ■ Creating a VxFS file system ■ Mounting a VxFS file system ■ Tuning the VxFS file system ■ Monitoring free space ■ Tuning I/O Creating a VxFS file system When you create a file system with the mkfs command, you can select the following characteristics: ■ Block size See “Block size” on page 34. ■ Intent log size See “Intent log size” on page 34.
34 VxFS performance: creating, mounting, and tuning file systems Creating a VxFS file system Block size The unit of allocation in VxFS is an extent. Unlike some other UNIX file systems, VxFS does not make use of block fragments for allocation because storage is allocated in extents that consist of one or more blocks. You specify the block size when creating a file system by using the mkfs -o bsize option. The block size cannot be altered after the file system is created.
VxFS performance: creating, mounting, and tuning file systems Mounting a VxFS file system Mounting a VxFS file system In addition to the standard mount mode (delaylog mode), Veritas File System (VxFS) provides the following modes of operation: ■ log ■ delaylog ■ tmplog ■ logsize ■ nodatainlog ■ blkclear ■ mincache ■ convosync ■ ioerror ■ largefiles|nolargefiles ■ cio ■ mntlock|mntunlock ■ tranflush Caching behavior can be altered with the mincache option, and the behavior of O_SYN
36 VxFS performance: creating, mounting, and tuning file systems Mounting a VxFS file system See the mount_vxfs(1M) manual page. The log mode In log mode, all system calls other than write(2), writev(2), and pwrite(2) are guaranteed to be persistent after the system call returns to the application. The rename(2) system call flushes the source file to disk to guarantee the persistence of the file data before renaming it.
VxFS performance: creating, mounting, and tuning file systems Mounting a VxFS file system Note: The term "effects of system calls" refers to changes to file system data and metadata caused by the system call, excluding changes to st_atime. See the stat(2) manual page. Logging mode persistence guarantees In all logging modes, VxFS is fully POSIX compliant. The effects of the fsync(2) and fdatasync(2) system calls are guaranteed to be persistent after the calls return.
38 VxFS performance: creating, mounting, and tuning file systems Mounting a VxFS file system is already written. If a disk error causes the metadata update to fail, then the file must be marked bad and the entire file is lost. If a disk supports bad block revectoring, then a failure on the data update is unlikely, so logging synchronous writes should be allowed. If the disk does not support bad block revectoring, then a failure is more likely, so the nodatainlog mode should be used.
VxFS performance: creating, mounting, and tuning file systems Mounting a VxFS file system ■ The mincache=direct, mincache=unbuffered, and mincache=dsync modes are used in environments where applications have reliability problems caused by the kernel buffering of I/O and delayed flushing of non-synchronous I/O. ■ The mincache=direct and mincache=unbuffered modes guarantee that all non-synchronous I/O requests to files are handled as if the VX_DIRECT or VX_UNBUFFERED caching advisories had been specified.
40 VxFS performance: creating, mounting, and tuning file systems Mounting a VxFS file system ■ convosync=dsync Note: The convosync=dsync option violates POSIX guarantees for synchronous I/O. ■ convosync=unbuffered The convosync=delay mode causes synchronous and data synchronous writes to be delayed rather than to take effect immediately. No special action is performed when closing a file. This option effectively cancels any data integrity guarantees normally provided by opening a file with O_SYNC.
VxFS performance: creating, mounting, and tuning file systems Mounting a VxFS file system The policies are the following: ■ disable ■ nodisable ■ wdisable ■ mwdisable ■ mdisable The disable policy If disable is selected, VxFS disables the file system after detecting any I/O error. You must then unmount the file system and correct the condition causing the I/O error. After the problem is repaired, run fsck and mount the file system again. In most cases, replay fsck to repair the file system.
42 VxFS performance: creating, mounting, and tuning file systems Mounting a VxFS file system to persist than write errors, such as when using non-redundant storage. mwdisable is the default ioerror mount option for local mounts. See the mount_vxfs(1M) manual page. The mdisable policy If mdisable (metadata disable) is selected, the file system is disabled if a metadata read or write fails. However, the file system continues to operate if the failure is confined to data extents.
VxFS performance: creating, mounting, and tuning file systems Mounting a VxFS file system Mounting a file system with large files If a mount succeeds and nolargefiles is specified, the file system cannot contain or create any large files. If a mount succeeds and largefiles is specified, the file system may contain and create large files. The mount command fails if the specified largefiles|nolargefiles option does not match the on-disk flag.
44 VxFS performance: creating, mounting, and tuning file systems Mounting a VxFS file system option, the file system must be unmounted and mounted again without the cio option. The mntlock|mntunlock option The mntlock option prevents a file system from being unmounted by an application. This option is useful for applications that do not want the file systems that the applications are monitoring to be improperly unmounted by other applications or administrators.
VxFS performance: creating, mounting, and tuning file systems Tuning the VxFS file system Performance can be significantly improved if the file system is mounted using convosync=dsync without any loss of data integrity.
46 VxFS performance: creating, mounting, and tuning file systems Tuning the VxFS file system command can be specified with the -h option so that the new value of vx_ninode takes effect after a system reboot. Be careful when changing the value of vx_ninode, as the value can affect file system performance. Typically, the default value determined by VxFS based on the amount of system memory ensures good system performance across a wide range of applications.
VxFS performance: creating, mounting, and tuning file systems Tuning the VxFS file system This command restores vx_ninode to its default value by clearing the user-specified value. The default value is the value determined by VxFS to be optimal based on the amount of system memory, which is used if vx_ninode is not explicitly set.
48 VxFS performance: creating, mounting, and tuning file systems Tuning the VxFS file system sets the high water mark to 300 megabytes. The change takes effect after you rebuild the HP-UX kernel using the mk_kernel command. You specify the vx_bc_bufhwm tunable in units of kilobytes. The minimum value is 6144. Increasing the value of vx_bc_bufhwm increases the VxFS buffer cache immediately, allowing a greater amount of memory to be used to cache VxFS metadata.
VxFS performance: creating, mounting, and tuning file systems Monitoring free space The default value of vx_ifree_timelag is 0. By setting vx_ifree_timelag to 0, the inode free time lag is autotuned to 600 seconds. Specifying negative one (-1) stops the freeing of inode space; no further inode allocations are freed until the value is changed back to a value other than negative one. You can change the value of vx_ifree_timelag using the sam or kctune commands. See the sam(1M) and kctune(1M) manual pages.
50 VxFS performance: creating, mounting, and tuning file systems Monitoring free space See the fsadm_vxfs(1M) manual page. Monitoring fragmentation Fragmentation reduces performance and availability. Regular use of fsadm's fragmentation reporting and reorganization facilities is therefore advisable. The easiest way to ensure that fragmentation does not become a problem is to schedule regular defragmentation runs using the cron command.
VxFS performance: creating, mounting, and tuning file systems Monitoring free space file system. If not, it may be a good idea to resize the file system; full file systems tend to fragment and are difficult to defragment. It is also possible that the reorganization is not being performed at a time during which the file system in question is relatively idle. Directory reorganization is not nearly as critical as extent reorganization, but regular directory reorganization improves performance.
52 VxFS performance: creating, mounting, and tuning file systems Tuning I/O The following example performs default reclamation of free storage to the Thin Storage LUN on a VxFS file system mounted at /mnt1: # fsadm -R /mnt1 The following example performs aggressive reclamation of free storage to the Thin Storage LUN on a VxFS file system mounted at /mnt1: # fsadm -R -o aggressive /mnt1 After performing the reclaim operation, you can verify that the storage was reclaimed using the vxdisk -o thin list com
VxFS performance: creating, mounting, and tuning file systems Tuning I/O 53 Tuning VxFS I/O parameters VxFS provides a set of tunable I/O parameters that control some of its behavior. These I/O parameters are useful to help the file system adjust to striped or RAID-5 volumes that could yield performance superior to a single disk. Typically, data streaming applications that access large files see the largest benefit from tuning the file system.
54 VxFS performance: creating, mounting, and tuning file systems Tuning I/O /dev/vx/dsk/userdg/solbuild read_pref_io=64k,write_pref_io=64k,read_nstream=4,write_nstream=4 /dev/vx/dsk/userdg/solrelease read_pref_io=64k,write_pref_io=64k,read_nstream=4,write_nstream=4 /dev/vx/dsk/userdg/solpatch read_pref_io=128k,write_pref_io=128k,read_nstream=4,write_nstream=4 Tunable I/O parameters Table 2-1 provides a list and description of these parameters.
VxFS performance: creating, mounting, and tuning file systems Tuning I/O Table 2-1 Tunable VxFS I/O parameters (continued) Parameter Description default_indir_ size On VxFS, files can have up to ten direct extents of variable size stored in the inode. After these extents are used up, the file must use indirect extents which are a fixed size that is set when the file first uses indirect extents. These indirect extents are 8K by default.
56 VxFS performance: creating, mounting, and tuning file systems Tuning I/O Table 2-1 Tunable VxFS I/O parameters (continued) Parameter Description fcl_keeptime Specifies the minimum amount of time, in seconds, that the VxFS File Change Log (FCL) keeps records in the log. When the oldest 8K block of FCL records have been kept longer than the value of fcl_keeptime, they are purged from the FCL and the extents nearest to the beginning of the FCL file are freed.
VxFS performance: creating, mounting, and tuning file systems Tuning I/O Table 2-1 Tunable VxFS I/O parameters (continued) Parameter Description fcl_winterval Specifies the time, in seconds, that must elapse before the VxFS File Change Log (FCL) records a data overwrite, data extending write, or data truncate for a file. The ability to limit the number of repetitive FCL records for continuous writes to the same file is important for file system performance and for applications processing the FCL.
58 VxFS performance: creating, mounting, and tuning file systems Tuning I/O Table 2-1 Tunable VxFS I/O parameters (continued) Parameter Description initial_extent_size Changes the default initial extent size. VxFS determines, based on the first write to a new file, the size of the first extent to be allocated to the file. Normally the first extent is the smallest power of 2 that is larger than the size of the first write. If that power of 2 is less than 8K, the first extent allocated is 8K.
VxFS performance: creating, mounting, and tuning file systems Tuning I/O Table 2-1 Tunable VxFS I/O parameters (continued) Parameter Description inode_aging_size Specifies the minimum size to qualify a deleted inode for inode aging. Inode aging is used in conjunction with file system Storage Checkpoints to allow quick restoration of large, recently deleted files. For best performance, it is advisable to age only a limited number of larger files before completion of the removal process.
60 VxFS performance: creating, mounting, and tuning file systems Tuning I/O Table 2-1 Tunable VxFS I/O parameters (continued) Parameter Description qio_cache_enable Enables or disables caching on Quick I/O files. The default behavior is to disable caching. To enable caching, set qio_cache_enable to 1. On systems with large memories, the database cannot always use all of the memory as a cache. By enabling file system caching as a second level cache, performance may be improved.
VxFS performance: creating, mounting, and tuning file systems Tuning I/O Table 2-1 Tunable VxFS I/O parameters (continued) Parameter Description write_throttle The write_throttle parameter is useful in special situations where a computer system has a combination of a large amount of memory and slow storage devices. In this configuration, sync operations, such as fsync(), may take long enough to complete that a system appears to hang.
62 VxFS performance: creating, mounting, and tuning file systems Tuning I/O Note: VxFS does not query VxVM with multiple volume sets. To improve I/O performance when using multiple volume sets, use the vxtunefs command. If the file system is being used with a hardware disk array or volume manager other than VxVM, try to align the parameters to match the geometry of the logical disk.
Chapter 3 Extent attributes This chapter includes the following topics: ■ About extent attributes ■ Commands related to extent attributes About extent attributes Veritas File System (VxFS) allocates disk space to files in groups of one or more adjacent blocks called extents. VxFS defines an application interface that allows programs to control various aspects of the extent allocation for a given file. The extent allocation policies associated with a file are referred to as extent attributes.
64 Extent attributes About extent attributes Some of the extent attributes are persistent and become part of the on-disk information about the file, while other attributes are temporary and are lost after the file is closed or the system is rebooted. The persistent attributes are similar to the file's permissions and are written in the inode for the file. When a file is copied, moved, or archived, only the persistent attributes of the source file are preserved in the new file.
Extent attributes About extent attributes smaller pieces. By erring on the side of minimizing fragmentation for the file system, files may become so non-contiguous that their I/O characteristics would degrade. Fixed extent sizes are particularly appropriate in the following situations: ■ If a file is large and contiguous, a large fixed extent size can minimize the number of extents in the file.
66 Extent attributes Commands related to extent attributes Write operations beyond reservation A reservation request can specify that no allocations can take place after a write operation fills the last available block in the reservation. This request can be used a way similar to the function of the ulimit command to prevent a file's uncontrolled growth. Reservation trimming A reservation request can specify that any unused reservation be released when the file is closed.
Extent attributes Commands related to extent attributes file system does not support extent attributes, has a different block size than the source file system, or lacks free extents appropriate to satisfy the extent attribute requirements.
68 Extent attributes Commands related to extent attributes To get an extent attribute's information ◆ Get the extent attribute information for the file file1: # getext -F vxfs file1 file1: Bsize 1024 Reserve 36 Extent Size 3 align noextend The file file1 has a block size of 1024 bytes, 36 blocks reserved, a fixed extent size of 3 blocks, and all extents aligned to 3 block boundaries. The file size cannot be increased after the current reservation is exhausted.
Chapter 4 Veritas File System I/O This chapter includes the following topics: ■ About Veritas File System I/O ■ Buffered and Direct I/O ■ Concurrent I/O ■ Cache advisories ■ Freezing and thawing a file system ■ Getting the I/O size ■ Enabling and disabling Concurrent I/O for a DB2 database About Veritas File System I/O VxFS processes two basic types of file system I/O: ■ Sequential ■ Random or I/O that is not sequential For sequential I/O, VxFS employs a read-ahead policy by default when
70 Veritas File System I/O Buffered and Direct I/O Buffered and Direct I/O VxFS responds with read-ahead for sequential read I/O. This results in buffered I/O. The data is prefetched and retained in buffers for the application. This is the default VxFS behavior. On the other hand, direct I/O does not buffer the data when the I/O to the underlying device is completed. This saves system resources like memory and CPU usage. Direct I/O is possible only when alignment and sizing criteria are satisfied.
Veritas File System I/O Buffered and Direct I/O Direct I/O versus synchronous I/O Because direct I/O maintains the same data integrity as synchronous I/O, it can be used in many applications that currently use synchronous I/O. If a direct I/O request does not allocate storage or extend the file, the inode is not immediately written. Direct I/O CPU overhead The CPU cost of direct I/O is about the same as a raw disk transfer.
72 Veritas File System I/O Concurrent I/O and, if necessary, an increased file size. In data synchronous I/O, the data is transferred to disk synchronously before the write returns to the user. If the file is not extended by the write, the times are updated in memory, and the call returns to the user. If the file is extended by the operation, the inode is written before the write returns. The direct I/O and VX_DSYNC advisories are maintained on a per-file-descriptor basis. Data synchronous I/O vs.
Veritas File System I/O Cache advisories See vxfsio(7) manual page. ■ By using the cio mount option. The read(2) and write(2) operations occurring on all of the files in this particular file system will use concurrent I/O. See “The cio option” on page 43. See the mount_vxfs(1M) manual page. Concurrent I/O is a separately licensed feature. Cache advisories VxFS allows an application to set cache advisories for use when accessing files.
74 Veritas File System I/O Getting the I/O size is blocked at the system call level. Current operations are completed and the file system is synchronized to disk. When the file system is frozen, any attempt to use the frozen file system, except for a VX_THAW ioctl command, is blocked until a process executes the VX_THAW ioctl command or the time-out on the freeze expires. Getting the I/O size VxFS provides the VX_GET_IOPARAMETERS ioctl to get the recommended I/O sizes to use on a file system.
Veritas File System I/O Enabling and disabling Concurrent I/O for a DB2 database 75 # /usr/sbin/mount -F vxfs -o cio special /mount_point ■ special is a block special device ■ /mount_point is the directory where the file system will be mounted.
76 Veritas File System I/O Enabling and disabling Concurrent I/O for a DB2 database To disable Concurrent I/O on a file system using the mount command 1 Shutdown the DB2 instance. 2 Unmount the file sytem using the umount command. 3 Mount the file system again using the mount command without using the -o cio option.
Chapter 5 Quotas This chapter includes the following topics: ■ About quota limits ■ About quota files on Veritas File System ■ About quota commands ■ Using quotas About quota limits Veritas File System (VxFS) supports user quotas. The quota system limits the use of two principal resources of a file system: files and data blocks. For each of these resources, you can assign quotas to individual users to limit their usage.
78 Quotas About quota files on Veritas File System See “About quota files on Veritas File System” on page 78. The quota soft limit can be exceeded when VxFS preallocates space to a file. Quota limits cannot exceed two terabytes on a Version 5 disk layout. See “About extent attributes” on page 63. About quota files on Veritas File System A quotas file (named quotas) must exist in the root directory of a file system for any of the quota commands to work.
Quotas Using quotas Turning on quotas To use the quota functionality on a file system, quotas must be turned on. You can turn quotas on at mount time or after a file system is mounted. To turn on quotas ◆ To turn on user quotas for a VxFS file system, enter: # quotaon /mount_point Turning on quotas at mount time Quotas can be turned on with the mount command when you mount a file system.
80 Quotas Using quotas To modify time limits ◆ Specify the -t option to modify time limits for any user: # edquota -t Viewing disk quotas and usage Use the quota command to view a user's disk quotas and usage on VxFS file systems.
Chapter 6 File Change Log This chapter includes the following topics: ■ About File Change Log ■ About the File Change Log file ■ File Change Log administrative interface ■ File Change Log programmatic interface ■ Summary of API functions ■ Reverse path name lookup About File Change Log The VxFS File Change Log (FCL) tracks changes to files and directories in a file system.
82 File Change Log About the File Change Log file About the File Change Log file File Change Log records file system changes such as creates, links, unlinks, renaming, data appended, data overwritten, data truncated, extended attribute modifications, holes punched, and miscellaneous file property updates. Note: FCL is supported only on disk layout Version 6 and later. FCL stores changes in a sparse file in the file system namespace. The FCL file is located in mount_point/lost+found/changelog.
File Change Log File Change Log administrative interface File Change Log administrative interface The FCL can be set up and tuned through the fcladm and vxtunefs VxFS administrative commands. See the fcladm(1M) and vxtunefs(1M) manual pages. The FCL keywords for fcladm are as follows: clear Disables the recording of the audit, open, close, and statistical events after it has been set. dump Creates a regular file image of the FCL file that can be downloaded to an off-host processing system.
84 File Change Log File Change Log administrative interface fcl_keeptime Specifies the duration in seconds that FCL records stay in the FCL file before they can be purged. The first records to be purged are the oldest ones, which are located at the beginning of the file. Additionally, records at the beginning of the file can be purged if allocation to the FCL file exceeds fcl_maxalloc bytes. The default value of fcl_keeptime is 0.
File Change Log File Change Log programmatic interface # fcladm off mount_point To remove the FCL file for a mounted file system, on which FCL must be turned off, type the following: # fcladm rm mount_point To obtain the current FCL state for a mounted file system, type the following: # fcladm state mount_point To enable tracking of the file opens along with access information with each event in the FCL, type the following: # fcladm set fileopen,accessinfo mount_point To stop tracking file I/O statisti
86 File Change Log File Change Log programmatic interface Backward compatibility Providing API access for the FCL feature allows backward compatibility for applications. The API allows applications to parse the FCL file independent of the FCL layout changes. Even if the hidden disk layout of the FCL changes, the API automatically translates the returned data to match the expected output record.
File Change Log Summary of API functions } if (fclsb.
88 File Change Log Reverse path name lookup vxfs_fcl_seek() Extracts data from the specified cookie and then seeks to the specified offset. vxfs_fcl_seektime() Seeks to the first record in the FCL after the specified time. Reverse path name lookup The reverse path name lookup feature obtains the full path name of a file or directory from the inode number of that file or directory.
Chapter 7 Multi-volume file systems This chapter includes the following topics: ■ About multi-volume support ■ About volume types ■ Features implemented using multi-volume support ■ About volume sets ■ Creating multi-volume file systems ■ Converting a single volume file system to a multi-volume file system ■ Adding a volume to and removing a volume from a multi-volume file system ■ Volume encapsulation ■ Reporting file extents ■ Load balancing ■ Converting a multi-volume file system t
90 Multi-volume file systems About volume types The MVS feature also allows file systems to reside on different classes of devices, so that a file system can be supported from both inexpensive disks and from expensive arrays. Using the MVS administrative interface, you can control which data goes on which volume types. See the Veritas Volume Manager Administrator's Guide. Note: Multi-volume support is available only on file systems using disk layout Version 6 or later.
Multi-volume file systems Features implemented using multi-volume support ■ Separating metadata from file data. ■ Encapsulating volumes so that a volume appears in the file system as a file. This is particularly useful for databases that are running on raw volumes. ■ Guaranteeing that a dataonly volume being unavailable does not cause a metadataok volume to be unavailable.
92 Multi-volume file systems About volume sets Note: Do not mount a multi-volume system with the ioerror=disable or ioerror=wdisable mount options if the volumes have different availability properties. Symantec recommends the ioerror=mdisable mount option both for cluster mounts and for local mounts. About volume sets Veritas Volume Manager exports a data object called a volume set. A volume set is a container for one or more volumes, each of which can have its own geometry.
Multi-volume file systems Creating multi-volume file systems 3 93 List the component volumes of the previously created volume set: # vxvset -g dg1 list myvset 4 VOLUME vol1 INDEX 0 LENGTH 20480 STATE ACTIVE CONTEXT - vol2 vol3 1 2 102400 102400 ACTIVE ACTIVE - Use the ls command to see that when a volume set is created, the volumes contained by the volume set are removed from the namespace and are instead accessed through the volume set name: # ls -l /dev/vx/rdsk/rootdg/myvset crw------- 1 ro
94 Multi-volume file systems Creating multi-volume file systems Example of creating a multi-volume file system The following procedure is an example of creating a multi-volume file system.
Multi-volume file systems Converting a single volume file system to a multi-volume file system 4 List the volume availability flags using the fsvoladm command: # fsvoladm queryflags /mnt1 5 volname vol1 flags metadataok vol2 vol3 vol4 vol5 dataonly dataonly dataonly dataonly Increase the metadata space in the file system using the fsvoladm command: # fsvoladm clearflags dataonly /mnt1 vol2 # fsvoladm queryflags /mnt1 volname vol1 vol2 vol3 vol4 vol5 flags metadataok metadataok dataonly dataonly dat
96 Multi-volume file systems Adding a volume to and removing a volume from a multi-volume file system 4 If the disk layout version is less than 6, upgrade to Version 7.
Multi-volume file systems Adding a volume to and removing a volume from a multi-volume file system To add a volume to a multi-volume file system ◆ Add a new volume to a multi-volume file system: # fsvoladm add /mnt1 vol2 256m Removing a volume from a multi-volume file system Use the fsvoladm remove command to remove a volume from a multi-volume file system. The fsvoladm remove command fails if the volume being removed is the only volume in any allocation policy.
98 Multi-volume file systems Volume encapsulation Volume encapsulation Multi-volume support enables the ability to encapsulate an existing raw volume and make the volume contents appear as a file in the file system. Encapsulating a volume involves the following actions: ■ Adding the volume to an existing volume set. ■ Adding the volume to the file system using fsvoladm. Encapsulating a volume The following example illustrates how to encapsulate a volume.
Multi-volume file systems Volume encapsulation 5 Add the new volume to the volume set: # vxvset -g dg1 addvol myvset dbvol 6 Encapsulate dbvol: # fsvoladm encapsulate /mnt1/dbfile dbvol 100m # ls -l /mnt1/dbfile -rw------- 1 root other 104857600 May 22 11:30 /mnt1/dbfile 7 Examine the contents of dbfile to see that it can be accessed as a file: # head -2 /mnt1/dbfile root:x:0:1:Super-User:/:/sbin/sh daemon:x:1:1::/: The passwd file that was written to the raw volume is now visible in the new file.
100 Multi-volume file systems Reporting file extents Reporting file extents MVS feature provides the capability for file-to-volume mapping and volume-to-file mapping via the fsmap and fsvmap commands. The fsmap command reports the volume name, logical offset, and size of data extents, or the volume name and size of indirect extents associated with a file on a multi-volume file system. The fsvmap command maps volumes to the files that have extents on those volumes.
Multi-volume file systems Load balancing Using the fsvmap command 1 Report the extents of files on multiple volumes: # fsvmap /dev/vx/rdsk/fstest/testvset vol1 vol2 vol1 vol1 vol1 vol1 vol2 vol2 2 /.
102 Multi-volume file systems Load balancing Note: If a file has both a fixed extent size set and an allocation policy for load balancing, certain behavior can be expected. If the chunk size in the allocation policy is greater than the fixed extent size, all extents for the file are limited by the chunk size. For example, if the chunk size is 16 MB and the fixed extent size is 3 MB, then the largest extent that satisfies both the conditions is 15 MB.
Multi-volume file systems Converting a multi-volume file system to a single volume file system 103 To rebalance extents 1 Define the policy by specifying the -o balance and -c options: # fsapadm define -o balance -c 2m /mnt loadbal vol1 vol2 vol4 \ vol5 vol6 2 Enforce the policy: # fsapadm enforcefile -f strict /mnt/filedb Converting a multi-volume file system to a single volume file system Because data can be relocated among volumes in a multi-volume file system, you can convert a multi-volume file
104 Multi-volume file systems Converting a multi-volume file system to a single volume file system Converting to a single volume file system 1 Determine if the first volume in the volume set, which is identified as device number 0, has the capacity to receive the data from the other volumes that will be removed: # df /mnt1 /mnt1 2 (/dev/vx/dsk/dg1/vol1):16777216 blocks 3443528 files If the first volume does not have sufficient capacity, grow the volume to a sufficient size: # fsvoladm resize /mnt1 v
Chapter 8 Using Veritas Extension for Oracle Disk Manager This chapter includes the following topics: ■ About Oracle Disk Manager ■ About Oracle Disk Manager and Storage Foundation Cluster File System ■ About Oracle Disk Manager and Oracle Managed Files ■ Setting up Veritas Extension for Oracle Disk Manager ■ Preparing existing database storage for Oracle Disk Manager ■ Converting Quick I/O files to Oracle Disk Manager files ■ Verifying that Oracle Disk Manager is configured ■ Disabling the
106 Using Veritas Extension for Oracle Disk Manager About Oracle Disk Manager as to which regions or blocks of a mirrored datafile to resync after a system crash. Oracle Resilvering avoids overhead from the VxVM DRL, which increases performance. Oracle Disk Manager reduces administrative overhead by providing enhanced support for Oracle Managed Files. Veritas Extension for Oracle Disk Manager has Quick I/O-like capabilities, but is transparent to the user.
Using Veritas Extension for Oracle Disk Manager About Oracle Disk Manager How Oracle Disk Manager improves database performance Oracle Disk Manager improves database I/O performance to VxFS file systems by: ■ Supporting kernel asynchronous I/O ■ Supporting direct I/O and avoiding double buffering ■ Avoiding kernel write locks on database files ■ Supporting many concurrent I/Os in one system call ■ Avoiding duplicate opening of files per Oracle instance ■ Allocating contiguous datafiles About ke
108 Using Veritas Extension for Oracle Disk Manager About Oracle Disk Manager and Storage Foundation Cluster File System About supporting many concurrent I/Os in one system call When performing asynchronous I/O, an Oracle process may try to issue additional I/O requests while collecting completed I/Os, or it may try to wait for particular I/O requests synchronously, as it can do no other work until the I/O is completed. The Oracle process may also try to issue requests to different files.
Using Veritas Extension for Oracle Disk Manager About Oracle Disk Manager and Oracle Managed Files and whether or not the file is in use by the database. OMF is only supported for databases that reside in file systems. OMF functionality is greatly enhanced by Oracle Disk Manager.
110 Using Veritas Extension for Oracle Disk Manager About Oracle Disk Manager and Oracle Managed Files DB_CREATE_FILE_DEST = '/PROD' DB_CREATE_ONLINE_LOG_DEST_1 = '/PROD' db_block_size = 4096 db_name = PROD $ sqlplus /nolog SQL> connect / as sysdba SQL> startup nomount pfile= initPROD.ora The Oracle instance starts.
Using Veritas Extension for Oracle Disk Manager Setting up Veritas Extension for Oracle Disk Manager 111 SQL> ALTER SYSTEM SET DB_CREATE_FILE_DEST = '/PROD/EMP_INDEX'; The system is altered. SQL> create tablespace EMP_INDEX DATAFILE AUTOEXTEND ON MAXSIZE \ 100M; A tablespace is created.
112 Using Veritas Extension for Oracle Disk Manager Setting up Veritas Extension for Oracle Disk Manager Linking the Veritas extension for Oracle Disk Manager library into Oracle home If the Veritas extension for Oracle Disk Manager library is not linked into Oracle home, perform the following procedure. The steps vary depending on the Oracle version.
Using Veritas Extension for Oracle Disk Manager Preparing existing database storage for Oracle Disk Manager To link the Veritas extension for Oracle Disk Manager library into Oracle home for Oracle 10g 1 Shut down the database instance before linking the Oracle Disk Manager library. 2 Use the mv and ln commands: For HP-UX PA, enter: # mv ${ORACLE_HOME}/lib/libodm10.sl \ ${ORACLE_HOME}/lib/libodm10.sl.orig # ln -s /opt/VRTSodm/lib/libodm.sl \ ${ORACLE_HOME}/lib/libodm10.
114 Using Veritas Extension for Oracle Disk Manager Verifying that Oracle Disk Manager is configured Note: If you are running an earlier version of Oracle (Oracle 8.x or lower), you should not convert your Quick I/O files because Oracle Disk Manager is for Oracle10g or later only. The Oracle Disk Manager uses the Quick I/O driver to perform asynchronous I/O, do not turn off the Quick I/O mount option, which is the default.
Using Veritas Extension for Oracle Disk Manager Verifying that Oracle Disk Manager is configured 115 To verify that Oracle Disk Manager is configured 1 Verify that the ODM feature is included in the license: # /opt/VRTS/bin/vxlicrep | grep ODM The output verifies that ODM is enabled. Note: Verify that the license key containing the ODM feature is not expired. If the license key has expired, you will not be able to use the ODM feature.
116 Using Veritas Extension for Oracle Disk Manager Disabling the Oracle Disk Manager feature 3 Verify that the Oracle Disk Manager is loaded: # /usr/sbin/kcmodule -P state odm state loaded 4 In the alert log, verify the Oracle instance is running. The log should contain output similar to the following: Oracle instance running with ODM: Veritas 5.1.100.00 ODM Library, Version 2.
Using Veritas Extension for Oracle Disk Manager Using Cached ODM To disable the Oracle Disk Manager feature in an Oracle instance 1 Shut down the database instance. 2 Use the rm and ln commands to remove the link to the Oracle Disk Manager Library. For Oracle 11g, enter: For HP Integrity systems, enter: # rm ${ORACLE_HOME}/lib/libodm9.sl # ln -s ${ORACLE_HOME}/lib/libodmd9.sl \ ${ORACLE_HOME}/lib/libodm9.sl For HP 9000 systems, enter: # rm ${ORACLE_HOME}/lib/limodm9.
118 Using Veritas Extension for Oracle Disk Manager Using Cached ODM does with the data. ODM uses these hints to perform caching and read ahead for some reads, but ODM avoids caching other reads, even for the same file. You can enable cached ODM for local mount files and cluster mount files. See “Enabling Cached ODM for file systems” on page 118. Cached ODM can be configured in two ways. The primary configuration method is to turn caching on or off for all I/O on a per-file basis.
Using Veritas Extension for Oracle Disk Manager Using Cached ODM ON caching state causes the specified file always to be cached, while the OFF caching state causes the specified file never to be cached. See the odmadm(1M) manual page. Note: The cache advisories operate only if Cached ODM is enabled for the file system. If the odm_cache_enable flag is zero, Cached ODM is OFF for all of the files in that file system, even if the individual file cache advisory for a file is ON.
120 Using Veritas Extension for Oracle Disk Manager Using Cached ODM See the odmadm(1M) manual page. By default, the cachemap is empty, but you can add caching advisories by using the odmadm setcachemap command. To add caching advisories to the cachemap ◆ Add a caching advisory to the cachemap: # odmadm setcachemap data/data_read_seq=cache,readahead With this example command, ODM uses caching and readahead for I/O to online log files (data) that have the data_read_seq I/O type.
Appendix A Quick Reference This appendix includes the following topics: ■ Command summary ■ Online manual pages ■ Creating a VxFS file system ■ Converting a file system to VxFS ■ Mounting a file system ■ Unmounting a file system ■ Displaying information on mounted file systems ■ Identifying file system types ■ Resizing a file system ■ Using quotas Command summary Symbolic links to all VxFS command executables are installed in the /opt/VRTS/bin directory.
122 Quick Reference Command summary Table A-1 VxFS commands (continued) Command Description diskusg Generates VxFS disk accounting data by user ID. extendfs Extends the size of a VxFS file system. fcladm Administers VxFS File Change Logs. ff Lists file names and inode information for a VxFS file system. fiostat Administers file I/O statistics fsadm Resizes or defragments a VxFS file system. fsapadm Administers VxFS allocation policies. fscat Cats a VxFS file system.
Quick Reference Command summary Table A-1 VxFS commands (continued) Command Description fsvoladm Administers VxFS volumes. glmconfig Configures Group Lock Managers (GLM). glmstat Group Lock Managers (GLM) statistics gathering utility. mkdstfs SmartTier file system creation utility. mkfs Constructs a VxFS file system. mount Mounts a VxFS file system. ncheck Generates path names from inode numbers for a VxFS file system. newfs Creates a new VxFS file system.
124 Quick Reference Online manual pages Table A-1 VxFS commands (continued) Command Description vxtunefs Tunes a VxFS file system. vxumount Unmounts a VxFS file system. vxupgrade Upgrades the disk layout of a mounted VxFS file system. Online manual pages This release includes the following online manual pages as part of the VRTSvxfs package.
Quick Reference Online manual pages Table A-3 Section 1M manual pages Section 1M Description df_vxfs Reports the number of free disk blocks and inodes for a VxFS file system. extendfs_vxfs Extends the size of a VxFS file system. fcladm Administers VxFS File Change Logs. ff_vxfs Lists file names and inode information for a VxFS file system. fsadm_vxfs Resizes or reorganizes a VxFS file system. fsapadm Administers VxFS allocation policies. fscat_vxfs Cats a VxFS file system.
126 Quick Reference Online manual pages Table A-3 Section 1M manual pages (continued) Section 1M Description ncheck_vxfs Generates path names from inode numbers for a VxFS file system. newfs_vxfs Creates a new VxFS file system. quot Summarizes ownership on a VxFS file system. quotacheck_vxfs Checks VxFS file system quota consistency. vxdiskusg Generates VxFS disk accounting data by user ID. vxdump Incrementally dumps file systems. vxenablef Enables specific VxFS features.
Quick Reference Online manual pages Table A-4 Section 3 manual pages (continued) Section 3 Description fsckpt_fpromote Promotes a file from a Storage Checkpoint into another fileset. fsckpt_fsclose Closes a mount point opened for Storage Checkpoint management. fsckpt_fsopen Opens a mount point for Storage Checkpoint management. fsckpt_info Returns status information on a Storage Checkpoint. fsckpt_intro Introduces the VxFS file system Storage Checkpoint API.
128 Quick Reference Online manual pages Table A-4 Section 3 manual pages (continued) Section 3 Description vxfs_ap_assign_fs_pat Assigns an pattern-based allocation policy for a file system. vxfs_ap_define Defines a new allocation policy. vxfs_ap_define2 Defines a new allocation policy. vxfs_ap_enforce_ckpt Reorganizes blocks in a Storage Checkpoint to match a specified allocation policy.
Quick Reference Online manual pages Table A-4 Section 3 manual pages (continued) Section 3 Description vxfs_fcl_sync Sets a synchronization point in the VxFS File Change Log. vxfs_fiostats_dump Returns file and file range I/O statistics. vxfs_fiostats_getconfig Gets file range I/O statistics configuration values. vxfs_fiostats_set Turns on and off file range I/O statistics and resets statistics counters. vxfs_get_ioffsets Obtains VxFS inode field offsets.
130 Quick Reference Creating a VxFS file system Table A-4 Section 3 manual pages (continued) Section 3 Description vxfs_vol_setflags Sets specified flags on volumes in a multi-volume file system. vxfs_vol_stat Returns free space information about a component volume within a multi-volume file system. Table A-5 describes the VxFS-specific section 4 manual pages. Table A-5 Section 4 manual pages Section 4 Description fs_vxfs Provides the format of a VxFS file system volume.
Quick Reference Creating a VxFS file system 131 To create a file system ◆ Use the mkfs command to create a file system: mkfs [-F vxfs] [-m] [generic_options] [-o specific_options] \ special [size] -F vxfs Specifies the VxFS file system type. -m Displays the command line that was used to create the file system. The file system must already exist. This option enables you to determine the parameters used to construct the file system. generic_options Options common to most other file system types.
132 Quick Reference Converting a file system to VxFS Converting a file system to VxFS The vxfsconvert command can be used to convert a HFS file system to a VxFS file system. See the vxfsconvert(1M) manual page. To convert a HFS file system to a VxFS file system ◆ Use the vxfsconvert command to convert a HFS file system to VxFS: vxfsconvert [-l logsize] [-s size] [-efnNvyY] special -e Estimates the amount of space required to complete the conversion.
Quick Reference Mounting a file system and Veritas-installed products, the generic mount command executes the VxFS mount command from the directory /sbin/fs/vxfs. If the -F option is not supplied, the command searches the file /etc/fstab for a file system and an fstype matching the special file or mount point provided. If no file system type is specified, mount uses the default file system type (VxFS).
134 Quick Reference Mounting a file system Support for large files If you specify the largefiles option, you can create files larger than two gigabytes on the file system. The default option is largefiles. Support for cluster file If you specify the cluster option, the file system is mounted in systems shared mode. HP Serviceguard Storage Management Suite environments require HP Serviceguard to be configured correctly before a complete clustering environment is enabled.
Quick Reference Unmounting a file system To mount the file system ◆ Mount the file system: # mount -F vxfs -o delaylog /dev/vx/dsk/fsvol/vol1 /mnt1 Editing the fstab file You can edit the /etc/fstab file to mount a file system automatically at boot time.
136 Quick Reference Displaying information on mounted file systems To unmount a file system ◆ Use the umount command to unmount a file system: vxumount [-o [force]] {special|mount_point} Specify the file system to be unmounted as a mount_point or special. special is the VxFS block special device on which the file system resides. Example of unmounting a file system The following are examples of unmounting file systems.
Quick Reference Identifying file system types To display information on mounted file systems ◆ Invoke the mount command without options: # mount /dev/vg00/lvol3 on / type vxfs ioerror=mwdisable,delaylog \ Wed Jun 5 3:23:40 2004 /dev/vg00/lvol8 on /var type vxfs ioerror=mwdisable,delaylog Wed Jun 5 3:23:56 2004 /dev/vg00/lvol7 on /usr type vxfs ioerror=mwdisable,delaylog Wed Jun 5 3:23:56 2004 /dev/vg00/lvol6 on /tmp type vxfs ioerror=mwdisable,delaylog Wed Jun 5 3:23:56 2004 /dev/vg00/lvol5 on /opt type v
138 Quick Reference Resizing a file system Example of determining a file system's type The following example uses the fstyp command to determine the file system type of the /dev/vx/dsk/fsvol/vol1 device.
Quick Reference Resizing a file system To extend a VxFS file system ◆ Use the fsadm command to extend a VxFS file system: fsadm [-F vxfs] [-b newsize] [-r rawdev] \ mount_point vxfs The file system type. newsize The size to which the file system will increase. The default units is sectors, but you can specify k or K for kilobytes, m or M for megabytes, or g or G for gigabytes. mount_point The file system's mount point.
140 Quick Reference Resizing a file system To decrease the size of a VxFS file system ◆ Use the fsadm command to decrease the size of a VxFS file system: fsadm [-F vxfs] [-b newsize] [-r rawdev] mount_point vxfs The file system type. newsize The size to which the file system will shrink. The default units is sectors, but you can specify k or K for kilobytes, m or M for megabytes, or g or G for gigabytes. mount_point The file system's mount point.
Quick Reference Resizing a file system vxfs The file system type. -d Reorders directory entries to put subdirectory entries first, then all other entries in decreasing order of time of last access. Also compacts directories to remove free space. -D Reports on directory fragmentation. -e Minimizes file system fragmentation. Files are reorganized to have the minimum number of extents. -E Reports on extent fragmentation. mount_point The file system's mount point.
142 Quick Reference Using quotas special Either a logical volume or a disk partition Note: If the file system resides on a volume set, the extendfs command fails. Use the fsvoladm command to extend a multi-volume file system. See the fsvoladm(1M) manual page. Example of extending a VxFS file system The following example extends a VxFS file system on a VxVM volume.
Quick Reference Using quotas To turn on quotas 1 Turn on quotas for a mounted file system: quotaon mount_point 2 Mount a file system and turn on quotas at the same time: mount -F vxfs -o quota special mount_point If the root directory does not contain a quotas file, the mount command succeeds, but quotas are not turned on. Example of turning on quotas for a mounted file system The following example creates a quoatas file and turns on quotas for a VxFS file system mounted at /mnt.
144 Quick Reference Using quotas edquota creates a temporary file for a specified user. This file contains on-disk quotas for each mounted VxFS file system that has a quotas file. The temporary file has one or more lines similar to the following: fs /mnt blocks (soft = 0, hard = 0) inodes (soft=0, hard=0) fs /mnt1 blocks (soft = 100, hard = 200) inodes (soft=10, hard=20) Quotas do not need to be turned on for edquota to work.
Appendix B 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: Marking an inode bad Inodes can be marked bad if an inode update or a directory-block update fails.
146 Diagnostic messages About kernel messages Disabling a 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.
Diagnostic messages Kernel messages 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.
148 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 002 WARNING: msgcnt x: mesg 002: V-2-2: vx_snap_strategy - mount_point file system write attempt to read-only file system WARNING: msgcnt x: mesg 002: V-2-2: vx_snap_copyblk - mount_point file system write attempt to read-only file system Description 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.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 006, 007 WARNING: msgcnt x: mesg 006: V-2-6: vx_sumupd - mount_point file system summary update in au aun failed WARNING: msgcnt x: mesg 007: V-2-7: vx_sumupd - mount_point file system summary update in inode au iaun failed Description 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.
150 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 010 WARNING: msgcnt x: mesg 010: V-2-10: vx_ialloc - mount_point file system inode inumber not free Description 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.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 013 WARNING: msgcnt x: mesg 013: V-2-13: vx_iposition - mount_point file system inode inumber invalid inode list extent Description 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 cannot be accessed.
152 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 015 WARNING: msgcnt x: mesg 015: V-2-15: vx_ibadinactive - mount_point file system cannot mark inode inumber bad WARNING: msgcnt x: mesg 015: V-2-15: vx_ilisterr - mount_point file system cannot mark inode inumber bad Description An attempt to mark an inode bad on disk, and the super-block update to set the VX_FULLFSCK flag, failed.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 017 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_p
154 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 017 (continued) 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 -
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 017 (continued) 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 Description When inode information is no longer dependable, the kernel marks it bad in memory.
156 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 019 WARNING: msgcnt x: mesg 019: V-2-19: vx_log_add - mount_point file system log overflow Description 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.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 021 WARNING: msgcnt x: mesg 021: V-2-21: vx_fs_init - mount_point file system validation failure ■ Description 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.
158 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 022 WARNING: msgcnt x: mesg 022: V-2-22: vx_mountroot - root file system remount failed Description The remount of the root file system failed. The system will not be usable if the root file system cannot be remounted for read/write access. When a root Veritas File System is first mounted, it is mounted for read-only access.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 024 WARNING: msgcnt x: mesg 024: V-2-24: vx_cutwait - mount_point file system current usage table update error Description 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.
160 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 027 WARNING: msgcnt x: mesg 027: V-2-27: vx_snap_bpcopy - mount_point snapshot file system write error Description 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.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 029, 030 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 Description During a snapshot backup, each snapshot file system maintains a block map on disk.
162 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 033 WARNING: msgcnt x: mesg 033: V-2-33: vx_check_badblock mount_point file system had an I/O error, setting VX_FULLFSCK Description 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.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 036 WARNING: msgcnt x: mesg 036: V-2-36: vx_lctbad - mount_point file system link count table lctnumber bad Description 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 cannot be written, the file system is disabled.
164 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 038 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 Description 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.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 039 WARNING: msgcnt x: mesg 039: V-2-39: vx_writesuper - file system super-block write error Description 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.
166 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 056 WARNING: msgcnt x: mesg 056: V-2-56: vx_mapbad - mount_point file system extent allocation unit state bitmap number number marked bad Description 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.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 058 WARNING: msgcnt x: mesg 058: V-2-58: vx_isum_bad - mount_point file system inode allocation unit summary number number marked bad Description 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. ■ Action Check the console log for I/O errors.
168 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 060 WARNING: msgcnt x: mesg 060: V-2-60: vx_snap_getbitbp mount_point snapshot file system bitmap read error Description 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.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 063 WARNING: msgcnt x: mesg 063: V-2-63: vx_fset_markbad mount_point file system mount_point fileset (index number) marked bad Description An error occurred while reading or writing a fileset structure. VX_FULLFSCK flag is set. If the VX_FULLFSCK flag cannot be set, the file system is disabled. ■ Action Unmount the file system and use fsck to run a full structural check.
170 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 067 WARNING: msgcnt x: mesg 067: V-2-67: mount of device_path requires HSM agent Description The file system mount failed because the file system was marked as being under the management of an HSM agent, and no HSM agent was found during the mount. ■ Action Restart the HSM agent and try to mount the file system again.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 071 NOTICE: msgcnt x: mesg 071: V-2-71: cleared data I/O error flag in mount_point file system Description 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 while the file system was previously mounted. See Message Number 038. ■ Action Informational only, no action required.
172 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 076 NOTICE: msgcnt x: mesg 076: V-2-76: checkpoint asynchronous operation on mount_point file system still in progress ■ Description 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.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 079 173
174 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 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_p
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition file system inode inumber marked bad on disk 079 (continued) 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: msgcn
176 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 079 (continued) ■ 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.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 081 WARNING: msgcnt x: mesg 081: V-2-81: possible network partition detected Description 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. ■ Action There are one or more private network links for communication between the nodes in a cluster.
178 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 084 WARNING: msgcnt x: mesg 084: V-2-84: in volume_name quota on failed during assumption. (stage stage_number) Description 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.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 088 WARNING: msgcnt x: mesg 088: V-2-88: quotaon on file_system failed; limits exceed limit Description The external quota file, quotas, contains the quota values, which range from 0 up to 2147483647. When quotas are turned on by the quotaon command, this message displays when a user exceeds the quota limit. ■ Action Correct the quota values in the quotas file.
180 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 092 WARNING: msgcnt x: mesg 092: V-2-92: vx_mkfcltran - failure to map offset offset in File Change Log file Description The vxfs kernel was unable to map actual storage to the next offset in the File Change Log file. This is mostly likely caused by a problem with allocating to the FCL file. Because no new FCL records can be written to the FCL file, the FCL has been deactivated.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 098 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 Description VxFS mount failed to initialize FCL structures for the current fileset mount. As a result, FCL could not be turned on. The FCL file will have no logging records. ■ Action Reactivate the FCL.
182 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 101 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. ■ Description The size of the FCL file is approching the maximum file size supported. This size is platform specific.
Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 104 WARNING: msgcnt x: mesg 104: V-2-104: File System mount_point device volume_name disabled ■ Description The volume manager detected that the specified volume has failed, and the volume manager has disabled the volume. No further I/O requests are sent to the disabled volume. ■ 105 Action The volume must be repaired.
184 Diagnostic messages Kernel messages Table B-1 Kernel messages (continued) Message Number Message and Definition 108 WARNING: msgcnt x: mesg 108: V-2-108: vx_dexh_error - error: fileset fileset, directory inode number dir_inumber, bad hash inode hash_inode, seg segment bno block_number ■ Description The supplemental hash for a directory is corrupt. ■ 109 Action If the file system is mounted read/write, the hash for the directory will be automatically removed and recreated.
Diagnostic messages About unique message identifiers Table B-1 Kernel messages (continued) Message Number Message and Definition 111 WARNING: msgcnt x: mesg 111: V-2-111: You have exceeded the authorized usage (maximum maxfs unique mounted user-data file systems) for this product and are out of compliance with your License Agreement. Please email sales_mail@symantec.com or contact your Symantec sales representative for information on how to obtain additional licenses for this product.
186 Diagnostic messages Unique message identifiers Unique message identifiers Some commonly encountered UMIs and the associated messages are described on the following table: Table B-2 Unique message identifiers and messages Message Number Message and Definition 20002 UX:vxfs command: ERROR: V-3-20002: message Description The command attempted to call stat() on a device path to ensure that the path refers to a character device before opening the device, but the stat() call failed.
Diagnostic messages Unique message identifiers Table B-2 Unique message identifiers and messages (continued) Message Number Message and Definition 20076 UX:vxfs command: ERROR: V-3-20076: message Description The command called stat() on a file, which is usually a file system mount point, but the call failed. ■ Action Check that the path specified is what was intended and that the user has permission to access that path.
188 Diagnostic messages Unique message identifiers Table B-2 Unique message identifiers and messages (continued) Message Number Message and Definition 21268 UX:vxfs command: ERROR: V-3-21268: message Description This message is printed by two different commands: fsckpt_restore and mount. In both cases, the kernel's attempt to mount the file system failed because of I/O errors or corruption of the VxFS metadata. ■ Action Check the console log for I/O errors and fix any problems reported there.
Diagnostic messages Dewey kernel messages Dewey kernel messages This section contains all the Kernel error code sources in Dewey format. V-2-1 NOTICE: msgcnt x: mesg 001: V-2-1: vx_nospace - mount_point file system full (n block extent) Description: The file system is out of space. Often, there is plenty of space and one runaway process used up all the remaining free space. In other cases, the available free space becomes fragmented and unusable for some files.
190 Diagnostic messages Dewey kernel messages V-2-3 WARNING: msgcnt x: mesg 003: V-2-3: vx_mapbad - mount_point file system free extent bitmap in au aun marked bad Description: 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.
Diagnostic messages Dewey kernel messages 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 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.
192 Diagnostic messages Dewey kernel messages Recommended 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. V-2-7 WARNING: msgcnt x: mesg 007: V-2-7: vx_sumupd - mount_point file system summary update in inode au iaun failed Description: An I/O error occurred while writing the allocation unit or inode allocation unit bitmap summary to disk.
Diagnostic messages Dewey kernel messages V-2-9 WARNING: msgcnt x: mesg 009: V-2-9: vx_direrr: function - mount_point file system dir inode dir_inumber dirent inode dirent_inumber immediate directory error errno Description: 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.
194 Diagnostic messages Dewey kernel messages The file system is out of inodes. Recommended 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. See the fsadm_vxfs(1M) online manual page.
Diagnostic messages Dewey kernel messages Description: All the system in-memory inodes are busy and an attempt was made to use a new inode. Recommended 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 vx_ninode parameter in the kernel. See “Tuning the VxFS file system” on page 45.
196 Diagnostic messages Dewey kernel messages V-2-17 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: msgc
Diagnostic messages Dewey kernel messages 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
198 Diagnostic messages Dewey kernel messages 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.
Diagnostic messages Dewey kernel messages V-2-20 WARNING: msgcnt x: mesg 020: V-2-20: vx_logerr - mount_point file system log error errno Description: 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 cannot be updated, the file system is disabled. Recommended action: Unmount the file system and use fsck to run a full structural check. Check the console log for I/O errors.
200 Diagnostic messages Dewey kernel messages The remount of the root file system failed. The system will not be usable if the root file system cannot be remounted for read/write access. When a root Veritas 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.
Diagnostic messages Dewey kernel messages V-2-24 WARNING: msgcnt x: mesg 024: V-2-24: vx_cutwait - mount_point file system current usage table update error Description: 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 cannot be written, the file system is disabled.
202 Diagnostic messages Dewey kernel messages 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. V-2-27 WARNING: msgcnt x: mesg 027: V-2-27: vx_snap_bpcopy - mount_point snapshot file system write error Description: A write to the snapshot file system failed.
Diagnostic messages Dewey kernel messages V-2-29 WARNING: msgcnt x: mesg 029: V-2-29: vx_snap_getbp - mount_point snapshot file system block map write error Description: 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.
204 Diagnostic messages Dewey kernel messages V-2-32 WARNING: msgcnt x: mesg 032: V-2-32: vx_disable - mount_point snapshot file system disabled Description: Snapshot file system disabled, preceded by a message that specifies the reason. Recommended action: Unmount the snapshot file system, correct the problem specified by the message, and rerun any backups that failed due to the error.
Diagnostic messages Dewey kernel messages V-2-35 WARNING: msgcnt x: mesg 035: V-2-35: vx_inactive - mount_point file system inactive of locked inode inumber Description: 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. Recommended action: Unmount the file system and use fsck to run a full structural check. Report as a bug to your customer support organization.
206 Diagnostic messages Dewey kernel messages 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).
Diagnostic messages Dewey kernel messages Description: 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.
208 Diagnostic messages Dewey kernel messages V-2-57 WARNING: msgcnt x: mesg 057: V-2-57: vx_esum_bad - mount_point file system extent allocation unit summary number number marked bad Description: An I/O error occurred reading or writing an extent allocation unit summary. The VX_FULLFSCK flag is set. If the VX_FULLFSCK flag cannot be set, the file system is disabled. Recommended action: Check the console log for I/O errors. If the problem is a disk failure, replace the disk.
Diagnostic messages Dewey kernel messages 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.
210 Diagnostic messages Dewey kernel messages Recommended action: Determine which vendor supplied the registered extended attribute intervention routine and contact their customer support organization. V-2-63 WARNING: msgcnt x: mesg 063: V-2-63: vx_fset_markbad - mount_point file system mount_point fileset (index number) marked bad Description: An error occurred while reading or writing a fileset structure. VX_FULLFSCK flag is set. If the VX_FULLFSCK flag cannot be set, the file system is disabled.
Diagnostic messages Dewey kernel messages Recommended action: Consult the HSM product documentation for the appropriate response to the message. V-2-67 WARNING: msgcnt x: mesg 067: V-2-67: mount of device_path requires HSM agent Description: The file system mount failed because the file system was marked as being under the management of an HSM agent, and no HSM agent was found during the mount. Recommended action: Restart the HSM agent and try to mount the file system again.
212 Diagnostic messages Dewey kernel messages 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. V-2-71 NOTICE: msgcnt x: mesg 071: V-2-71: cleared data I/O error flag in mount_point file system Description: The user data I/O error flag was reset when the file system was mounted.
Diagnostic messages Dewey kernel messages Unmount the file system from the cluster. Use fsck to run a full structural check and mount the file system again. V-2-76 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.
214 Diagnostic messages Dewey kernel messages Unmount the file system and use fsck to run a full structural check.
Diagnostic messages Dewey kernel messages 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:
216 Diagnostic messages Dewey kernel messages 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.
Diagnostic messages Dewey kernel messages V-2-81 WARNING: msgcnt x: mesg 081: V-2-81: possible network partition detected Description: 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. Recommended action: 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.
218 Diagnostic messages Dewey kernel messages 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. V-2-84 WARNING: msgcnt x: mesg 084: V-2-84: in volume_name quota on failed during assumption.
Diagnostic messages Dewey kernel messages V-2-87 WARNING: msgcnt x: mesg 087: V-2-87: vx_dotdot_manipulate: file_system file system inumber inode ddnumber dotdot inode error Description: When performing an operation that changes an inode entry, if the inode is incorrect, this message will display. Recommended action: Run a full file system check using fsck to correct the errors.
220 Diagnostic messages Dewey kernel messages One or more users or groups has a soft limit set greater than the hard limit, preventing the BSD quota from being turned on. Recommended action: Check the soft limit and hard limit for every user and group and confirm that the soft limit is not set greater than the hard limit.
Diagnostic messages Dewey kernel messages Recommended action: Informational only; no action required. V-2-96 WARNING: msgcnt x: mesg 096: V-2-96: file_system file system fullfsck flag set function_name. Description: The next time the file system is mounted, a full fsck must be performed. Recommended action: No immediate action required. When the file system is unmounted, run a full file system check using fsck before mounting it again.
222 Diagnostic messages Dewey kernel messages V-2-99 WARNING: msgcnt x: mesg 099: V-2-99: The specified value for vx_ninode is less than the recommended minimum value of min_value Description: 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).
Diagnostic messages Dewey kernel messages Take any corrective action possible to restrict the loss due to the FCL being deactivated and reactivated. V-2-102 WARNING: msgcnt x: mesg 102: V-2-102: File Change Log of mount_point for file set index has been reactivated. Description: 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.
224 Diagnostic messages Dewey kernel messages The volume must be repaired. V-2-105 WARNING: msgcnt x: mesg 105: V-2-105: File System mount_point device volume_name re-enabled Description: The volume manager detected that a previously disabled volume is now operational, and the volume manager has re-enabled the volume. Recommended action: Informational only; no action required.
Diagnostic messages Dewey kernel messages V-2-108 WARNING: msgcnt x: mesg 108: V-2-108: vx_dexh_error - error: fileset fileset, directory inode number dir_inumber, bad hash inode hash_inode, seg segment bno block_number Description: The supplemental hash for a directory is corrupt. Recommended action: If the file system is mounted read/write, the hash for the directory will be automatically removed and recreated. If the removal or recreation fails, subsequent messages indicate the type of prolem.
226 Diagnostic messages Dewey UMI messages Recommended action: Tune the vx_bc_bufhwm tunable to a value greater than the recommended minimum indicated by the warning message. V-2-111 WARNING: msgcnt x: mesg 111: V-2-111: You have exceeded the authorized usage (maximum maxfs unique mounted user-data file systems) for this product and are out of compliance with your License Agreement. Please email sales_mail@symantec.
Diagnostic messages Dewey UMI messages V-3-20002 UX:vxfs command: ERROR: V-3-20002: message Description: The command attempted to call stat() on a device path to ensure that the path refers to a character device before opening the device, but the stat() call failed. The error message will include the platform-specific message for the particular error that was encountered, such as "Access denied" or "No such file or directory". Recommended action: The corrective action depends on the particular error.
228 Diagnostic messages Dewey UMI messages The command was invoked on a device that did not contain a valid VxFS file system. Recommended action: Check that the path specified is what was intended. V-3-20076 UX:vxfs command: ERROR: V-3-20076: message Description: The command called stat() on a file, which is usually a file system mount point, but the call failed. Recommended action: Check that the path specified is what was intended and that the user has permission to access that path.
Diagnostic messages Dewey UMI messages One reason that the mount point could be busy is if a process has the directory open or has the directory as its current directory. Another reason that the mount point could be busy is if the directory is NFS-exported.
230 Diagnostic messages Dewey UMI messages Cluster mounts require the vxfsckd daemon to be running, which is controlled by Veritas Cluster Server (VCS). Recommended action: Check the VCS status to see why this service is not running. After starting the daemon via VCS, try the mount again.
Appendix C Disk layout This appendix includes the following topics: ■ About disk layouts ■ Supported disk layouts and operating systems ■ VxFS Version 4 disk layout ■ VxFS Version 5 disk layout ■ VxFS Version 6 disk layout ■ VxFS Version 7 disk layout ■ VxFS Version 8 disk layout About disk layouts The disk layout is the way file system information is stored on disk. On VxFS, several different disk layout versions were created to take advantage of evolving technological developments.
232 Disk layout About disk layouts Version 3 Version 3 disk layout encompasses all file system structural information in files, rather than at fixed locations on disk, allowing for greater scalability. Version 3 supports files and file systems up to one terabyte in size. Not Supported Version 4 Version 4 disk layout encompasses all file system structural information in files, rather than at fixed locations on disk, allowing for greater scalability.
Disk layout Supported disk layouts and operating systems Version 7 Version 7 disk layout enables support for variable and Supported large size history log records, more than 2048 volumes, large directory hash, and SmartTier. Version 8 Version 8 disk layout enables support for file-level snapshots. Supported Some of the disk layout versions were not supported on all UNIX operating systems.
234 Disk layout Supported disk layouts and operating systems File system type and operating system versions (continued) Table C-1 JFS 3.3, VxFS 3.5, HP-UX HP-UX 11i v1 11i v1 Disk Layout Version 2 Version 3 Version 4 Version 5 Version 6 VxFS VxFS 4.1, VxFS 5.0, VxFS 5.0, VxFS 5.0.1 3.5.2, HP-UX HP-UX HP-UX 11i and 5.
Disk layout VxFS Version 4 disk layout File system type and operating system versions (continued) Table C-1 JFS 3.3, VxFS 3.5, HP-UX HP-UX 11i v1 11i v1 Disk Layout Version 7 Version 8 VxFS VxFS 4.1, VxFS 5.0, VxFS 5.0, VxFS 5.0.1 3.5.2, HP-UX HP-UX HP-UX 11i and 5.
236 Disk layout VxFS Version 4 disk layout The Version 4 file system also moves away from the model of storing AU structural data at the start of an AU and puts all structural information in files. So expanding the file system structures simply requires extending the appropriate structural files. This removes the extent size restriction imposed by the previous layouts. All Version 4 structural files reside in the structural fileset.
Disk layout VxFS Version 4 disk layout File Description free extent map file Contains the free extent maps for each of the allocation units. quotas files Contains quota information in records. Each record contains resources allocated either per user. The Version 4 disk layout supports Access Control Lists and Block-Level Incremental (BLI) Backup. BLI Backup is a backup method that stores and retrieves only the data blocks changed since the previous backup, not entire files.
238 Disk layout VxFS Version 5 disk layout VxFS Version 4 disk layout Figure C-1 Super-block Object Location Table OLT Extent Addresses Initial Inode Extents Fileset Header/ File Inode Number Fileset Header File Inode Initial Inode List Extent Addresses Inode List Inode Inode Allocation Unit Inode .... .... OLT Replica Primary Fileset Header Fileset Header File Inode List inum Structural Fileset Header Fileset Index and Name Primary Fileset Header max_inodes Features .... ....
Disk layout VxFS Version 6 disk layout Block Size Maximum File System Size 2048 bytes 8,589,934,078 sectors (≈8 TB) 4096 bytes 17,179,868,156 sectors (≈16 TB) 8192 bytes 34,359,736,312 sectors (≈32 TB) If you specify the file system size when creating a file system, the block size defaults to the appropriate value as shown above. See the mkfs(1M) manual page. See “About quota files on Veritas File System” on page 78. The Version 5 disk layout also supports up to 1024 access control list entries.
240 Disk layout VxFS Version 7 disk layout See “About quota files on Veritas File System” on page 78. VxFS Version 7 disk layout VxFS disk layout Version 7 is similar to Version 6, except that Version 7 enables support for variable and large size history log records, more than 2048 volumes, large directory hash, and SmartTier. The Version 7 disk layout can theoretically support files and file systems up to 8 exabytes (263).
Disk layout VxFS Version 8 disk layout kernels, the maximum size of the file system you can create depends on the block size: Block Size Currently-Supported Theoretical Maximum File System Size 1024 bytes 68,719,472,624 sectors (≈32 TB) 2048 bytes 137,438,945,248 sectors (≈64 TB) 4096 bytes 274,877,890,496 sectors (≈128 TB) 8192 bytes 549,755,780,992 sectors (≈256 TB) Note: Sector size in bytes specified by the DEV_BSIZE system parameter.
242 Disk layout VxFS Version 8 disk layout
Glossary access control list (ACL) The information that identifies specific users or groups and their access privileges for a particular file or directory. agent A process that manages predefined Veritas Cluster Server (VCS) resource types. Agents bring resources online, take resources offline, and monitor resources to report any state changes to VCS. When an agent is started, it obtains configuration information from VCS and periodically monitors the resources and updates VCS with the resource status.
244 Glossary on the disk before the write returns, but the inode modification times may be lost if the system crashes. defragmentation The process of reorganizing data on disk by making file data blocks physically adjacent to reduce access times. direct extent An extent that is referenced directly by an inode. direct I/O An unbuffered form of I/O that bypasses the kernel’s buffering of data. With direct I/O, the file system transfers data directly between the disk and the user-supplied buffer.
Glossary inode A unique identifier for each file within a file system that contains the data and metadata associated with that file. inode allocation unit A group of consecutive blocks containing inode allocation information for a given fileset. This information is in the form of a resource summary and a free inode map. intent logging A method of recording pending changes to the file system structure. These changes are recorded in a circular intent log file.
246 Glossary quotas file The quotas commands read and write the external quotas file to get or change usage limits. When quotas are turned on, the quota limits are copied from the external quotas file to the internal quotas file. See quotas, internal quotas file, and external quotas file. reservation An extent attribute used to preallocate space for a file. root disk group A special private disk group that always exists on the system. The root disk group is named rootdg.
Glossary volume A virtual disk which represents an addressable range of disk blocks used by applications such as file systems or databases. volume set A container for multiple different volumes. Each volume can have its own geometry. vxfs The Veritas File System type. Used as a parameter in some commands. VxFS Veritas File System. VxVM Veritas Volume Manager.
248 Glossary
Index A D access control lists 24 allocation policies 64 default 64 extent 19 extent based 19 data copy 70 data integrity 23 data synchronous I/O 39, 71 data transfer 70 default allocation policy 64 block size 19 default_indir_size tunable parameter 55 defragmentation 31 extent 50 scheduling with cron 50 delaylog mount option 36 device file 236 direct data transfer 70 direct I/O 70 directory reorganization 51 disabled file system transactions 145 disabling Concurrent I/O 75 discovered direct I/O 71 disc
250 Index ENOTDIR 149, 192–193 expansion 32 extent 19, 63 attributes 63 indirect 19 reorganization 51 extent allocation 19 aligned 64 control 63 fixed size 63 unit state file 236 unit summary file 236 extent size indirect 19 external quotas file 78 F fc_foff 84 fcl_inode_aging_count tunable parameter 58 fcl_inode_aging_size tunable parameter 59 fcl_keeptime tunable parameter 56 fcl_maxalloc tunable parameter 56 fcl_winterval tunable parameter 57 file device 236 extent allocation unit state 236 extent all
Index indirect extent address size 19 double 19 single 19 initial_extent_size tunable parameter 58 inode allocation unit file 236 inode list error 146 inode list file 236 inode table 45 internal 45 sizes 45 inodes, block based 19 intent log 21 file 236 multi-volume support 90 intent log resizing 21 internal inode table 45 internal quotas file 78 ioctl interface 63 K kctune 45, 47–49 kernel tunable parameters 45 L label file 236 large files 24, 42 creating file systems with 42 mounting file systems with 4
252 Index parameters (continued) tunable 54 tuning 53 partitioned directories 28 performance overall 34 Storage Checkpoints multi-volume support 90 synchronous I/O 71 system failure recovery 21 system performance overall 34 Q T qio_cache_enable tunable parameter 60 Quick I/O converting files to Oracle Disk Manager 113 quota commands 78 quotaoff how to turn off quotas 144 quotaon how to turn on quotas 143 quotas 77 exceeding the soft limit 78 hard limit 77 how to view quotas 144 soft limit 77 quotas fi
Index VERITAS Enterprise Administrator 30 Veritas Operations Manager 31 Version 1 disk layout 231 Version 2 disk layout 231 Version 3 disk layout 232 Version 4 disk layout 232, 235 Version 5 disk layout 232, 238 Version 6 disk layout 232 Version 7 disk layout 233 Version 8 disk layout 233 virtual disks 32 volume sets 92 VOP_INACTIVE 162, 205 vx_bc_bufhwm tunable parameter 47 VX_DSYNC 72 VX_FREEZE 74 VX_FULLFSCK 146, 148–152, 155–157, 159, 162– 163, 166–169, 176, 190–195, 198–199, 201, 204– 205, 207–210, 21
