samba - Oct 2001 - FW: twice delete a directory before it really is deleted

I have tested but it doesn't work

oplocks = no doesn't solve the problem.

But it's very strange. When I delete a directory on the right side it works
direct!

BTW I use Windows 2000 Prof



-----Oorspronkelijk bericht-----
Van: samba-admin@lists.samba.org
[mailto:samba-admin@lists.samba.org]Namens Bill Moran
Verzonden: vrijdag 26 oktober 2001 14:48
Aan: Edward Dekkers; SAMBA
Onderwerp: Re: twice delete a directory before it really is deleted


 -- Warning -- I'm guessing here --

Try turning off all oplocks.  Win9X has a lot of trouble with oplocks.  This
just has the sound of the Windows machine thinking it's OK to cache
information indefinately, and that sounds like broken oplock usage to me.

Also, could you let me know if that's the solution, since I'm guessing.

-Bill

On Friday 26 October 2001 08:09, Edward Dekkers wrote:
> > I've also had difficulty getting W98 to see updated versions of
files
> > when the modifications have originated at other smb clients or the
Linux
>
> console.
>
> > I put it down to newbieness infecting a config somewhere, and added it
to
>
> a
>
> > long list of such issues which are steadily evaporating as the
newbieness
> > fades.  But maybe this one's real?
>
> Yep, yep yep hang on. I think I have a related problem that I dumped by
the
> wayside a long time ago because I just couldn't get it to work.
>
> I had a diald monitoring program logging into a straight text file on a
> /home/shared public share from within Linux. The idea was that Winblows
> clients would poll this text file, updating it every so often within
> windows memory to show latest throughput statistics. The logging was
> working perfectly. I could easily 'tail-f' the file and see it grow
for
> testing purposes on the Linux box. However the Winbloze clients would load
> the file correctly always first thing in the morning. I had set the logger
> to pass values into the text file at one minute intervals, and I set the
> clients up to parse the text file every 10 or so (a refresh basically). In
> code on the clients this was done as such every 10 minutes:
>
> 1> Open the text file.
> 2> Parse statistics
> 3> Close the text file
>
> and after a while of fighting with it I even did:
>
> 4> Drop any file handles etc.
>
> Just to try to get it to work. No go. The file would not re-load WITH the
> new information. It would always re-load (bad terminology - it obviously
> didn't really re-load but you get the picture) the file as it was first
> thing in the morning. No matter how much more info was supposed to be in
> it. I dumped the project with a 'too hard' sticker on it.
>
> I was a newbie at the time too. Maybe it wasn't my fault?
>
> What am I missing? Is there a real problem?
>
> --
> Edward Dekkers (Director)
> Triple D Computer Services Pty. Ltd.
> 822 Rowley Road
> Oakford W.A. 6121
> +61 8 9397-1040
> ABN: 33 635 238 024
--
Bill Moran
Potential Technology technical services
http://www.potentialtech.com

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Martin,

On Fri, 26 Oct 2001, Martin Stuij wrote:
> I have tested but it doesn't work
> 
> oplocks = no doesn't solve the problem.
> 
   I have strong reason to believe that the oplocks bug is unrelated to
the bug you're experiencing. The problem described by Edward was when
deleting files server-side not being reflected client-side. Your problems,
seems to be that W2K cannot recursively delete directories in certain
situations.
> But it's very strange. When I delete a directory on the right side it
works
> direct!
> 
> BTW I use Windows 2000 Prof
> 
   Can you please try the following tests for me?

1) If you have a copy of Win9x, WinME or WinNT, can you repeat the test
with those clients. My tests indicates that it is W2K-specific.

2) Can you narrow down the bug by doing the following.
- Create a "FolderA" and open it up in a normal view (ie without the
  tree-like pane).
- Under "FolderA", create a subdirectory called "FolderB".
Also open up
  "FolderB".
- Try to delete "FolderA" anyway you wish. It should fail and give an
  error message. However, "FolderB" will be deleted.
- If you repeat the test with "FolderB" closed, you should be able to
  delete "FolderA"

Thanks

Eddie