Issue 18189 - NFS lock problem under Linux
Summary: NFS lock problem under Linux
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 1.1 RC2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-13 15:25 UTC by davide
Modified: 2004-03-19 10:35 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description davide 2003-08-13 15:25:41 UTC 
I've enabled file locking by setting the variable

SAL_ENABLE_FILE_LOCKING=1
export SAL_ENABLE_FILE_LOCKING 

into program/soffice, and I've tried to get access to file shared into an NFS area.
There are no possibility to open any file. It seems that the lock mechanism
doesn't work.

Infact if I mount the NFS area with nolock option all works. Apart the
possibility that two users can work on the same file at the same moment... 

Situation:

Server Linux RedHat 7.3 with nfs-utils-0.3.3
kernel 2.4.18

Client Mandrake 9.1 with nfs-utils-clients-1.0.1
kernel 2.4.21

Regards

Davide
Comment 1 atr 2003-08-14 07:28:45 UTC 
ATR: Hi, Thorsten, one for you. Please have a look.
Comment 2 thorsten.martens 2003-08-14 09:45:19 UTC 
TM->ddozza: Did you enable the file-locking entries in the ./soffice -
start script in the office installation directory (where OpenOffice
has been installed) by removing the hash-marks in front of the two
lines ? If you do so, file-locking should work (the second one who
tries to open the same file, only gets it readonly).
Comment 3 davide 2003-08-14 14:49:37 UTC 
Please, read carefully my first post! I think it's quite clear.

Yes, I definitely do enable. I have set file locking by enabling into
./soffice located into installation directory.... 

Moreover I've controlled all file permissions in order to be sure.

SAL_ENABLE_FILE_LOCKING=1
export SAL_ENABLE_FILE_LOCKING 

The problem is that if I enable file locking I can't open any file on
NFS mounted area !!! Neither in read only!!!

In order to get access I've to mount NFS with nolock option enabled.

This is very annoying and dangerous because:

- Normally NFS areas are directly managed by sysadm so I can't ask
them to disable such feature

- If the same area is exported via SMB to windows client there is no
way to manage lock file between SMB and NFS. So interoperaction became
dangerous.

I'm a disposal in order to do any test. I think this bug is very critic.

Davide
Comment 4 philipp.lohmann 2003-08-18 11:30:56 UTC 
Are the locking daemon as well as the stat daemons running on NFS
client as well as server ?
Comment 5 davide 2003-08-18 12:28:34 UTC 
Uhm... There is really a strange behavior. It seems that lockd dies as
I open the first file.
If I restart lockd and statd I can open the first file. Then I can't
open any file anymore.

Let me do some other tests. 

Davide
Comment 6 davide 2003-08-19 15:52:40 UTC 
It seems a problem connected with the NFS releases we are using in our
configuration.

Infact the server RH 7.2 uses nfs-utils 0.3.3 while clients Mandrake
9.1 nfs-utils 1.0. They seems that are incompatible to each other. 

So I can't confirm the issue.

Davide
Comment 7 thorsten.martens 2004-03-19 10:35:15 UTC 
.