[Samba] File writing strangeness

Chris Nighswonger cnighswonger at foundations.edu
Tue Feb 22 14:20:32 MST 2011

 On Tue, Feb 22, 2011 at 5:26 AM, Volker Lendecke <Volker.Lendecke at sernet.de
> wrote:

> On Mon, Feb 21, 2011 at 03:53:17PM -0500, Chris Nighswonger wrote:
> > All sorts of file reads/writes/etc. to any part of this share work fine
> for
> > any user with a singular exception. This exception occurs when a very
> > antiquated piece of DOS based software attempts to write a zip backup
> file
> > to the share. The attached tcpdump packet summary shows the error at
> around
> > number 1069. It appears that samba responds to a request for information
> > about the backup file with STATUS_NO_SUCH_FILE, which is, in fact, not
> true
> > based on a directory listing via a shell prompt on the samba box. A check
> of
> > perms on the file in question shows that they are correct for the
> operation
> > being attempted. Ie.
> Please send the raw network trace and a debug level 10 log
> of smbd during that attempt. Information on how to create
> useful network traces can be found under
> http://wiki.samba.org/index.php/Capture_Packets

Attached is the verbose debug output of this client from the time it
connects to the time the problem occurs. I've sanitized it a bit. I've not
figured out how to sanitize the tcpdump, so it is not attached at present.

To my uninitiated eyes, it appears that the transaction with the problem
begins about line 4199 with the creation of MPLUSWIN.ZIP. At line 4373 I see
a delete_on_close flag set which later results (as I would expect) in the
file being presumably deleted at 4462. A bit later at 4718 the
status is sent along to the client.

This is strange as a check of that directory shows the file still exists
albeit of 0b length.

I'm sure having the full tcpdump would help, but until I can sanitize it,
I'll have to hold off posting it.

Kind Regards,

More information about the samba mailing list