Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm having a peculiar problem with nfs on linux. I am trying to mount and use an nfs-shared directory, shared from an HPUX machine, mounting it on a linux box. I can mount it in all instances, but I can only "ls" the directory if I mount it using nfs version 2 or 1. If I mount it using nfs version 3, I get an Input/Output error if I try to list the directory ("ls"):
mount -o soft,intr hphost:/directory /mnt/cdrom
ls
<long wait, 30 secs.>
ls: reading directory /mnt/cdrom: Input/output error
If I use nfs version 1 or 2, all is well:
mount -o soft,intr,nfsvers=2 hphost:/directory /mnt/cdrom
ls
whatever files
are there
"soft,intr" are just there so I can bail out of a broken command. Otherwise, I wait forever, and have to reboot the machine to get rid of the shell session.
"nfsvers=n
Use an alternate RPC version number to con_tact the NFS daemon on the remote host. This option is useful for hosts that can run multiple NFS servers. The default value is version 2."
Haven't tried it but seems if you add "nfsver=3" to your options it might help.
I guess I wasn't clear enough. Default is nfsvers=3, but that is the version that chokes. if I use:
mount -o soft,intr,nfsver=3..., it fails, and that is default. Other boxes with similar loads (same set of CD's, e.g.) take nfsvers=3 just fine. This ONE install won't, and I don't understand what I am doing wrong with the install to hose nfs.
Since you say it works on systems that are apparently the same build it suggests to me slightly different libraries or binaries. You might want to cksum the mount command on this server and another server where it works to see if they are in fact the same.
This is probably a server side problem, I'd guess that your setup of HPUX doesnt support V3 NFS. On a linux nfs server the command "rpcinfo -p | grep nfs" would list the versions supported, this command also works on AIX, I dont have access to HPUX to test.
For a server that supports V2 and V3 the output should look something like this...
FYI: HP-UX 10.20 does NOT support version 3 but 11i DOES.
However he is saying that the export from HP to other servers using NFS 3 is working so I assumed he was on an 11 version.
There was actually a patch once for 10.20 that added NFS Version 3 to it that caused me some real issues when I installed it because /net would hang and I had a binary that had /net in the library path and even though it was set to use SHLIB_PATH for shared libraries it would first try to hit /net so therefore hang. Our fix then was to back out the patch.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.