Found the problem to be fixed by Jeremy Alison in Samba version 3.3.3, BUG 6196: Unable to serve files with colons to Linux CIFS/VFS client.
Thanks to the Samba team for being more on top of issues than I am (of course I just spent the last three wasted days scouring the web for this tidbit ;-) Now I'll just wait for Fedora 11 to get the update, sigh :( Bob --bs On Tue, 23 Jun 2009 04:20:12 +0200, Bob Smith wrote: > To follow up on Unix Extension verification I ran the following on a > CIFS mounted share: > > $ > "testfile\/" > bash: testfile\/: Is a directory > $ > "testfile:" > bash: testfile:: No such file or directory $ > "testfile\:" > bash: testfile\:: No such file or directory $ > "testfile*" > $ > "testfile?" > $ > "testfile\"" > $ > "testfile<" > $ > "testfile>" > $ > "testfile|" > $ ls -l testfile* > -rw-r--r-- 1 rwsmith rwsmith 0 2009-06-22 19:21 testfile< -rw-r--r-- 1 > rwsmith rwsmith 0 2009-06-22 19:21 testfile> -rw-r--r-- 1 rwsmith > rwsmith 0 2009-06-22 19:21 testfile| -rw-r--r-- 1 rwsmith rwsmith 0 > 2009-06-22 19:20 testfile? -rw-r--r-- 1 rwsmith rwsmith 0 2009-06-22 > 19:21 testfile" -rw-r--r-- 1 rwsmith rwsmith 0 2009-06-22 19:20 > testfile* -rw-r--r-- 1 rwsmith rwsmith 0 2009-06-22 19:19 testfile\ > > As you can see 7 of the reserved characters can be used within > filenames--the slash "/" character I known why, but why not the colon > ":" character?!?! > > Bob > --bs > > P.S. I have also validated that this an issue when using a client with > Fedora 11 + CIFS. > > >> I didn't get any responses to my previous post "Wine broken on Samba >> shares due to colon ":" filenames" so I am re-posting with a subject to >> reflect what I now believe to the the root cause of my problems. >> >> I recently changed from mounting my home directory using NFS to >> mounting with CIFS via the pam module pam_mount.so. It turns out that I >> am having problems with many applications that are embedding any of the >> Samba reserved characters "\ / : * ? " < > |", principally the colon >> ":". Here is a short list of applications that I use that embed the >> colon in files within their respective configuration directories in the >> home directory: >> >> Evolution >> Wine >> Picasa (via wine) >> VNC >> Opera >> Pulse Audio >> Nautilus >> Rhythmbox (if your track name has a colon) >> >> Possibly many others. Some apps gracefully handle any problems, many >> others don't. >> >> I am positive that I have enabled Unix Extensions on my Samba server. >> Here is a snippet of my smb.conf for the Samba server serving the home >> shares: >> [global] >> unix extensions = yes >> case sensitive = yes >> delete readonly = yes >> >> dos charset = >> unix charset = UTF8 >> >> On my client workstation (Ubuntu Karmic Koala (latest)) I have the >> following output from /proc/fs/cifs: >> $ cat LinuxExtensionsEnabled >> 1 >> $ cat DebugData >> Display Internal CIFS Data Structures for Debugging >> --------------------------------------------------- CIFS Version 1.55 >> Active VFS Requests: 0 >> Servers: >> 1) Name: 192.168.1.4 Domain: BISLINK Uses: 3 OS: Unix >> NOS: Samba 3.3.2-0.33.fc11 Capability: 0x80f3fd SMB session status: 1 >> TCP status: 1 >> Local Users To Server: 1 SecMode: 0x3 Req On Wire: 0 Shares: >> 1) \\san01\work Mounts: 1 Type: NTFS DevInfo: 0x0 Attributes: 0x1002f >> PathComponentMax: 255 Status: 0x1 type: 0 >> >> 2) \\san01\business Mounts: 1 Type: NTFS DevInfo: 0x0 Attributes: >> 0x1002f >> PathComponentMax: 255 Status: 0x1 type: 0 >> >> 3) \\san01\finances Mounts: 1 Type: NTFS DevInfo: 0x0 Attributes: >> 0x1002f >> PathComponentMax: 255 Status: 0x1 type: 0 >> >> MIDs: >> >> I would appreciate any assistance with this issue. I will provide >> additional information upon request to anyone willing to help me look >> into this problem. >> >> Regards, >> Bob >> --bs >> >> >> -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
