Red Hat Bugzilla – Bug 193964
F_WRLCK flock on samba mount disallows reads from other fds
Last modified: 2007-11-30 17:11:34 EST
Description of problem:
I have FC5 running on a laptop & a server with samba running. When I try to
create a link between 2 calc files on the server, it does not work (it use to
work without problem on FC3)
Version-Release number of selected component (if applicable):
Lastest rpm package updated thru YUM.
Group : Applications/Productivity
Source : openoffice.org-2.0.2-5.12.2.src.rpm
Build Time : Tue May 23 20:40:29 2006
Install Time : Tue May 30 12:42:32 2006
License : LGPL
How reproducible: ALWAYS
Steps to Reproduce:
1. create on the laptop 2 spreadsheets: essai1.ods & essai2.ods
2. save them to the server thru the samba drive
3. keep both docs opened and from essai1 try to link to a cell on essai2
4. the result is '#NOM ?' (i have a french version, in English it must be #NAME ?)
-> the link is not created
If the files are located on the laptop, the link is created.
What is the text of the formula that gives "#NOM ?", i.e. click on it and copy
and paste the text that appears in the formula editor e.g. is it something like
or something like
Here is the text :
I will also attach my 2 files essai1 & essai2
Created attachment 130451 [details]
Created attachment 130452 [details]
I have done other tests and it might be linked to capital letters. My folder
"/mnt/serveur/aaa" is in fact "/mnt/serveur/AAA" and it might be the reason why
he cannot create the link.
If i save a new set of essai1 & 2 files into a new folder called
"/mnt/serveur/bbb" (no capital letter) the problem disappear.
This issue is very annoying. Can I do anything to help you to solve it ?
I wasn't able to reproduce this, but what are the details of the samba server,
is it windows or samba itself. and when you type "mount" on the client, what is
the line for /mnt/serveur, perhaps some casemapping option is being used, or not
The samba server works on a FC5 server. His config file is :
# Samba config file created using SWAT
workgroup = MYGROUP
netbios name = SAMBA
server string = Samba Server
log file = /var/log/samba/%m.log
max log size = 1000
ldap ssl = no
hosts allow = 127.0.0.1, 192.168.0.
hosts deny = all
comment = Home Directories
read only = No
On the laptop (running also FC5) I mount the server thru /etc/fstab with the
following line :
//192.168.0.4/bg /mnt/serveur cifs rw,uid=bgirin,username=xx,password=xx 0 0
where 192.168.0.4 is the ip address of the server.
I can reproduce now, will get onto it
Please try this for me...
as root edit the script
# file locking now enabled by default
to be instead
# file locking now enabled by default
i.e. comment those two lines out
and tell me if that "fixes" it
Created attachment 132003 [details]
simple lock test
./a.out /mnt/serveur/AAA/essai1.ods lock
./a.out /mnt/serveur/AAA/essai1.ods unlock
The "case mapping" led me astray, calc makes the text of a failed operation into
lowercase, the problem is simply that once the document has been opened with a
read-write lock over cifs, then it cannot be opened simultaneously and read from.
> oocalc /mnt/serveur/AAA/essai1.ods &
> cp /mnt/serveur/AAA/essai1.ods /tmp
Once the cock-up has occured, OOo lowercases the failed text so that's what's
there on save. Presumably if you then close the referred doc, and move it to a
location which is equal to the new wrong string it'll find it again, but that's
neither here nor there.
caolanm->fenlason: Is this strict locking a feature or bug ?
I have followed your instruction i.e. commenting the 2 lines in
/usr/lib/openoffice.org2.0/program/soffice and that has fixed the bug for me. I
have tried several tests, with different files and all are working now. Thank
you very much for solving this issue !
This is working as expected, if OpenOffice.org fails to deal properly with
locking I'd say it is an OpenOffice.org bug.
Please Reopen if you have more info that lead to think it is a samba bug instead.