NFS Error

[Peter Clarke]

Can anyone help??

Just set up NFS client on VMS 7.3-2 and mounted file system on my linux box but does not allow me to copy a file to this device.
Am i using the correct command (see attached...)

Regards

Peter

[Daniel Fernandez Illan]

Hi Peter.

You have a problem with permission between Linux and VMS (proxies accounts).

Yo may prove this command:

TCPIP> add proxy tcpip$nobody /uid=-2/gid=-2/host=*
TCPIP> sysconfig -r nfs noproxy_enabled=1
TCPIP> sysconfig -r nfs noproxy_uid=-2
TCPIP> sysconfig -r nfs noproxy_gid=-2

After shutdown and reboot TCP/IP services.

Best Regards.
Daniel.

[Kris Clippeleyr]

Peter,

As the RMS-E-PRV indicates, the account you're are using has no write access to the MFD of that disk.

Did you check the protection on that disk?

Kris

[Peter Clarke]

Daniel,

Do i have to shut down tcpip services or can i just stop nfs and restart??

Regards

Peter

[faris_3]

restarting nfs should be enough

You can also do on a console on the nfs server

$ reply/enable=network
to see the nfs messages.

hth,
HF

[Bojan Nemec]

Hi,

Check the /etc/exports file on the Linux machine and, as I suggested in yours previous thred, the /var/log/messages (just do a tail /var/log/messages after you try the copy command on VMS). Can you read anything from this disk or just a dir command?

Bojan

[Peter Clarke]

I checked the var/log/messages and there is nothing obvious here it just says that it mounted ok.
Tried reply/enable=network and i dont recieve any messages when the copy fails.

Let me just check this.

On the Linux box i have edited the /etc/exports file and entered /data/vmsalpha(sync) 129.100.2.1/16
I have added the user nfs_user 400:400 this is the same as user on the alpha.
Then i have started the nfsd daemon.

On the alpha i have created user account nfs_user [400,400] given privileges sysnam and grpnam,then i have added the proxy:
TCPIP>ADD PROXY NFS_USER /NFS=(OUTGOING,INCOMING)/UID=400/GID=400/HOST=ERITHMAIL
and mounted the remote directory:

TCPIP>MOUNT DNFS1: /HOST="ERITHMAIL" /PATH="/data/vmsalpha/"

then i want to copy file pctest.txt to remote directory:

COPY PCTEST.TXT DNFS1:[000000]

I this correct have i missed anything??

Regards

Peter

[faris_3]

have you tried connecting using nfs v3 ?

Some Linux use nfs V4 not yet supported by
the VMS nfs server.

[faris_3]

sorry i thought the server was VMS.

Anyhow, can your exports be accessed by a nfs V3 client ?

/hf

[faris_3]

I guess what you have checked on Linux
that the user nfs_user has write access
to the exported directory.

[Willem Grooters]

Peter,

Thinks like this have been discussed before:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=448989

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=246673

Perhaps your answer is in one of these

Willem

[Bojan Nemec]

Peter,

Try to modify yours /etc/exports line to:

/data/vmsalpha(sync) 129.100.2.1/16(rw)

Try as Faris suggested:

su - nfs_user -c "echo test > /data/vmsalpha/test"
ls -l /data/vmsalpha/test

If the owner of /data/vmsalpha is not nfs_user do a:

chown 400:400 /data/vmsalpha

By the way (sorry if this is a stupid question but sometimes happens) is the directory /data/vmsalpha created?

Bojan

[Peter Clarke]

I can now set my default as dnfs1:[000000] and see the files in this directory.
However when i try to write a file it gives the message:

Device currently write locked

Reg

Peter

[Bojan Nemec]

Peter,

What is the exact reported error? Can you try to access to this NFS disk from another Linux machine?

Bojan

[Peter Clarke]

Exact error is:

-RMS-E-WLK, device currently write locked

Unfortunately i don't have another Linux machine!

Peter

[faris_3]

can you temporarily do
a chmod 777 on the directory on linux
(access to everybody)
to see if that works

[Bojan Nemec · Accepted solution]

Peter,

The only reported error in VMS abbout RMS-E-WLK is taht you have mounted the NFS device whit the /NOWRITE qualifier. I suppose that you have not done this.

So probably there is an error on the Linux side. Please see the Linux NFS-HOWTO
http://www.faqs.org/docs/Linux-HOWTO/NFS-HOWTO.html

maybe the most interesant for you is
http://www.faqs.org/docs/Linux-HOWTO/NFS-HOWTO.html#SYMPTOM4

Bojan

[Bojan Nemec]

Maybe this page will also be a good reading:

http://nfs.sourceforge.net/

Bojan

[Peter Clarke]

ok,I set my oracle dump file to save to this device (dnsf1:) and checked it today and the file has been output to this device and freed up lots of space on my alpha.

However the dump file on the Alpha was over 14GB but the one on the Linux is only 1.41GB i have checked the log file and it seems to have copied all the data but im not sure it has done this correctly!! and have no real way of checking this dump file ie. no spare machine and not enough space to create a new DB on the alpha or linux box.

Also the oracle export normally takes 1 and a half hours but to the Linux box it took 5 and a half is this normal? any way of improving this??

Cheers

Peter

[Ian Miller.]

as you are now exporting your database over a network connection rather than a directly connected disk I would expect it to be slower.

As the file sizes you mentioned are a factor of 10 different could there be an arithmentic error in how you are obtaining the file sizes?

[Bojan Nemec]

Peter,

Abbout the size I have realy no idea why is the file 10 times smaller. Check another time the sizes.

The speed is normaly slower, but I never tested on huge files. NFS was used for small files only.

An idea regarding yours problem:
If you need only to make an export of the database you can install the client part of Oracle on Linux and run the export (exp) command directly from linux.

Bojan

[Peter Clarke]

No, on friday i had about 1.12GB left on alpha disk this morning i had over 14GB so just to check this i copied the dump file back from the Linux machine onto the Alpha and i still have 13.07GB free, so something has gone wrong somewhere.

[Bojan Nemec]

Hi,

Check if you can write so large files on yours Linux. There are many restrictions for files larger than 2G, you must have the right kernel. There is also a restriction in the NFS V2 protocol, where the files are also restricted to 2G.

Bojan

[Peter Clarke]

Bojan,

Is there an easy way to check this?

Regards

Peter

[Martin Vorlaender]

Peter,

with SuSE Linux, you normally see this in in the "uname -a" kernel name (something like "...-4GB").

HTH,
Martin