Katarina Machalkova wrote:

Hola!

...

Choosing directory works but then choosing mount point gives: "Unable to mount the NFS entries from /etc/fstab"

This means that the restart of NFS service failed (the message is rather stupid^W inaccurate :)). Can you restart manually, from the console? ('rcnfs restart')

# /etc/init.d/nfs restart Shutting down NFS client services: idmapd rpc.statd done Starting NFS client services: sm-notify idmapd done # mount -a mount.nfs: access denied by server while mounting 192.168.0.99:/data1 This is odd, other (11.0 physical boxes) machines connect swimmingly. Server 11.0, /var/log/messages: refused mount request from 192.168.0.99 for /data1 (/data1): illegal port 24646 Retries show different illegal ports there. Firewall(s) have no affect. Client is a vmware guest connecting to server on host, same physical machine. Other protocols, smb, sftp and fish (fish since yesteday) work fine though.

...

Also, another pop-up window Error-KDialog says: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Success

Known bug: https://bugzilla.novell.com/show_bug.cgi?id=530283 Will most probably end up assigned to me, no clue how to fix it so far .. *grin*

Sorry, not much of assistance there... Vahis -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Katarina Machalkova wrote:

Hi,

...

# mount -a mount.nfs: access denied by server while mounting 192.168.0.99:/data1

...

Server 11.0, /var/log/messages: refused mount request from 192.168.0.99 for /data1 (/data1): illegal port 24646

I see. What happens here is that the server requires mount requests from the clients on privileged ports ( < 1024) and does not allow those from unprivileged ones.

To get around that, either * export the shared dir with 'insecure' option on the server (/etc/exports) - this will allow mounts from any ports, or

This one does not help: /data1 *(fsid=0,rw,root_squash,sync,insecure,no_subtree_check) I wonder if the syntax is right? Always using YaST has perhaps made me a victim of it, I never need to edit configuration files, so I don't much know which ones to edit or how to. * have clients use privileged ports (erm, but I don't know how :( )

Me neither :( But when I mount in 11.1 client I see this in log: authenticated mount request from 192.168.0.90:822 for /data1 (/data1) The requested port is 822 there.

...

This is odd, other (11.0 physical boxes) machines connect swimmingly.

The major change between openSUSE 11.0 and 11.1 was that rpcbind (instead of portmap) is now the default portmapper. If that is the reason for clients using >=1024 ports for mounting shares by default is a question for nfs utils maintainers ...

hB.

Do you mean 11.2? Since 11.0 and 11.1 work fine together, both ways. I also see something else: I can browse the directory in 11.2 client's file manager: nfs://192.168.0.99/data1/ and logs: authenticated mount request from 192.168.0.99:4111 for /data1 (/data1) Removing insecure option and browsing: authenticated mount request from 192.168.0.99:7636 for /data1 (/data1) So in any case it's possible to browse via those ports but it can't be mounted via fstab. I've tried mounting via cli but I'm not sure of the syntax so I don't know for sure if it works or not. What would be the correct command to try? Vahis -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Katarina Machalkova wrote:

Hi,

...

...

To get around that, either * export the shared dir with 'insecure' option on the server (/etc/exports) - this will allow mounts from any ports, or

This one does not help: /data1 *(fsid=0,rw,root_squash,sync,insecure,no_subtree_check)

I wonder if the syntax is right? Always using YaST has perhaps made me a victim of it, I never need to edit configuration files, so I don't much know which ones to edit or how to.

We have YaST nfs-server module too :) (I guess it just does not get installed by default). You can adjust export options from there as well. Anyway, the above is correct syntax and if it still fails for you, the error message in /var/log/messages on the server now should be different, isn't it?

I know about YaST. My server is configured with it. For years. It works fine, but 11.2 can't mount any exports. Neither via fstab nor commandline.

...

...

The major change between openSUSE 11.0 and 11.1 was that rpcbind (instead of portmap) is now the default portmapper.

Do you mean 11.2? Since 11.0 and 11.1 work fine together, both ways.

No. 11.1 was the first one to default to rpcbind.

Yeah, I found that out in the meantime, too :)

...

So in any case it's possible to browse via those ports but it can't be mounted via fstab.

Hm, could be because file manager (whichever you are using) mounts nfs share read-only for browsing ... and attempt to mount it read-write fails. Just a guess

Mounting in any way fails, cli, fstab, ro, rw, name it.

...

I've tried mounting via cli but I'm not sure of the syntax so I don't know for sure if it works or not. What would be the correct command to try?

mount -t nfs server.ip.add.ress:/$exportdir /$localdir

Wanted to make sure. No cigar.

(or '-t nfs4' if you're using that one). You can try to add '-o ro' parameter to those to tell the client to mount the share read-only to see if that succeeds.

hB.

I think I have but I'll check again. Vahis -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org