[opensuse] NFS, openSUSE 10.0 and 10.3
Hello I have encountered an unexpected problem with the nfs client on openSUSE 10.3. Even as root, I cannot mount an NFS share from a 10.0 system on a 10.3 client. I have searched the archives and do not see this problem. I have seen reports of mounts not happening at boot or of non-root users not being able to mount things. This is not what I am experiencing. I can mount between two 10.3 systems. Or between two 10.0 systems. And, 10.0 can mount from a 10.3 system. Only mounting on a 10.3 client system from a 10.0 server fails. I have the things exported on the 10.0 server as: /home *(rw,no_root_squash,sync) On the 10.0 server, I see this in /var/log/messages: rpc.mountd: authenticated mount request from vmic1.pacific:761 for /home (/home) No complaints. However, on the 10.3 client, I get: # mount -t nfs 10.1.6.131:/home /tmp/qqq mount: 10.1.6.131:/home failed, reason given by server: Permission denied This happens for all 10.3 systems I have. So if I am doing something wrong, I am at least consistent. Anyone else have this problem? Any pointer as to how I can get more information about the problem? The server does not say more. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Roger Oberholtzer wrote:
Hello
I have encountered an unexpected problem with the nfs client on openSUSE 10.3. Even as root, I cannot mount an NFS share from a 10.0 system on a 10.3 client. I have searched the archives and do not see this problem. I have seen reports of mounts not happening at boot or of non-root users not being able to mount things. This is not what I am experiencing.
I can mount between two 10.3 systems. Or between two 10.0 systems. And, 10.0 can mount from a 10.3 system. Only mounting on a 10.3 client system from a 10.0 server fails.
IIRC, the defaults as regards NFS version were changed for 10.3. The "2GB File size limit exceeded over NFS on 10.3" thread from December may give you some clues. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-02-15 at 16:05 +0000, Dave Howorth wrote:
Roger Oberholtzer wrote:
Hello
I have encountered an unexpected problem with the nfs client on openSUSE 10.3. Even as root, I cannot mount an NFS share from a 10.0 system on a 10.3 client. I have searched the archives and do not see this problem. I have seen reports of mounts not happening at boot or of non-root users not being able to mount things. This is not what I am experiencing.
I can mount between two 10.3 systems. Or between two 10.0 systems. And, 10.0 can mount from a 10.3 system. Only mounting on a 10.3 client system from a 10.0 server fails.
IIRC, the defaults as regards NFS version were changed for 10.3. The "2GB File size limit exceeded over NFS on 10.3" thread from December may give you some clues.
Just what I tried first on the 10.3 client: -onfsvers=2 or -onfsvers=3. Same complaint. linux:~ # mount -t nfs -onfsvers=3 -otcp 10.1.6.131:/home /tmp/qq mount: 10.1.6.131:/home failed, reason given by server: Permission denied linux:~ # mount -t nfs -onfsvers=2 -otcp 10.1.6.131:/home /tmp/qq mount: 10.1.6.131:/home failed, reason given by server: Permission denied linux:~ # mount -t nfs -onfsvers=2 -oudp 10.1.6.131:/home /tmp/qq mount: 10.1.6.131:/home failed, reason given by server: Permission denied linux:~ # mount -t nfs -onfsvers=3 -oudp 10.1.6.131:/home /tmp/qq mount: 10.1.6.131:/home failed, reason given by server: Permission denied And to see if it is even looking at my options: linux:~ # mount -t nfs -onfsvers=4 10.1.6.131:/home /tmp/qq 'vers=4' is not supported. Use '-t nfs4' instead. So, it uses them. But to no effect. I am guessing that there is another parameter that could be different. I will look further. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 15 February 2008 16:06, Roger Oberholtzer wrote:
I have encountered an unexpected problem with the nfs client on openSUSE 10.3. Even as root, I cannot mount an NFS share from a 10.0 system on a 10.3 client.
SUSE 10.0 reached end of life on December 20, 2007. Have you considered an upgrade? -- A.M. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-02-15 at 20:27 +0100, Alexandr Malusek wrote:
On Friday 15 February 2008 16:06, Roger Oberholtzer wrote:
I have encountered an unexpected problem with the nfs client on openSUSE 10.3. Even as root, I cannot mount an NFS share from a 10.0 system on a 10.3 client.
SUSE 10.0 reached end of life on December 20, 2007. Have you considered an upgrade?
We are in the process of doing this. We started working on 10.3 support the week the final release was made. We install it on all new systems we deliver. But 10.0 system are 'out there'. Unlike those lucky guys at SUSE, we cannot end our support so readily. During the transition, there will be mixes of releases. So, a 10.3 client may very well need to access files on a 10.0 server until the 10.0 server can be migrated to 10.3. One thing that has slowed down our full development migration (as opposed to our customer platform, whihc is fully supported on 10.3) to 10.3 is that cxoffice (which we use to run MSVC++ to make Win32 versions of some of our software) does not run the same apps for us on 10.3 that the same cxoffice release does run on 10.0. The folks at cxoffice don't know why. As the MSVC++ compiler is not an officially supported app, they won't do much to sort it out. So, we are currently trying to get gcc cross compilation to work with mingw. When all that is working, I expect we will able to move to new releases on our development systems much faster. Currently, we need to keep the odd 10.0 system aroung to perform tasks that are not working as needed on 10.3. Of course, our OS/2-based TMS DSP compilers that run great in dosbox would remain vulnerable to new OSs. But such is life in Linux-land. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----Original Message----- From: Roger Oberholtzer [mailto:roger@opq.se] Sent: Friday, February 15, 2008 10:07 AM To: opensuse Subject: [opensuse] NFS, openSUSE 10.0 and 10.3
Hello
I have encountered an unexpected problem with the nfs client on openSUSE 10.3. Even as root, I cannot mount an NFS share from a 10.0 system on a 10.3 client. I have searched the archives and do not see this problem. I have seen reports of mounts not happening at boot or of non-root users not being able to mount things. This is not what I am experiencing.
I can mount between two 10.3 systems. Or between two 10.0 systems. And, 10.0 can mount from a 10.3 system. Only mounting on a 10.3 client system from a 10.0 server fails.
I have the things exported on the 10.0 server as:
/home *(rw,no_root_squash,sync)
On the 10.0 server, I see this in /var/log/messages:
rpc.mountd: authenticated mount request from vmic1.pacific:761 for /home (/home)
No complaints. However, on the 10.3 client, I get:
# mount -t nfs 10.1.6.131:/home /tmp/qqq
mount: 10.1.6.131:/home failed, reason given by server: Permission denied
Use -o nolock: mount -t nfs -o nolock nfsserver:/path/to/share /mnt Let us know if that works... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-02-15 at 14:34 -0500, Marlier, Ian wrote:
-----Original Message----- From: Roger Oberholtzer [mailto:roger@opq.se] Sent: Friday, February 15, 2008 10:07 AM To: opensuse Subject: [opensuse] NFS, openSUSE 10.0 and 10.3
Hello
I have encountered an unexpected problem with the nfs client on openSUSE 10.3. Even as root, I cannot mount an NFS share from a 10.0 system on a 10.3 client. I have searched the archives and do not see this problem. I have seen reports of mounts not happening at boot or of non-root users not being able to mount things. This is not what I am experiencing.
I can mount between two 10.3 systems. Or between two 10.0 systems. And, 10.0 can mount from a 10.3 system. Only mounting on a 10.3 client system from a 10.0 server fails.
I have the things exported on the 10.0 server as:
/home *(rw,no_root_squash,sync)
On the 10.0 server, I see this in /var/log/messages:
rpc.mountd: authenticated mount request from vmic1.pacific:761 for /home (/home)
No complaints. However, on the 10.3 client, I get:
# mount -t nfs 10.1.6.131:/home /tmp/qqq
mount: 10.1.6.131:/home failed, reason given by server: Permission denied
Use -o nolock: mount -t nfs -o nolock nfsserver:/path/to/share /mnt
Let us know if that works...
Nope. You were right rpc.statd is not running on the 10.3 client. I also tried running it on the client (started by hand with the command: rpc.statd). That made no difference. Could there be something like this missing on the 10.0 server? -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 15 Feb 2008 16:06:35 +0100, Roger Oberholtzer wrote: [...]
No complaints. However, on the 10.3 client, I get:
# mount -t nfs 10.1.6.131:/home /tmp/qqq
mount: 10.1.6.131:/home failed, reason given by server: Permission denied
This happens for all 10.3 systems I have. So if I am doing something wrong, I am at least consistent.
Anyone else have this problem? Any pointer as to how I can get more information about the problem? The server does not say more.
Yes, I had this problem. The problem is that the client side doesn't automatically run start-statd as I believe it used to. If you run this (as root), then the mounts will work fine. There are a couple of open bugs on this in bugzilla. One of them is 353538. Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Alexandr Malusek -
Dave Howorth -
Jim Henderson -
Marlier, Ian -
Roger Oberholtzer