Error: "failed to change delete on close flag" in 2.2.8 (JYC 17-Aug-05)

[BG - Ben Armstrong]

Hi,

Is anyone else seeing these in SAMBA_LOG logs?

[2005/08/26 08:53:12, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_8-SRC.SOURCE.SMBD]TRANS2.C;9:(2229)
  set_delete_on_close_internal: failed to change delete on close flag for file Dymax/020005/VIM2E.tmp
[2005/08/26 08:53:21, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_8-SRC.SOURCE.SMBD]TRANS2.C;9:(2229)
  set_delete_on_close_internal: failed to change delete on close flag for file Dymax/020005/VIM2E.tmp
[2005/08/26 08:53:21, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_8-SRC.SOURCE.SMBD]CLOSE.C;11:(165)
  close_normal_file: failed to change delete on close flag for file Dymax/020005/VIM2E.tmp

The user is merely trying to edit a file.  Cream (our PC text editor,
used to edit files on a Samba share) warns that the file is not writable
and asks the user to open anyway or cancel.

If a different user tries to edit the same file, the error is not
thrown.  When I try to get the first user to edit the same file again,
the error persists, and more error messages are logged in their log
file.

We had the same problem running one of our Ruby benchmark programs that
opens, writes to, and then deletes a temporary file.  The delete threw
an error.  Also, in DOS shell the delete threw an "Access denied" error.
The log entries look quite similar:

[2005/08/25 09:17:37, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_8-SRC.SOURCE.SMBD]TRANS2.C;9:(2229)
  set_delete_on_close_internal: failed to change delete on close flag for file dm/BENCH.TMP
[2005/08/25 09:17:45, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_8-SRC.SOURCE.SMBD]TRANS2.C;9:(2229)
  set_delete_on_close_internal: failed to change delete on close flag for file dm/BENCH.TMP
[2005/08/25 09:17:45, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_8-SRC.SOURCE.SMBD]CLOSE.C;11:(165)
  close_normal_file: failed to change delete on close flag for file dm/BENCH.TMP

Not all files are affected.  The users experiencing errors can edit some
other files and delete files successfully.

This all looks vaguely familiar.  Has some patch been accidentally left
out of this version, or is this some new problem?

Ben