Preventive Service Planning
This technote provides information about known issues with Linux VOB hosts (both SUSE and Red Hat) accessing VOB database storage over Network File System ( NFS).
Various defects in the Linux implementation of the NFS client can cause VOBs to become inaccessible (worst case) or cause significant performance degradations (best case).
The following versions of Linux are known to work correctly (as of June 2012) when VOBs are hosted on a Network Attached Storage (NAS):
- Red Hat Enterprise 4 Update 8
- Red Hat Enterprise 5 Update 3
- Red Hat Enterprise 5 Update 5 with Advisory RHSA-2010:0504-1
- SUSE 10 with all Updates
- Use one of the Linux versions listed above.
- Do not use NFS to mount the VOB database storage.
- Version 126.96.36.199 introduces a new alternate configuration which involves moving the almd files (used for VOB database concurrency control) to local disk storage on the VOB server, that reduces the impact of the NFS defects on ClearCase.
Review technote 1637860 for more details on this solution.
- Version 188.8.131.52 added the new alternate configuration described above..
If you choose to avoid using NFS for VOB database storage (workaround "b" above), consider the following:
- Split the VOB database storage from the VOB pools and keep the VOB pools on the NAS.
- Use fiber channel or iSCSI to connect the VOB host to the VOB database storage on the NAS.
Refer to the Rational ClearCase System Requirements List for additional information about supported platforms.
|Software Development||Rational ClearCase||VOB||Linux|