Bug 12954 - Attempting to change upper case file name to lower case from windows results in no change to file
Summary: Attempting to change upper case file name to lower case from windows results ...
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.5.8
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-09 13:48 UTC by Scott Yates
Modified: 2017-08-28 01:41 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Yates 2017-08-09 13:48:27 UTC
Samba does not allow a windows box to rename a file from upper case to lower case.  I am running 4.5.8 on a Debian base, and somewhere after 4.1.17 it appears something has changed that is disallowing case change.  The freenode #samba channel suggested that it might be a regression, and directed me to file a bug.

This particular machine is not one that I am permitted to direct compile on.  I have apt access however and have updated to the latest in the stable Debian repos.

My testing has been limited to ensuring I am using the same smb.conf file that worked under 4.1.17.
Comment 1 Björn Baumbach 2017-08-24 16:09:18 UTC
Hi! I've verified that this is solved in current 4.6.7.
Changing the case of the filename is working fine with smbclient and Windows 7 and Samba does also send change notifications to other clients about this change.

Can you confirm that?

smb: \xxxxx\> ls aaaaaaaaaaaaa
  aaaaaaaaaaaaa                       A      227  Thu Aug 24 17:50:16 2017

                18447056 blocks of size 1024. 16346160 blocks available
smb: \xxxxx\> rename aaaaaaaaaaaaa Aaaaaaaaaaaaa
smb: \xxxxx\> ls Aaaaaaaaaaaaa
  Aaaaaaaaaaaaa                       A      227  Thu Aug 24 17:50:16 2017

                18447056 blocks of size 1024. 16345768 blocks available


smb: \> notify xxxxx
0001 aaaaaaaaaaaaa
0003 aaaaaaaaaaaaa
0004 aaaaaaaaaaaaa
0005 Aaaaaaaaaaaaa
0003 Aaaaaaaaaaaaa
0004 Aaaaaaaaaaaaa
Comment 2 Scott Yates 2017-08-28 01:41:15 UTC
(In reply to Björn Baumbach from comment #1)
While I am unable to test with this customer's installation, I was able to confirm correct behavior with the release you indicated on a separate vm.

Thank you.