[Samba] File size is sometimes 0 after saving

[Jeremy Allison]

On Tue, Jun 24, 2014 at 01:04:21PM -0700, Jeremy Allison wrote:
> On Tue, Jun 24, 2014 at 05:44:58PM +0200, Matthias Heinz wrote:
> > Hi,
> > 
> > this may sound odd, but now I had the same problem while using the
> > windows explorer to copy a file over another file. It got an error
> > message, the file size of the file I wanted to overwrite was
> > suddenly 0 (I double checked with "file" on the server and it just
> > said empty), but I could in no way overwrite the file.
> > 
> > It was the same as describe before. The file was owned (unix user
> > rights here) by another user and I had to use chown to change the
> > user to mine to write the file in the end.
> > 
> > Has really nobody else experienced such problems before and may a
> > hint where to look for the error?
> > 
> > 
> > Best regards
> > Matthias
> > 
> > 
> > On 16.06.2014 16:47, Matthias Heinz wrote:
> > > [...]
> > >What we experience is that some programs (e.g. Inkscape) have problems
> > >saving files sometimes. It manages to access the file and to erase
> > >everything in it (that's my guess), but then fails somehow to write it
> > >again, leaving the file size 0. Most oft the time this happens when the
> > >file itself belongs to another user (as I said above, we only enforce a
> > >common group on the share). I say most of the time, because I only can
> > >reproduce it when the file itself belongs to another user. A colleague
> > >mentioned that he had problems with his own files, too, but I have no
> > >proof here.
> > > [...]
> 
> If this is with 4.1.x, then it's probably bug #10671.
> 
> https://bugzilla.samba.org/show_bug.cgi?id=10671
> 
> Fix (along with regression test) will be posted *very* soon :-).

Fix for 4.1.x is posted to that bug, and original
reporter has confirmed it fixes the problem.