Issue 65002

This bug affects all components, likely a framework issue.

Yes I have always had this problem through versions of v2.
Over Samba and over NFS mounts. Works OK for me on local volumes.
Would be nice if it gets fixed oneday....

Please could you replicate this issue with openoffice.org version 2.1 and see if
it still  occurs. 

yes.
same problem with 2.1.0 version.

I can confirm this bug on OOo 2.1.0 running on gentoo. Disabling locking
(mount.cifs's nolock mount option) does not help.

I can confirm this with version 2.1 on both Linux and Windows, and in Calc and
Writer.  

I have a system running Gentoo, using a binary install of OpenOffice 2.1.  In
both Writer and Calc (I have not tried the other parts of OpenOffice) whenever I
click the Save icon to save a document that is stored on my Samba server it
pauses for a couple seconds and pops up a dialog box to report it could not
create a backup.  If I click OK on the dialog box, then immediately click the
Save icon again it saves the file without complaint.  During the first attempt
it not only does not create a backup, it does not actually save the file.  

At work I use a Windows XP computer and save files to a file server running
Windows Server 2003.  Again, I'm using OpenOffice.org 2.1.  In both Writer and
Calc I can open up a file from the server, make some changes and click the Save
icon.  The first time I click save after opening the document it saves without
incident.  Every subsequent time I modify and click Save OpenOffice freezes for
a few minutes before popping up a dialog box saying "Could not create backup
copy."  Again, if I click OK and immediately click Save again it saves quickly
and without problem.  

I've noticed this issue in the 2.0.x versions of OpenOffice on Linux and this is
not a very big problem on Linux because the freeze is for only a second or two
and I can just hit Save again immediately to successfully save my file.  

This is a big problem in Windows because the application freezes for minutes
instead of seconds, and all open OpenOffice windows freeze, so if I'm working
with a spreadsheet and a couple of Writer documents, I click Save in any one of
these open files and all work on any open file is halted.

This only happens for files that are opened from network shares, if the file is
on my local hard drive this does not happen in either Linux or Windows.  

In both of the above scenarios I have unchecked the "Always create backup copy"
checkbox in the Options dialog.  I have not changed the default backup path on
either system, I can confirm that the Windows XP default backup path is pointing
to a folder on my C: drive.

I believe this Issue needs to be escalated to include multiple components and
multiple operating systems.

ds

I can confirm this with version 2.1 on both Linux and Windows, and in Calc and
Writer.  

I have a system running Gentoo, using a binary install of OpenOffice 2.1.  In
both Writer and Calc (I have not tried the other parts of OpenOffice) whenever I
click the Save icon to save a document that is stored on my Samba server it
pauses for a couple seconds and pops up a dialog box to report it could not
create a backup.  If I click OK on the dialog box, then immediately click the
Save icon again it saves the file without complaint.  During the first attempt
it not only does not create a backup, it does not actually save the file.  

At work I use a Windows XP computer and save files to a file server running
Windows 2003 Server.  In both Writer and Calc I can open up a file from the
server, make some changes and click the Save icon.  The first time I click save
after opening the document it saves without incident.  Every subsequent time I
modify and click Save OpenOffice freezes for a few minutes before popping up a
dialog box saying "Could not create backup copy."  Again, if I click OK and
immediately click Save again it saves quickly and without problem.  

This only happens for files that are opened from network shares, if the file is
on my local hard drive this does not happen in either the Linux/Samba
environment or in the Windows environment.  

In both of the above scenarios I have unchecked the "Always create backup copy"
checkbox in the Options dialog.  I have not changed the default backup path on
either system, I can confirm that the Windows XP default backup path is pointing
to a folder on my C: drive.

I believe this Issue needs to be escalated to include multiple components and
multiple operating systems.

Related to  Issue 70600?

*** Issue 70600 has been marked as a duplicate of this issue. ***

*** Issue 65002 has been confirmed by votes. ***

Hi,

as it seems to affect all applications, component changed to framework and
re-assigned.

Frank

Try setting option "oplocks = no" in smb.conf. It helped in my case.

("locking = no" -- helped also but IT IS NOT RECOMMENDED because lack of locking
may result in data corruption)

All the best
Jan Kaliszewski

PS.

> I didn't select to "always save backup copy" in the OO options, i tried to
> change the default path of the backup copy with no result.

That "can't create backup copy" message is annoying (so it's a bug?). The file
which doesn't want to be written is the file you trying to save, not a backup copy.

All the best.

PS2.
With a backup copy also is that problem -- if you turn on "always save backup
copy" option (then you get "can't create backup copy" message twice).

PS3.
> Try setting option "oplocks = no" in smb.conf
...on the Samba server of course -- if you have access to server conf.

please consider that from opensuse10.2 , for example, smbfs module isn't
compiled in the default kernel so a normal user will have this annoying problem
with cifs module that is the only way to mount windows shares.
So i think this bug have to be solved sooner as possible.....

regards

This bug is serious as samba ships with oplocks = yes by default.

Can we have the source of the problem explained?

File locking (at least with flock()) seems to work as expected under cifs
mounted shares using the default samba config.

What causes this problem and why does it dissapear with 

oplocks = no 

on smb.conf?

Hi,

I make some test with this interesting results: the problem (ie can't create
backup copy when file is stored on a cifs filesystem) only occurs if the format
of the document is o?t. If the file is txt, html, doc, xml, ... I can save it
without  get "can't create backup copy" message.

I expect this information help to solve the problem as soon as possible.

Josep

Happens also with xls files (and sx*).

Hi,

Although saving in txt, doc, ... doesn't appear "can't create backup copy"
message, serious problems with file locking continue (same problems as with OO
formats) :-(

Josep

Following Novell support advice, I tried the CIFS mount option "nobrl". That
immediately and entirely solved all of these problems for me.

For the archives, this is what I had been told by Suresh Jayaraman from Novell:

' Please try "nobrl" mount option and see whether the problem is fixed. This
option allows to not send byte range lock requests to the server. This is
necessary for certain applications that break with  cifs  style mandatory byte
range locks (and most cifs servers do not yet support requesting advisory byte
range locks). '

He wasn't able to reproduce the failures, however my samba host is a windows
2000 server box, and that is the only environment he wasn't able to get hold of.
Maybe others experiencing problems could comment here what operating system
their samba hosts are running on?

I saw problems on shares at WinXP Pro sp(whatever) and WD Netcenter network 
drive (no idea, what  its is running, maybe Linux).