File corruption again

Jeremy Allison jeremy at
Mon Jun 4 21:42:37 GMT 2001

On Sat, May 26, 2001 at 07:05:30PM +0200, Juergen Hasch wrote:
> Finally I found a way to trigger my problem independent of the log
> level.
> I think I spotted the place, where the file corruption comes from.
> It's in reply.c/reply_write_and_X()
> I am copying a 8628 bytes file to the Samba share:
> smb_doff= 63, smblen=8691, numtowrite=401844
> This triggers the ERRbadmem error and the created file is empty.
> Copying it a second time yields:
> smb_doff= 63, smblen=8691, numtowrite=8628
> No error and the created file is valid.

Well spotted. I'm back from Japan and trying to catch
up. Can you send me a debug level 10 for this one (or
a .cap file). It looks like in some cases the vwv10
field is non zero.

I need to understand when it's safe to look at the
vwv10 field and when it's not....


Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.

More information about the samba-technical mailing list