Red Hat Summitこのコンテンツは選択した言語では利用できません。
10.2. Additional Configuration Considerations
In addition to the locking considerations, you should take the following into account when configuring an NFS service over a GFS or GFS2 file system.
- Red Hat supports only Red Hat Cluster Suite configurations using NFSv3 with locking in an active/passive configuration with the following characteristics:
- The backend file system is a GFS or GFS2 file system running on a 2 to 16 node cluster.
- An NFSv3 server is defined as a service exporting the entire GFS/GFS2 file system from a single cluster node at a time.
- The NFS server can fail over from one cluster node to another (active/passive configuration).
- No access to the GFS/GFS2 file system is allowed except through the NFS server. This includes both local GFS/GFS2 file system access as well as access through Samba or Clustered Samba.
- The GFS or GFS2 file system must be mounted with the
localflocksoption. - There is no NFS quota support on the system.
This configuration provides HA for the file system and reduces system downtime since a failed node does not result in the requirement to execute thefsckcommand when failing the NFS server from one node to another. - The
fsid=NFS option is mandatory for NFS exports of GFS/GFS2. - There is currently an issue with failover and failback when using NFSv3 over GFS with TCP when the following scenario comes into play:
- Client A mounts from server 1.
- The system administrator moves NFS service from server 1 to server 2.
- The client resumes I/O operations.
- The system administrator moves NFS service from server 2 to server 1.
In this situation, the NFS service on server 1 does not get shut down because this would render other NFS services inoperable.Should this situation arise, you should move all NFS services off of server 1 and run theservice nfs restart. After this you can safely migrate your NFS services back to server 1. - If problems arise with your cluster (for example, the cluster becomes inquorate and fencing is not successful), the clustered logical volumes and the GFS/GFS2 file system will be frozen and no access is possible until the cluster is quorate. You should consider this possibility when determining whether a simple failover solution such as the one defined in this procedure is the most appropriate for your system.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}