On Mon, 06 Sep 2010 03:02:59 +0200, Frans de Boer wrote:

Mount command: mount -t nfs4 <IP>:/home/maint /media/pubserv1 ------ failed, same on 11.2 with 2.6.34.6 is ok.

Maybe this forum thread can help you: http://forums.opensuse.org/english/get-help-here/network-internet/394119-sus... Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 09/06/2010 04:21 AM, Frans de Boer wrote:

On 09/06/2010 03:54 AM, Philipp Thomas wrote:

...

On Mon, 06 Sep 2010 03:02:59 +0200, Frans de Boer wrote:

Hi

...

Mount command: mount -t nfs4 <IP>:/home/maint /media/pubserv1 ------ failed, same on 11.2 with 2.6.34.6 is ok.

Maybe this forum thread can help you: http://forums.opensuse.org/english/get-help-here/network-internet/394119-sus...

Philipp

Hi, Philipp,

I do not use autofs, but maybe your pointer has some merit which I will check out without great hope. Again, same server (11.3) but client 11.2 is working and 11.3 is not. Guess problem is with 11.3.

regards, Frans.

Hi all, Thanks for the various pointers and some constructive comments. As it turns out: don't use the yast2 module to setup the server. When I configured the server environment by hand (using an Ubuntu document - although a bit flawed) , started the server, everything works just fine. I decided not to use the yast2 nfs clients setup, but rather did this by hand too. At least I have a working NFS environment again and am happily back at 11.3. Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Report the bug, please. Is better if all yast modules work fine -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 09/11/2010 01:35 AM, Carlos E. R. wrote:

On 2010-09-10 08:15, Roger Oberholtzer wrote:

...

On Thu, 2010-09-09 at 21:13 +0200, Frans de Boer wrote:

...

Thanks for the various pointers and some constructive comments. As it turns out: don't use the yast2 module to setup the server. When I configured the server environment by hand (using an Ubuntu document - although a bit flawed) , started the server, everything works just fine. I decided not to use the yast2 nfs clients setup, but rather did this by hand too. At least I have a working NFS environment again and am happily back at 11.3.

The server config must be modifying /etc/exports, and the client modifying /etc/fstab.

It would be curious what yast put in these files that you have done differently.

Now that I remember: yast nfs client setup usually borks tyhe fstab file, leaving only mounted partitions and deleting those that are not mounted when yast runs. It destroyed my setup several times, had to restore fstab from backups.

I have a vague recolection of having reported this long ago :-?

Because of popular demand I will report the bug, even if it means messing up a perfectly good working environment (yes, I make backups). If this error has been reported as stated above, I just wonder if I should waist my time to report it again. Ah, well, I will do it. Maybe someone ate Novell gets a wakeup call to do it properly next time or even provide an "update" which take proper care of the NFS4 differences. Reason: i am exposing my server more and more to the outside (hostile) world but want assurance that anything beyond my DMZ (i.e. my local LAN) is shielded adequately. The drive being "anywhere, anytime any means". I am far from it, but slowly progressing towards my private implementation of the Jericho framework. Live long and prosper, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 09/06/2010 12:12 PM, Tejas Guruswamy wrote:

On 06/09/10 02:02, Frans de Boer wrote:

...

On 09/06/2010 02:21 AM, Michael S. Dunsaavage wrote:

...

On 9/5/2010 8:06 PM, Frans de Boer wrote:

...

Dear all,

After many experiments I am back at 11.2 (linux kernel 2.6.34.6). Why? Well NFS client is not working out of the box or with updates. NFS Server is working fine, but whatever try under 11.3, it's not working. After some time, I thought it would be the kernel causing the problem, but reverting back to earlier 2.6.34 versions or even going as high as 2.6.35.4 did not do anything. Guess the NFS client utilities are broken.

Any suggestions?

Ummm. It's broken how? Doesn't start up? Doesn't connect? Client starts up and says "I'm broken"? Do logs say anything?

http://www.catb.org/esr/faqs/smart-questions.html#beprecise

Well, suse 11.2 using 2.6.34.6 is working fine. Suse 11.3 using standard 2.6.34-12 or native 2.6.34.6 or 2.6.35.4 are not working. So, it's not the kernel who is at fault. Identical configuration, but 11.3 does not work. NFS Server is working as before.

The logs: say only that the can't find the designated directory: Sep 6 01:42:48 pws1 sm-notify[3441]: Already notifying clients; Exiting! Sep 6 01:42:48 pws1 rpc.idmapd[2126]: nss_getpwnam: name 'maint' not found in domain 'fransdb.local'

Mount command: mount -t nfs4 <IP>:/home/maint /media/pubserv1 ------ failed, same on 11.2 with 2.6.34.6 is ok.

I can't see how this command ever worked using NFSv4. NFSv4 exports a single pseudo filesystem as the share root - the real path on the server is never needed by the client. The share marked as "fsid=0" in /etc/exports appears as root (<IP>:/). It's not perfect, but to learn the theory read something like this: https://help.ubuntu.com/community/NFSv4Howto

I'm not sure what you had working before with 11.2, but it doesn't look like it was NFSv4. Maybe 11.2 was falling back to NFSv3 silently or something; but I don't ever remember it doing that on my systems.

...

NFS Server is on 11.3 machine pubserv1, client is on machine2 using 11.3 = fail. NFS Server is on 11.3 machine pubserv1, client is on machine2 using 11.2 = ok.

The only thing I did not try sofar is to use the nfs utils prior to version 1.2.1.

An please, it's not a good feature to be sarcastic.

It's not polite of them, but you did not start this conversation with the right tone. Your first email didn't properly ask a question; to me it just seems to proclaim that "NFS is BROKEN on 11.3". Many people on this list have NFS working; of course they are going to treat such claims as ridiculous.

Regards, Tejas

I never proclaimed that NFS is broken, I stated that I Guessed that the NFS utils are broken. Now it might be that on 11.2 there was something going on, not according specs. However, I used the YAST utils to setup the server and the client. Also the mentioned mount command is the actual command executed when doing a mount from /etc/fstab. So, it might be that some parameters are not correct, but that's settings supplied by YAST. I will look anyhow to the alternative settings. Thanks for the pointer. Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 09/06/2010 04:01 AM, Carlos E. R. wrote:

On 2010-09-06 02:21, Michael S. Dunsaavage wrote:

...

On 9/5/2010 8:06 PM, Frans de Boer wrote:

...

...

After many experiments I am back at 11.2 (linux kernel 2.6.34.6). Why? Well NFS client is not working out of the box or with updates. NFS Server is working fine, but whatever try under 11.3, it's not working. After some time, I thought it would be the kernel causing the problem, but reverting back to earlier 2.6.34 versions or even going as high as 2.6.35.4 did not do anything. Guess the NFS client utilities are broken.

Any suggestions?

Ummm. It's broken how? Doesn't start up? Doesn't connect? Client starts up and says "I'm broken"? Do logs say anything?

Several people have reported problems in 11.3 with NFS mounts during boot, with delays of several minutes till timeout. Some reported success after disabling version 4 features.

samples:

...

http://ftp5.gwdg.de/pub/opensuse/discontinued/distribution/11.0/repo/ http://forums.opensuse.org/showthread.php?t=44491 Hi Carlos,

Disabling the NFS4 features on both the server and the client did not work. Anyhow, disabling should not be "the" solution! Again, 11.2 is working, IDENTICAL configuration on 11.3 is not!!! Only change is client being SuSE 11.3!! Seeing your response makes me even stronger in believing that the NFS utils are at fault. I just wonder why it has slipped through the cracks before. Everybody (Aplha/Beta/RC testers) are using a server but nobody is using a client with NFS4?? Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 2010-09-06 04:15, Frans de Boer wrote:

On 09/06/2010 04:01 AM, Carlos E. R. wrote:

Hi Carlos,

Disabling the NFS4 features on both the server and the client did not work. Anyhow, disabling should not be "the" solution!

Yes, that's right. It is a hack and a clue for devs.

Seeing your response makes me even stronger in believing that the NFS utils are at fault. I just wonder why it has slipped through the cracks before. Everybody (Aplha/Beta/RC testers) are using a server but nobody is using a client with NFS4??

I did not test NFS on 11.3 at all. I had other bigger issues (video not working right). Betatesting is not thorough: each one tries to test the features we use, and seldom all of those we use. At least, that's what I do, and I guess most people do the same. But hey! you could have tested it yourself and reported ;-) -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar))