samba - Nov 2007 - File renaming doesn't work if only case changes

Hi!

I've searched the web, but didn't find anything related to my strange
problem: when I try to rename a file or a directory on a Samba share from my
Windows-Client and I only change the case of a some characters it's ignored
and the old filename is displayed again.

Example:
 A directory "New Folder" should be renamed to "new Folder".
Thats just ignored :-(. If I rename first to "New Folder1" and then to
"new Folder" it works.

I tried that in various situations:
 * on local Windows drive: no problem
 * on Samba share from Windows-client (Explorer): problem
 * on Samba share from Windows-client (DOS): problem
 * on Samba share from Samba-Client (smbclient): no problem

My configuration:
 Client: Windows XP; SP2; latest updates
 Server: Samba 3.0.24 (Debian 4.0, Etch)

 I have set no character- or case-specific parameters in my smb.conf, I just use
the defaults.

Has anyone seen this or a similar problem?

Best regards,
Michael

-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

On Wed, Nov 07, 2007 at 02:15:38PM +0100, Michael Hofer
wrote:
> Hi!
> 
> I've searched the web, but didn't find anything related to my
strange problem: when I try to rename a file or a directory on a Samba share
from my Windows-Client and I only change the case of a some characters it's
ignored and the old filename is displayed again.
> 
> Example:
>  A directory "New Folder" should be renamed to "new
Folder". Thats just ignored :-(. If I rename first to "New
Folder1" and then to "new Folder" it works.
> 
> I tried that in various situations:
>  * on local Windows drive: no problem
>  * on Samba share from Windows-client (Explorer): problem
>  * on Samba share from Windows-client (DOS): problem
>  * on Samba share from Samba-Client (smbclient): no problem
> 
> My configuration:
>  Client: Windows XP; SP2; latest updates
>  Server: Samba 3.0.24 (Debian 4.0, Etch)
> 
>  I have set no character- or case-specific parameters in my smb.conf, I
just use the defaults.
> 
> Has anyone seen this or a similar problem?
Can you retest this with 3.0.26a please ?

I think there was a recent regression that
has been fixed.

Thanks,

	Jeremy.