|
|
|
|
|
The Mount agent for AIX has the following notes:
When a file system has heavy I/O, the umount command can take several minutes to respond. However, the umount command deletes the mount point from mount command output before returning. Per IBM, this is the expected and supported behavior on AIX. The umount command's processing later puts the mount point back if the mount point is found busy. Meanwhile, the default OfflineTimeout value of the Mount agent can get exceeded, which in turn invokes the Clean agent function. The Clean function can find the mount point's entry absent from the mount command output and exit with success.
The unmounting, however, may not have happened yet. If unmounting did not occur, offlining resources below the Mount resource (for example the LVMVG or DiskGroup resources) can fail.
The Mount resource's Offline agent function then proceeds to unmount the mount point. After several attempts, the Clean scripts that clean the resources below the Mount resource succeed and the group goes offline.
See the VCS User's Guide for more information about the OfflineTimeout attribute.
The Mount agent uses the fsck command to repair a corrupted file system. In a cluster running AIX 5.1c, the fsck command requires the /etc/filesystems file on each system to contain entries for all file systems referenced by the BlockDevice attribute of the Mount agent. The fsck-V vfstype filesystemname command also does not work on AIX 5.1c systems without a corresponding entry for the file system in /etc/filesystems.
The crfs command automatically adds an entry for a new file system to /etc/filesystems on the system it was created on. You must add entries to /etc/filesystems on all other systems in the cluster. The mkfs command does not add an entry for a new file system to /etc/filesystems. You must add entries to /etc/filesystems on all systems in the cluster.
In this /etc/filesystems entry for a VxFS file system created on a VxVM volume, /mount_point is the mount point for the file system, /dev/vx/dsk/Diskgroup_name/Volume_name is the block device on which the file system is created, and vxfs is the file system type.
dev = /dev/vx/dsk/Diskgroup_name/Volume_name
In this /etc/filesystems entry for a JFS file system created on an LVM logical volume, /mount_point2 is the mount point for the file system, /dev/LVMlogical_volume is the block device on which the file system is created, /dev/LVMlogical_volumelog is the log device for the file system automatically created by the crfs command, and jfs is the file system type.
log = /dev/LVMlogical_volumelog
Use the crfs and mkfs commands to create file systems. VCS supports the following configurations for the Mount agent: