Today, let me share this problem that we could see on working on Rhel 6.x and CC.
Inside a dynamic view, and vob directory, we are unable to read elements unless we check out them first.
Where the ClearCase Client machine runs Red Hat 6.x and reaches the View and Vob Stores through NFS.
By default Red Hat 6.x uses nfs version 4, so if the VobServer or NAS device supports NFS version 4, the client machine will mount using nfs 4 that will present the wrong behaviour.
3) Reproducing the issue.
On client machine:
3.1) Set a view.
cleartool setview myview
3.2) Alternate to Vob directory.
cd /vobs/myvob
$ ls -l abc.txt
-r-xr-xr-x 1 ibmer users 13203 Mar 4 14:50 abc.txt
3.3) Try to read some files.
cat abc.txt
cat: abc.txt: Not a directory
### Update on 2013-06-11 ##########
This is fixed in ClearCase 7.1.2.10 and 8.0.0.6.
Reference: http://www-01.ibm.com/support/docview.wss?uid=swg1PM68068
###################################
If you cannot upgrade CC yet, use the the Workaround below:
Remount the VobStore using nfs version 3 instead 4.
(use nfsvers=3 option).
4.1) For hard mount
Edit /etc/fstab and use nfsvers=3 on the nfs mount options for
instance:
9.xx.xxx.239:/vobstore /vobstore nfs nfsvers=3,defaults 0 0
4.2) For automount
Edit the default behavior for mount:
For instance on Red Hat
Edit the Client side by changing /etc/nfsmount.conf
file
Changing from:
# Defaultvers=4
Changing to:
Defaultvers=3
test it
cd /net/9.xx.xxx.239/vobstore
]# nfsstat -m
/net/9.32.252.239/vobstore from 9.32.252.239:/vobstore
Flags:
rw,nosuid,nodev,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,
proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=9.32.252.239,mountvers=3
,mountport=600,mountproto=udp,local_lock=none,addr=9.32.252.239
---
For while we have some issues when using NFS version 4, so keep using version 3 instead.
"The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions." #
#################################################################################################