Bug 130170

Summary:	OpenOffice 2.0 Novell Edition has I/O-Error with NFS-Access and SMB-Access
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Karsten Kretschmer <krskrt01987>
Component:	OpenOffice.org	Assignee:	Petr Mladek <pmladek>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	pmladek
Version:	Final
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Errormessage 1 if i save the file Error Message 2 , i have accept Error # 1

Description Karsten Kretschmer 2005-10-22 22:12:20 UTC

I have to use an NFS-Server with SuSE 10.0 and Clients with this OS.
User have Access to User-Share and an Global-Share.
I have startet OO.org and will create a File.
I become an Error-Message: "Cannot create File xxxx, I/O-Interrupt-Error". 
The Name from the File in this Message is not my Filename. File was create on 
NFS-Share, but i can´t open.
I can create File locally and i can copy this File to an Server. If i open this 
File, i can this, but i can`t save this File, Error-Message .....

If i will access via SMB, i have this problem too.

I have create NFS-Server and NFS-Clients with YaST.
I have this Problem with all of my systems.

Excuse me for my bad english please.

Comment 1 Karsten Kretschmer 2005-10-22 22:17:42 UTC

Created attachment 55162 [details]
Errormessage 1 if i save the file

Comment 2 Karsten Kretschmer 2005-10-22 22:19:29 UTC

Created attachment 55163 [details]
Error Message 2 , i have accept Error # 1

Comment 3 M Nagashree 2005-11-02 06:18:20 UTC

I was not able to replicate the issue here, Petr, could you try it out once if possible. Thankyou.

Comment 4 Karsten Kretschmer 2005-11-07 17:55:51 UTC

I have "re-migrated" to OOorg 1.1.5 and I don´t have the problem now.

I think, with version 2.0 its a problem with the RPC, i hade problems with the kernel-based NFS-Server: error-messages from the lockd. With the daemon-based nfsserver i don´t had the problem, but this daemon doesn´t correctly run on my systems. 

OOorg 1.1.5 runs under kernel-based nfs correctly with high performance.

Comment 5 Petr Mladek 2005-11-11 17:01:05 UTC

First, I am sorry for the late response. I missed this bug by a mistake.

It is probably related to the messages from lockd. OOo-2.0 wants to create a lock when it saves a file.

Could you please try to disable locking in OOo? You can do it if you comment out or remove the the lines:
SAL_ENABLE_FILE_LOCKING=1
export SAL_ENABLE_FILE_LOCKING
from:
/usr/lib/ooo-2.0/program/soffice

Does it help?

Comment 6 Karsten Kretschmer 2005-11-11 19:24:05 UTC

I´m so happy, it´s help!!
I have comment this Line (line 43 / first uncommend line)and i can save/open/write/create all my files.
I have tested on 2 PC without problems or errors. But, behind an update of OOorg you must new edit this file. 

This problem dosn´t longer exist.

Thank you Petr!

Comment 7 Tim Fechtner 2006-01-13 21:29:54 UTC

http://qa.openoffice.org/issues/show_bug.cgi?id=54586 gives details informations over this topic.

Comment 8 Tim Fechtner 2006-01-15 12:54:39 UTC

It doesn't work because OOo 2.0 uses file locking by default and there is a problem with file locking over nfs, see bug 128784.

Comment 9 Karsten Kretschmer 2006-01-15 13:29:11 UTC

I have comment the Lines (line 43 and 44 / first and second uncommend line)and i can save/open/write/create all my files now.
I have tested on 2 PC without problems or errors. But, behind an update of
OOorg you must new edit this file. I have migrateted to StarOffice 8 SP1, i have comment the Lines in file "soffice" (/opt/staroffice8/program/soffice), i have not problems.
Ihave tested with NFS an smbmount, no problems. 
My Server and Client-OS is SuSE 10.0

Comment 10 Petr Mladek 2006-02-09 10:18:08 UTC

Well, I epxect that the problem will locking is fined on SL 10.1/SLES10/NLD10.

Olaf, did we provide a fixed kernel for SL 10.0?

Comment 11 Tim Fechtner 2006-02-21 07:47:49 UTC

Yes, there is a patch for the kernel. So the problem is fixed.