Try running - as root - 'showmount' on the poblano machine Check the man page for details showmount -e showmount -a -- A hollow voice says, "A hollow voice says, 'Plugh'." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, Jul 6, 2011 at 12:24 AM, LLLActive@GMX.Net wrote:

On 01/05/11 18:16, Stan Goodman wrote:

...

On Sunday 01 May 2011 at 19:02:27 (GMT+2) Wolfgang Mueller  wrote:

...

On 05/01/11 14:39, Stan Goodman wrote:

...

The client is on a v11.4 laptop. The entries in YaST>   NFS client are:

Server: poblano Remote directory: /home/stan Mount point: /home/stan/nfs/poblano (which exists) NFS type: nfs Options: default (for the time being) NFSv4 is unchecked Firewall port is open on all interfaces (for the time being)

fstab contains the line: "poblano:/home/stan  /home/stan/nfs/poblano  nfs  defaults 0 0"

An attempt to write this configuration results in: "Unable to mount NFS entries from /etc/fstab"

I must be doing something foolish, but I don't see it.

Did you configure the server's export file? If not, add the following line to poblano:/etc/exports

Here are the entries in YaST>  NFS Server (in poblano):

Start server is checked Directories to export: /home/stan Hosts: chipotle (the laptop) Options: rw,root_squash,sync,no_subtree_check (just as you now suggest)

I think that already does what you write below.

...

+-----

| /home *(rw,root_squash,sync,no_subtree_check)

+-----

or, if you want to limit the nfs access to /home/stan only:

+-----

| /home/stan *(rw,root_squash,sync,no_subtree_check)

+-----

Yast may help you to do this. Select "NFS Server" in "Network Services".

It usually does, but it seems not to help now. As I have been doing for many moons, I have been doing all this configuration in YaST. Something else must be missing.

...

Bye, Wolfgang

Hi all,

I have come across this problem today. I have two openSUSE 11.4 systems, one as NFS Server and the other as user with all its data on the NFS server. The idea is to centralise the data pool of 6 systems, on a raid 10 system that also acts as file/nfs server and making DAR backups with scripts and cron onto USB external disks. So the NFS is crucial. I do not have Samba or any Win systems.

The problem started with not being able to get NFS to work at all between the newly installed 11.4 system (server) and 11.1 systems. I then did a NFS client setup with yast on a 11.4 system, and the NFS client could not mount the fstab nfs mounts when it completes the setup.  Manually mounting was without problems.

 That led me to this thread.

Then I restarted the 11.4 client system, and it hung at the point where the nfs "Starting NFS client services: sm-notify" and then "Mounting network file systems ... mount.nfs: connection timed out" occurs. NFS is not mounted, because it tries to mount before the network is up.

This turned out to be a bug: 694461 - mount.nfs starts before the network is up!I get the NFS to mount with a script before I can get to my data, but this is very unsatisfactory. There has been no movement since 16-06-2011, only some workaround.

I found using NFS 3 on both systems to be more stable. On a Mac and Linux WLan the drives and some directories would sometimes report " .... *.odt does not exist". On the NFS Server I also had to clean the /etc/exports by hand, redo the server config with yast, because it caused the "cannot mount nfs in fstab" error that the first problem has, i.e. it does not configure in the clients. Once I got everything cleaned and as NFS3, all works, besides the mount problem at boot time.

Any ideas to fix the bug 694461will be welcome.

Al

Shouldn't the line in fstab have _netdev instead of defaults to tell the system to attempt mounting the remote share after the network is fired up? i.e. poblano:/home/stan /home/stan/nfs/poblano nfs _netdev 0 0 Regards Tim -- Tim Hempstead thempstead@gmail.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 06/07/11 15:20, LLLActive@GMX.Net wrote:

On 06/07/11 09:31, Tim Hempstead wrote:

...

On Wed, Jul 6, 2011 at 12:24 AM, LLLActive@GMX.Net wrote:

...

On 01/05/11 18:16, Stan Goodman wrote:

...

On Sunday 01 May 2011 at 19:02:27 (GMT+2) Wolfgang Mueller �wrote:

...

On 05/01/11 14:39, Stan Goodman wrote:

...

The client is on a v11.4 laptop. The entries in YaST> � NFS client are:

Server: poblano Remote directory: /home/stan Mount point: /home/stan/nfs/poblano (which exists) NFS type: nfs Options: default (for the time being) NFSv4 is unchecked Firewall port is open on all interfaces (for the time being)

fstab contains the line: "poblano:/home/stan �/home/stan/nfs/poblano �nfs �defaults 0 0"

An attempt to write this configuration results in: "Unable to mount NFS entries from /etc/fstab"

I must be doing something foolish, but I don't see it. Did you configure the server's export file? If not, add the following line to poblano:/etc/exports Here are the entries in YaST> �NFS Server (in poblano):

Start server is checked Directories to export: /home/stan Hosts: chipotle (the laptop) Options: rw,root_squash,sync,no_subtree_check (just as you now suggest)

I think that already does what you write below.

...

+-----

| /home *(rw,root_squash,sync,no_subtree_check)

+-----

or, if you want to limit the nfs access to /home/stan only:

+-----

| /home/stan *(rw,root_squash,sync,no_subtree_check)

+-----

Yast may help you to do this. Select "NFS Server" in "Network Services". It usually does, but it seems not to help now. As I have been doing for many moons, I have been doing all this configuration in YaST. Something else must be missing.

...

Bye, Wolfgang Hi all,

I have come across this problem today. I have two openSUSE 11.4 systems, one as NFS Server and the other as user with all its data on the NFS server. The idea is to centralise the data pool of 6 systems, on a raid 10 system that also acts as file/nfs server and making DAR backups with scripts and cron onto USB external disks. So the NFS is crucial. I do not have Samba or any Win systems.

The problem started with not being able to get NFS to work at all between the newly installed 11.4 system (server) and 11.1 systems. I then did a NFS client setup with yast on a 11.4 system, and the NFS client could not mount the fstab nfs mounts when it completes the setup. �Manually mounting was without problems.

�That led me to this thread.

Then I restarted the 11.4 client system, and it hung at the point where the nfs "Starting NFS client services: sm-notify" and then "Mounting network file systems ... mount.nfs: connection timed out" occurs. NFS is not mounted, because it tries to mount before the network is up.

This turned out to be a bug: 694461 - mount.nfs starts before the network is up!I get the NFS to mount with a script before I can get to my data, but this is very unsatisfactory. There has been no movement since 16-06-2011, only some workaround.

I found using NFS 3 on both systems to be more stable. On a Mac and Linux WLan the drives and some directories would sometimes report " .... *.odt does not exist". On the NFS Server I also had to clean the /etc/exports by hand, redo the server config with yast, because it caused the "cannot mount nfs in fstab" error that the first problem has, i.e. it does not configure in the clients. Once I got everything cleaned and as NFS3, all works, besides the mount problem at boot time.

Any ideas to fix the bug 694461will be welcome.

Al

Shouldn't the line in fstab have _netdev instead of defaults to tell the system to attempt mounting the remote share after the network is fired up?

i.e.

poblano:/home/stan /home/stan/nfs/poblano nfs _netdev 0 0

Regards

Tim

-- Tim Hempstead thempstead@gmail.com

I tried the following and put it into bugzilla:

On my terminal ctrl-alt-F1 at boot time, I see that my eth0 & eth1 is being configured before the nfs is started. One is onboard to the mobo, the other a PCI card. I have, however, a WLan card that has the actual network, which gets configured after the nfs is started. So if the system is hard wired by ethernet cable, it works. It does not work with WLan cards, because they seem to be configured after nfs is started. On my terminal ctrl-alt-F1 at boot time, I see that my eth0 & eth1 is being configured before the nfs is started. One is onboard to the mobo, the other a PCI card. I have, however, a WLan card that has the actual network, which gets configured after the nfs is started. So if the system is hard wired by ethernet cable, it works. It does not work with WLan cards, because they seem to be configured after nfs is started.

So, your suggestion does not work, because the WLan card only gets configured later.

:-) Al

Pardon the double copy and paste text above! :-) Al -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 06/07/11 20:35, Patrick Shanahan wrote:

You are not pardoned! You even posted it twice and most is irrelevant.

...

/dev/null

Hi Partick, :-) Al -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 06/07/11 16:07, Dave Howorth wrote:

LLLActive@GMX.Net wrote:

...

I tried the following and put it into bugzilla:

On my terminal ctrl-alt-F1 at boot time, I see that my eth0& eth1 is being configured before the nfs is started. One is onboard to the mobo, the other a PCI card. I have, however, a WLan card that has the actual network, which gets configured after the nfs is started. So if the system is hard wired by ethernet cable, it works. It does not work with WLan cards, because they seem to be configured after nfs is started.On my terminal ctrl-alt-F1 at boot time, I see that my eth0& eth1 is being configured before the nfs is started. One is onboard to the mobo, the other a PCI card. I have, however, a WLan card that has the actual network, which gets configured after the nfs is started. So if the system is hard wired by ethernet cable, it works. It does not work with WLan cards, because they seem to be configured after nfs is started.

So, your suggestion does not work, because the WLan card only gets configured later. You might want to check this thread and especially post #13 http://forums.opensuse.org/showthread.php?t=460259 Hi Dave,

I had a look at the bug. I changed the config, but it only caused the attempt to start the nfs to report that the "network is unreachable" during boot time and it goes straight through without mounting the nfs. I have to manually mount afterwards. Another problem seems to be the " low NFS performance. Misconfiguration or protocol limitation?" reported by listas.correo (mailing lists - 09/12/10). It is pathetic, and seems to be a little faster (but just a little) with cable. While typing this mail the cursor sometimes stops and when I click to a new mail, it takes up to 10 seconds before it is opened over the nfs network mount. It is not acceptable at all. It seems nfs is all messed up in 11.4; what changed? In 11.1 it was still quite good - used a lot of it (I skipped the others, and with 11.4 I should have done the same; I got many other problems <besides nfs> on the system where 11.1 worked perfectly)>:o . !! NCARS !! Only if you have nothing else to do for a few weeks and want to do some banana care (the software ripens at the customers) - Why did these problems not come up in beta testing? :-( Al -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 07/06/2011 12:31 AM, Tim Hempstead wrote:

On Wed, Jul 6, 2011 at 12:24 AM, LLLActive@GMX.Net wrote:

...

On 01/05/11 18:16, Stan Goodman wrote:

...

On Sunday 01 May 2011 at 19:02:27 (GMT+2) Wolfgang Mueller wrote:

...

On 05/01/11 14:39, Stan Goodman wrote:

...

The client is on a v11.4 laptop. The entries in YaST> NFS client are:

Server: poblano Remote directory: /home/stan Mount point: /home/stan/nfs/poblano (which exists) NFS type: nfs Options: default (for the time being) NFSv4 is unchecked Firewall port is open on all interfaces (for the time being)

fstab contains the line: "poblano:/home/stan /home/stan/nfs/poblano nfs defaults 0 0"

An attempt to write this configuration results in: "Unable to mount NFS entries from /etc/fstab"

I must be doing something foolish, but I don't see it.

Did you configure the server's export file? If not, add the following line to poblano:/etc/exports

Here are the entries in YaST> NFS Server (in poblano):

Start server is checked Directories to export: /home/stan Hosts: chipotle (the laptop) Options: rw,root_squash,sync,no_subtree_check (just as you now suggest)

I think that already does what you write below.

...

+-----

| /home *(rw,root_squash,sync,no_subtree_check)

+-----

or, if you want to limit the nfs access to /home/stan only:

+-----

| /home/stan *(rw,root_squash,sync,no_subtree_check)

+-----

Yast may help you to do this. Select "NFS Server" in "Network Services".

It usually does, but it seems not to help now. As I have been doing for many moons, I have been doing all this configuration in YaST. Something else must be missing.

...

Bye, Wolfgang

Hi all,

I have come across this problem today. I have two openSUSE 11.4 systems, one as NFS Server and the other as user with all its data on the NFS server. The idea is to centralise the data pool of 6 systems, on a raid 10 system that also acts as file/nfs server and making DAR backups with scripts and cron onto USB external disks. So the NFS is crucial. I do not have Samba or any Win systems.

The problem started with not being able to get NFS to work at all between the newly installed 11.4 system (server) and 11.1 systems. I then did a NFS client setup with yast on a 11.4 system, and the NFS client could not mount the fstab nfs mounts when it completes the setup. Manually mounting was without problems.

That led me to this thread.

Then I restarted the 11.4 client system, and it hung at the point where the nfs "Starting NFS client services: sm-notify" and then "Mounting network file systems ... mount.nfs: connection timed out" occurs. NFS is not mounted, because it tries to mount before the network is up.

This turned out to be a bug: 694461 - mount.nfs starts before the network is up!I get the NFS to mount with a script before I can get to my data, but this is very unsatisfactory. There has been no movement since 16-06-2011, only some workaround.

I found using NFS 3 on both systems to be more stable. On a Mac and Linux WLan the drives and some directories would sometimes report " .... *.odt does not exist". On the NFS Server I also had to clean the /etc/exports by hand, redo the server config with yast, because it caused the "cannot mount nfs in fstab" error that the first problem has, i.e. it does not configure in the clients. Once I got everything cleaned and as NFS3, all works, besides the mount problem at boot time.

Any ideas to fix the bug 694461will be welcome.

Al

Shouldn't the line in fstab have _netdev instead of defaults to tell the system to attempt mounting the remote share after the network is fired up?

i.e.

poblano:/home/stan /home/stan/nfs/poblano nfs _netdev 0 0

Regards

Tim

-- Tim Hempstead thempstead@gmail.com

I suggest the following: switch over to autofs with auto.master and auto.home instead of using the fstab file. The mounts will not occur until you logon to the system. That way you can wait a minute or so to allow the wlan to come and it will allow the autofs to start after wlan. Other solutions is to change the execution order of the autofs startup with the network startup. Change the fstab with soft,intr,timeout=60. This will prevent a hard freeze up. -- Joseph Loo jloo@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org