Jan Evert van Grootheest
2002-Jul-23 06:30 UTC
[Samba] strange files appearing after file copy
Hello,
I just had something strange happen and could not find explanations in
the documentation, FAQs or mailing list.
The server is a Debian installation running Samba 2.2.3 (kernel 2.4.18
if interested). It has been recently upgraded from 2.0.x (I think x=6).
My smb.conf is at the bottom; the directory used is on the [public]
share.
The client runs Win2k (probably SP2).
I copied some files in the windows explorer to an existing directory on
the server. Somehow, I got more files on the server than I copied! And
the had all those funny filenames, like abcd.jpg:{aksdjlkjl}:$DATA in
addition to abcd.jpg that I copied.
Here are some real world examples:
2002_0626_211216AB.JPG:?Q30lsldxJoudresxAaaqpcawXc:$DATA
2002_0626_211216AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
2002_0626_213753AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
2002_0626_213759AB.JPG:?Q30lsldxJoudresxAaaqpcawXc:$DATA
2002_0626_213759AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
2002_0626_213953AB.JPG:?Q30lsldxJoudresxAaaqpcawXc:$DATA
2002_0626_213953AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
2002_0626_220822AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
2002_0626_220857AB.JPG:?Q30lsldxJoudresxAaaqpcawXc:$DATA
2002_0626_220931AB.JPG:?Q30lsldxJoudresxAaaqpcawXc:$DATA
2002_0626_220931AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
The ones with *:{*}:$DATA look like they have a class id between {}, but
they can't be found in the registry. The others I don't readily
recognize.
Some of these files are empty, some contain a few Kb of data.
Also, such files are not created for all files that are copied....
What are these files? Can I safely remove them? Is this due to the
upgrade and are there some new directives that I need to add in the
samba configuration?
Any hints and/or clues are appreciated.
-- Jan Evert
[global]
printing = bsd
printcap name = /etc/printcap
load printers = yes
guest account = nobody
invalid users = root
security = share
interfaces = eth0 127.0.0.1
bind interfaces only = yes
workgroup = JANEVERT
netbios name = server
server string = %h server (Samba %v)
syslog only = no
socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096
SO_RCVBUF=4096
encrypt passwords = yes
wins support = no
domain master = yes
local master = yes
name resolve order = host bcast
dns proxy = no
preserve case = yes
short preserve case = yes
unix password sync = false
max log size = 1000
[printers]
comment = All Printers
browseable = no
path = /tmp
printable = yes
public = yes
writable = no
create mode = 0700
[public]
comment = Shared disk
path = /pub/samba/share
public = yes
writable = yes
printable = no
guest only = yes
browseable = yes
[extradrive]
comment = Extra disk space for other machines
path = /pub/samba/%m
writeable = yes
browseable = yes
guest only = yes
printable = no
public = yes
fake oplocks = yes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2072 bytes
Desc: S/MIME Cryptographic Signature
Url :
http://lists.samba.org/archive/samba/attachments/20020723/e1599c0e/smime.bin
On Tue, Jul 23, 2002 at 03:28:12PM +0200, Jan Evert van Grootheest wrote:> Hello, > > I just had something strange happen and could not find explanations in > the documentation, FAQs or mailing list. > The server is a Debian installation running Samba 2.2.3 (kernel 2.4.18 > if interested). It has been recently upgraded from 2.0.x (I think x=6). > My smb.conf is at the bottom; the directory used is on the [public] > share. > The client runs Win2k (probably SP2). > > I copied some files in the windows explorer to an existing directory on > the server. Somehow, I got more files on the server than I copied! And > the had all those funny filenames, like abcd.jpg:{aksdjlkjl}:$DATA in > addition to abcd.jpg that I copied. > Here are some real world examples: > > 2002_0626_211216AB.JPG:?Q30lsldxJoudresxAaaqpcawXc:$DATA > 2002_0626_211216AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA > 2002_0626_213753AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA > 2002_0626_213759AB.JPG:?Q30lsldxJoudresxAaaqpcawXc:$DATA > 2002_0626_213759AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA > 2002_0626_213953AB.JPG:?Q30lsldxJoudresxAaaqpcawXc:$DATA > 2002_0626_213953AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA > 2002_0626_220822AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA > 2002_0626_220857AB.JPG:?Q30lsldxJoudresxAaaqpcawXc:$DATA > 2002_0626_220931AB.JPG:?Q30lsldxJoudresxAaaqpcawXc:$DATA > 2002_0626_220931AB.JPG:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA > > The ones with *:{*}:$DATA look like they have a class id between {}, but > they can't be found in the registry. The others I don't readily > recognize. > > Some of these files are empty, some contain a few Kb of data. > > Also, such files are not created for all files that are copied.... > > What are these files? Can I safely remove them? Is this due to the > upgrade and are there some new directives that I need to add in the > samba configuration? > Any hints and/or clues are appreciated.Known bug we fixed for 2.2.5, I would recommend an upgrade. Cheers, Jeremy.