NFS Client crippled by Rational Clearcase

	Free Downloads, Community Forum, FAQs and Developer Resources

Make /Tools Your Home | Link to us

Today's posts | Posts since last visit | Most Active Topics

All Forums	Register	Login	Search	Subscriptions	My Profile	Inbox
Tool Warehouse	FAQs	Resources	Help	Member List	Address Book	Logout

NFS Client crippled by Rational Clearcase

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [Windows - UNIX Interop] >> System & Network Admin Forum >> NFS Client crippled by Rational Clearcase

Page: [1]

Message

<< Older Topic Newer Topic >>

NFS Client crippled by Rational Clearcase - Oct. 25, '04, 12:00:48 PM

rtwede

Posts: 18
Joined: Sep. 30, '04,
Status: offline

Using SFU 3.5, NFS shares can easily be accessed using the UNC path names:

\\server\exportdir

Using Run: and typing the UNC name opens a window showing the contents of the directory.

However, simply installing Rational Clearcase causes all such accesses to fail.

As far as I can detect, it is due to the mvfs (multi-variant filesystem) for which Clearcase adds a filesystem driver into the OS.

At that point the simple 'mount' command from the bash prompt fails to list all mount points as well.

Any advice anyone can give?

Post #: 1

RE: NFS Client crippled by Rational Clearcase - Oct. 25, '04, 1:24:45 PM

Rodney

Posts: 3696
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline

Don't do that then

(more seriously)
I haven't used Clearcase is my disclaimer.
I see you using "\\server\exportdir" which I assume you are doing from the Win32 world
because network drive access from Interix (which includes bash is through the
/net (slash-net) filesystem. So the equivalent is "/net/server/exportdir". If you try
access via /net, do you get the same problem?
When you are looking with the mount command (which is really a Win32 cmd BTW)
are you on the glass or via a pseudo-terminal (pty; xterm, telnet, ssh, ...)?

(in reply to rtwede)

Post #: 2

RE: NFS Client crippled by Rational Clearcase - Oct. 25, '04, 2:38:04 PM

rtwede

Posts: 18
Joined: Sep. 30, '04,
Status: offline

Thanks for the tip.

It appears I get the same result through /net however.

Interestingly, once Clearcase is installed I can still see all the exports of a server using 'cd /net/server; ls' or Run:\\server\

However I cannot change directory to or list any files on the exports. The server is as far as I can go.

For example, in the /net/server directory if I issue ls I get 'local', but 'cd local' returns '/net/server/local: Not a directory'

The ksh attempt returns not a directory and the Run:\\server\local equivalent returns 'The network path was not found' even though it is displaying an icon for the directory at the server level that I can click on.

(in reply to rtwede)

Post #: 3

RE: NFS Client crippled by Rational Clearcase - Oct. 25, '04, 2:40:51 PM

rtwede

Posts: 18
Joined: Sep. 30, '04,
Status: offline

I'd like to know more about the mvfs driver Clearcase inserts into the OS. It's somehow intervening and getting in the middle of non mvfs filesystem accesses. I haven't ever seen how a new filesystem type is inserted into Windows so I don't know how to further think down this line.

(in reply to rtwede)

Post #: 4

RE: NFS Client crippled by Rational Clearcase - Oct. 25, '04, 3:06:47 PM

Rodney

Posts: 3696
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline

I'm guessing that it could be a "shim". Essentially like a layer FS on Unix. It sits
in-between the API caller and the next level of device driver. You might want to grok
through the registry to see if there are some Rationale/Clearcase setting that could
be tweaked. Have you check with Clearcase to see if they know of the problem?

(in reply to rtwede)