Cluster Server 7.3.1 Bundled Agents Reference Guide - Linux
- Introducing Bundled agents
- Storage agents
- DiskGroup agent
- DiskGroupSnap agent
- Notes for DiskGroupSnap agent
- Sample configurations for DiskGroupSnap agent
- Volume agent
- VolumeSet agent
- Sample configurations for VolumeSet agent
- LVMLogicalVolume agent
- LVMVolumeGroup agent
- Sample configurations for LVMVolumeGroup agent
- Mount agent
- Sample configurations for Mount agent
- VMwareDisks agent
- SFCache agent
- AWS EBSVol agent
- AzureDisk agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- Notes for the NIC agent
- Sample configurations for NIC agent
- IPMultiNIC agent
- MultiNICA agent
- IP Conservation Mode (ICM) for MultiNICA agent
- Performance Mode (PM) for MultiNICA agent
- Sample configurations for MultiNICA agent
- DNS agent
- Agent notes for DNS agent
- About using the VCS DNS agent on UNIX with a secure Windows DNS server
- Sample configurations for DNS agent
- AWSIP agent
- AWSRoute53 agent
- AzureIP agent
- AzureDNSZone agent
- File share agents
- NFS agent
- NFSRestart agent
- Share agent
- About the Samba agents
- SambaServer agent
- SambaShare agent
- NetBios agent
- Service and application agents
- Apache HTTP server agent
- Application agent
- Notes for Application agent
- Sample configurations for Application agent
- CoordPoint agent
- KVMGuest agent
- Notes for KVMGuest agent
- Sample configurations for KVMGuest environment
- Sample configurations for RHEV environment
- Process agent
- Usage notes for Process agent
- Sample configurations for Process agent
- ProcessOnOnly agent
- AzureAuth agent
- Infrastructure and support agents
- Testing agents
- Replication agents
- RVG agent
- RVGPrimary agent
- RVGSnapshot
- RVGShared agent
- RVGLogowner agent
- RVGSharedPri agent
- VFRJob agent
- Dependencies for VFRJob agent
- Notes for the VFRJob agent
RHEL 7: Configuring bind mounts
RHEL 7 supports bind mount, but it does not display the bind flag with the mount point. In case of bind mounts, the mount command displays the parent block device and file system type instead of the block device and "bind" option used while performing a bind mount. The mount command output displays the bind mount as a parent block device mounted on multiple mount points. Due to this behavior, the Mount agent is unable to determine bind mounts and any mount resource with FSType=bind fails to come online and the Mount agent reports the resource state as UNKNOWN. You can configure FSType=bind in other Linux versions.
The Mount agent now allows the same block device to be mounted on multiple mount points, so to configure a bind mount in VCS, use the parent block device and file system type.
Mount mntres1 ( BlockDevice = "/dev/vx/dsk/vcsdg/vcsvol" MountPoint = "/vcsmnt" FSType = vxfs FsckOpt = "-y" ) Mount mntres2 ( BlockDevice = "/vcsmnt" MountPoint = "/bindmount" FSType = bind )
Mount mntres1 ( BlockDevice = "/dev/vx/dsk/vcsdg/vcsvol" MountPoint = "/vcsmnt" FSType = vxfs FsckOpt = "-y" ) Mount mntres2 ( BlockDevice = "/dev/vx/dsk/vcsdg/vcsvol" MountPoint = "/bindmount" FSType = vxfs FsckOpt = "-y" )