Please enter search query.
Search <book_title>...
Veritas InfoScale™ 7.4.1 Virtualization Guide - AIX
Last Published:
2019-02-01
Product(s):
InfoScale & Storage Foundation (7.4.1)
Platform: AIX
- Section I. Overview
- Storage Foundation and High Availability Solutions in AIX PowerVM virtual environments
- Section II. Implementation
- Setting up Storage Foundation and High Availability Solutions in AIX PowerVM virtual environments
- Supported configurations for Virtual I/O servers (VIOS) on AIX
- Installing and configuring Storage Foundation and High Availability (SFHA) Solutions in the logical partition (LPAR)
- Installing and configuring Cluster Server for logical partition and application availability
- Supported configurations for Virtual I/O servers (VIOS) on AIX
- Setting up Storage Foundation and High Availability Solutions in AIX PowerVM virtual environments
- Section III. Use cases for AIX PowerVM virtual environments
- Application to spindle visibility
- Simplified storage management in VIOS
- Configuring Dynamic Multi-Pathing (DMP) on Virtual I/O server
- Configuring Dynamic Multi-Pathing (DMP) pseudo devices as virtual SCSI devices
- Extended attributes in VIO client for a virtual SCSI disk
- Virtual machine (logical partition) availability
- Simplified management and high availability for IBM Workload Partitions
- Implementing Storage Foundation support for WPARs
- How Cluster Server (VCS) works with Workload Patitions (WPARs)
- Configuring VCS in WPARs
- High availability and live migration
- Limitations and unsupported LPAR features
- Multi-tier business service support
- Server consolidation
- About IBM Virtual Ethernet
- Using Storage Foundation in the logical partition (LPAR) with virtual SCSI devices
- How DMP handles I/O for vSCSI devices
- Physical to virtual migration (P2V)
- Section IV. Reference
Tracing Inode cache event
For any inode, an iget() call increments its vcount by 1, and an iput() call decrements the vcount if it is not equal to one. The trace entries containing 'iget' or 'iput' would correspond to inode cache operations. The entries also provide details such as inode number and device ID, whenever inode cache operations are performed in VxFS. You can use tracing to collect the data and analyze it further.
In this example, the trace hook identifier for VxFS inode cache operations is 0E4. For tracing only inode cache operations, enter:
# trace -a -j 0E4 & # trcon # cat script.sh (file on VxFS file system) # trcoff # trcstop # trcrpt > trace.out
Sample output :
0E1 0.028564739 0.089402 VxFS VxFS iget: vp = F10001180CCDEDF0, dev = 8000002D00004E20, fsindex = 03E7, iltype = 0000, vcount = 0001, inode = 0002, getcaller = D60063
0E1 0.031875091 0.001512 VxFS VxFS iput: vp = F10001180CCDEDF0, dev = 8000002D00004E20, fsindex = 03E7, iltype = 0000, vcount = 0001, inode = 0002, getcaller = D60063