On Thu, Jul 11, 2013 at 10:42:05AM +1000, Craig Sanders wrote:
Has anyone else experienced this? Anywhere I should look?
a google search for 'libre office NFS freeze'
the second search result was the LibreOffice 4.0 ReadMe which says: http://www.libreoffice.org/get-help/readme ---------------------------------------------------------------------- File Locking ---------------------------------------------------------------------- File locking is enabled by default in LibreOffice. On a network that uses the Network File System protocol (NFS), the locking daemon for NFS clients must be active. To disable file locking, edit the soffice script and change the line "export SAL_ENABLE_FILE_LOCKING" to "# export SAL_ENABLE_FILE_LOCKING". If you disable file locking, the write access of a document is not restricted to the user who first opens the document. Warning: The activated file locking feature can cause problems with Solaris 2.5.1 and 2.7 used in conjunction with Linux NFS 2.0. If your system environment has these parameters, we strongly recommend that you avoid using the file locking feature. Otherwise, LibreOffice will hang when you try to open a file from a NFS mounted directory from a Linux computer. I think the issue is a lot more wide-spread than is suggested here - i doubt if your NAS is running Solaris. and NFS v2 is truly ancient. v3 has been the default for ages. hmmm. another solution might be to check if your NAS can do NFS v4 and tell your Linux machine to mount it with that instead of NFS v3. you can use rpcinfo to find out what versions of NFS are available on your NAS. rpcinfo -u YOUR-NAS-SERVER-IP nfs e.g. you'd see something like this: # rpcinfo -u localhost nfs program 100003 version 2 ready and waiting program 100003 version 3 ready and waiting program 100003 version 4 ready and waiting if nfs v4 is available, then changing to it is probably as simple as unmounting the NFS mount, editing /etc/fstab to change 'nfs' to 'nfs4' and then remounting the share. NOTE HOWEVER, that this may not fix the problem....but it's worth a try if anything else needs to lock files on the NFS server, and especially if it's shared with multiple simultaneous users. disabling locking may solve the symptom, but it's a pretty drastic solution that may end up causing other problems (in particular, file corruption if two or more processes open a file for write at the same time) craig -- craig sanders <cas@taz.net.au> BOFH excuse #99: SIMM crosstalk.