NFS

[Balasiu Dan]

Hi!

we have a server A (HPUX10.20)
mounting on /B, /opt/ptc/ exported from server B (HPUX11.0).
we can`t acces data on some subdirectories of /B;
for example, we can ll /B/a or /B/c but not /B/b (result "total 0").
it??s interesting we can cp or vi files on /B/b but can`t list them from Server A.
We found this files on Server B.

As further information, on Server B , SAMBA is exporting
/opt/ptc/DirB for Windows Clients.

Rebooting server A did not help.

on Server B :

/opt/ptc -anon=65534, root=serverA

any idea?

thanks
dan

[Robert-Jan Goossens]

Hi,

Could you check the NFS version Samba is using on /opt/ptc/DirB.

By default, the version of NFS protocol used between the client and the server is the highest one available on both systems. In this case if SAMBA uses a lower version (2) there could be a mismatch.

I have to admit this is a bit of a wildshot.

Hope it helps,

Robert-Jan.

[T G Manikandan]

What are the permissions of dir /opt/ptc/b on the server B.

[Balasiu Dan]

Hi!

i find out where the problem comes from:
Server A and Server B are connected through WAN (2MBit/s connection).
Server A can??t list /B/b because there a lot of files in /B/b.
Small subdirectories (ex /B/a)can be listed.

A Server C, in the same LAN segment with Server B, can list everything.

I think the NFS Client gets a timeout..Is this true?

Can we configure the NFS Client (Server A)in this case?

thanks
dan

[Michael Knaup]

Hi Dan,

is the mount using NFSv3? You can check this with "nfsstat -m" on the client.

My idea is that NFSv3 uses readdirplus, which transfers a lot more data than a readdir.

So a possible workaround could be to do the nfs mount with the option "-o vers=2" and check it again.

Cheers,

Michael

[Balasiu Dan]

Hi Michael,

client is version 2


thanks
dan

[T G Manikandan]

NFS using UDP on WAN create lot of problems reg. the timeout problems.They were for LAN.

you can use NFS over TCP for WAN.

By default it is not enabled on 11.0.

you can use

rpcinfo -p
to check the version and the protocol .

To enable NFS over TCP you need to change NFS_TCP variable from '0' to '1' in the /etc/rc.config.d/nfsconf.

And then re-starting the nfs.server and nfs.client services.

Thanks

[Balasiu Dan]

Hi TG,

i did not found any parameter NFS_TCP in the nfsconf file
neither on server A (HPUX 10.20) nor on Server B (HPUX 11.00)

thanks
dan

[T G Manikandan]

You should use

#setoncenv NFS_TCP 1

check the man pages of setoncenv.




Thanks

[Steven E. Protter]

Samba is independent of NFS. NFS of samba.

If this is a samba issue, we're looking at the smb.conf file and the error logs in /opt/samba

If its an NFS issue, we don't care about samba.

If a Windows server is connecting, its probably a Samba issue. Windows can mount nfs volumes but requires additional software. The samba client is built in above Win98.

You nfs setup btw seems to allow anonymous access only from server A. Lots of users, but only one server as a client.

SEP

[Balasiu Dan]

Hi SEP!

its a NFS problem.
Let??s resume:

My NFS ServerB ??s a HPUX11.0
and the NFS ClientA is HPUX10.20, connected through a WAN line
(2MBits/sec).

The ClientA can??t list directories with many files,
perhaps a timeout problem.

Questions:

1) If i activate on ServerB HPUX11.0 the NFS_TCP connection (setoncenv) will the ClientA (10.20) then be able to mount the ressource from the ServerB and work correctly?
What protocol uses the NFS Client when FS requesting?

2) This ServerB mounts a ressource from another HPUX10.20 ServerC. Will this connection be affected?

thanks
dan