Hello everyone,

This is my first time here.

I have Kubuntu Natty and Lucid running on my Laptop and Desktop respectively.
Each machine has a network drive on the other computer (NFS)

I have this frustrating behaviour. If one machine goes off (eg take the portable away) then the plasma-desktop on the other freezes. This happen regardless of which machine goes offline.

Activating krunner and checking the processes shows that plasma-desktop is in disk-sleep state. The whole plasma functionality is useless. Even killing the process and re-starting does not help.

Anyone have any thoughts on how to deal with this.

Thanks

This is a fundamental feature of the operation of a UNIX system, and a primary risk of remotely mounted file systems. In this case, using KDE nfs:// urls is recommended - which won't freeze and will fail more gracefully.

Note that it will cause problems for non-KDE applications such as OpenOffice however.

I thought there was some form of caching in such cases? What are your NFS mount options?

Hi everybody:

I am having the same issue. I installed Kubuntu 11.04 on a netbook (Asus EeePC 1015PN) including a broadcom wi-fi chip (BCM4313). I still have not figured out why, but if there is no network traffic for a while, the connection is lost even though it is still shown as active on the knetworkmanager icon. When that happens, if I open the K menu (application launcher), it freezes. I have an nfs share on my home server, mounted with the following fstab line on the netbook:

chaosfwall.invitados.org:/ /media/export nfs4 auto,proto=tcp 0 0

Is there an nfs mount option I can set to make this issue go away? Else, how does nfs:// work? Is it a kio slave, do I have to install it separately, do I write nfs:// URLs on dolphin...?

Please let me know if there is any other relevant information I can provide.

nfs:// works through KIO and establishes it's connections in a different manner I believe. KIO is resistant to failures in network connections, which is not something which is possible with remote shares mounted directly into the file system.

Thank you. I am trying to figure out how to invoke nfs:// URLs using Dolphin -something like nfs://172.16.0.1/export/shared is not working for me-, but with your help I at least now know what I am looking for.

For the time being I have found information on Ubuntu's fora indicating how to solve my networking woes, and with them my plasma-desktop issues have gone away as well, which is absolutely fantastic

Hi,

I came here by searching the forums for the same problem.

Now I'd like to use the "build in" nfs function but all I get is the message "Authorization failed, authentication not supported". Any ideas? I can connect to the shared drive if I use an entry in /etc/fstab.

Just want to bump this because of my unresolved problem ;b

If you try it without the "/export/" does it work?
Also, please post an example of the nfs:// url you are trying to use as well as a entry from your FStab.

Please be aware that if your NFS server requires authentication you will not be able to use the nfs:// method as it appears to lack support for authentication.

bcooksley wrote:If you try it without the "/export/" does it work?
Also, please post an example of the nfs:// url you are trying to use as well as a entry from your FStab.

Please be aware that if your NFS server requires authentication you will not be able to use the nfs:// method as it appears to lack support for authentication.

I'm not the one with the "export" but here's the information. The NFS server doesn't ask for a password and therefore there's no appropriate entry in the fstab. Here's an example of one share that is mounted automatically. There are some more and some of them have the option noauto.

Code: Select all

192.168.0.7:/volume1/thomas /home/thomas/DiskStation/Thomas nfs rsize=32768,wsize=32768 0 1

I tried different urls, e.g.
nfs://192.168.0.7/thomas
nfs://192.168.0.7/volume1/thomas

In theory at least, nfs://192.168.0.7/volume1/thomas should have worked. What happens when you try nfs://192.168.0.7/ ?

bcooksley wrote:What happens when you try nfs://192.168.0.7/ ?

I get the message "Authorization failed, authentication not supported"

Unfortunately it appears that your NAS is incompatible with the nfs:// KIO slave due to unknown reasons. I would suggest filing a bug report at bugs.kde.org - please include full details in your report - including if possible the version of NFS your NAS advertises.

Unfortunately no one can tell me what version of NFS is running on the NAS so I guess filing a bug report won't help that much. So I'll live with the /etc/fstab solution and cross my fingers that I don't lose the connection that often (actually it doesn't happens very often ;b )