Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I take it that you can still manually mount the nfs share using the mount command?
You could try: mount -av and read the messages ... looking at the boot log should tell you what happened when the share was to be loaded. dmesg is a good bet.
try option "user" by itself - this should allow you to mount/unmount without being root.
try options "user,auto" should this work.
You don't want "users" because then any user can unmount the share you are working on if you see what I mean.
I'm the only person that uses this computer so I'm not bothered about user access, and I can mount as user. From dmesg I have:
Code:
nfs warning: mount version older than kernel
RPC: call_verify: program 100003, version 3 unsupported by server quiller
RPC: call_verify: program 100003, version 3 unsupported by server quiller
nfs warning: mount version older than kernel
I don't know if this means it didn't work, because it mounts manually when I'm logged on without a problem.
You're gonna make it if you try - They're gonna love you!
Shall I tell you the name of the game ... ?
sounds like updating mount may do the trick.
OK - you can mount as user ...
try it with the -v option and check the output.
try again with -av (most are already mounted so fine - but you see, the boot script is calling mount -a to mount everything not marked "noauto". The only difference as user (except that you have given a user root access?) is the absence of the -a option (and it's being run by init I guess).
(Or - are there two versions of "mount" - like if the kernel boot image is an old one?)
-v and -av both mount sucessfully but with "mount: failed with nfs mount version 4, trying 3..". Not sure what you mean by the last comment but my kernel is 2.6.10.
Sometimes, when people recompile their kernel, they keep the old initrd or use pointers to the old kernel tree or other oddness. This creates trouble.
Probably dosn't apply to you.
I take it client and server machines are not identical?
The boot message is telling you that nfs mount 3 is not supported on the server - the mount message is telling you it failed with nfs4 and tries nfs3 (then it works!!!) <sigh>
read man nfs to see what these are.
you may need to specify nfsvers=2
I *think* my kernel's OK. I tried using nfs 2 and it eliminates the messages, dmesg just has the usual mount version lower than kernel thing, it seems to suggest that it's been mounted. I can't imagine what's going on here unless something else is unmounting it afterwards. I think I've just done so much poking around to my installation it's gone weird. Ah well, thanks for your help anyway
(AFTERTHOUGHT: I think I'll try and work around it by putting the mount in my login script.)
Last edited by amnesty_puppy; 08-06-2005 at 05:32 AM.
Your bootscript should have a "mount -a" command in there. You could try explicitly mounting the nfs share after this.
You could, instaed, try adding it to the login script.
BTW: it won't mount is the client cannot see the server, if the client dosn't have the right access on the server, if NFS is not running on the server. Hence NFS is not usually configured to mount at startup unless you know the server will be running.
On your mention of bootscripts I checked mine out and it seems there is an nfsmount bootscript that wasn't set to run. Looks like I didn't sort it out properly when I set the share up a while back . Thanks for your time, I wouldn't have noticed that without your mention.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.