#134 Renaming Files Via Samba

v0.68
closed
5
2012-10-28
2006-11-21
Robbie
No

I've notived that in ver 0.68 if you attempt to change a file name to the same file name with different capitalization (green.jpg to Green.jpg) the rename does not work when chainging such via samaba. It does work however via FTP. The only way I am able to get it to work via samba is to add, delete, or change a character. Then go back and complete the revision. (green.jpg - gree.jpg - Green.jpg)

Discussion

  • Volker

    Volker - 2006-11-23

    Logged In: YES
    user_id=1598685
    Originator: NO

    This bug is not reproducible. Maybe your settings on the Services/CIFS page are incorrect.

    My settings:
    Dos charset = CP850
    Unix charset = UTF-8

     
  • Peter

    Peter - 2006-12-02

    Logged In: YES
    user_id=1621489
    Originator: NO

    I have the same issue, with my settings in Services/CIFS correct.
    Happens always (or in other words, changing just CAPS in filnames over Samba not possible).

     
  • Olivier Cochard-Labbe

    Logged In: YES
    user_id=1370551
    Originator: NO

    I've got the same problem: From my XP station, I can't rename a file with a new case (toto => Toto).

    But it seem normal comportement.
    Here is the notes about the Samba and case management (FreeNAS use the default value):

    smb.conf options are:

    case sensitive = yes/no/auto

    controls whether filenames are case sensitive. If they aren't, Samba must do a filename search and match on passed names. The default setting of auto allows clients that support case sensitive filenames (Linux CIFSVFS and smbclient 3.0.5 and above currently) to tell the Samba server on a per-packet basis that they wish to access the file system in a case-sensitive manner (to support UNIX case sensitive semantics). No Windows or DOS system supports case-sensitive filename so setting this option to auto is that same as setting it to no for them. Default auto.
    

    default case = upper/lower

    controls what the default case is for new filenames (ie. files that don't currently exist in the filesystem). Default lower. IMPORTANT NOTE: This option will be used to modify the case of all incoming client filenames, not just new filenames if the options case sensitive = yes, preserve case = No, short preserve case = No are set. This change is needed as part of the optimisations for directories containing large numbers of files.
    

    preserve case = yes/no

    controls whether new files (ie. files that don't currently exist in the filesystem) are created with the case that the client passes, or if they are forced to be the default case. Default yes.
    

    short preserve case = yes/no

    controls if new files (ie. files that don't currently exist in the filesystem) which conform to 8.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced to be the default case. This option can be used with preserve case = yes to permit long filenames to retain their case, while short names are lowercased. Default yes.
    

    By default, Samba 3.0 has the same semantics as a Windows NT server, in that it is case insensitive but case preserving. As a special case for directories with large numbers of files, if the case options are set as follows, "case sensitive = yes", "case preserve = no", "short preserve case = no" then the "default case" option will be applied and will modify all filenames sent from the client when accessing this share.

     
  • Peter Ivan Dunne

    Logged In: YES
    user_id=1276920
    Originator: NO

    I have similar problems renaming files on winxp over lan, I think this issue is with Windows, I have also noticed same behaviour when attempting to rename local files and same on win nt 4 & win 2000

     
  • eSpy

    eSpy - 2007-12-30

    Logged In: YES
    user_id=1954145
    Originator: NO

    Everything works fine for me with samba in 0.686b3...

     
  • SourceForge Robot

    Logged In: YES
    user_id=1312539
    Originator: NO

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks