Very strange samba problem

Very strange samba problem

Post by patz » Wed, 08 Oct 2003 18:13:35


Hi everyone,

I have stumbled across a perplexing problem with the Samba client
2.2.7a/9.2 on Linux Mandrake 9.0.

I have set up a number of shared directories that reside on a windows
2000 server platform. In these directories are loads of
sub-directories containing thousands of files. All but one of these
directories are fine, however the dodgy directory does not return a
list of files on the ls or dir command. You can navigate the
sub-directories without any issues and you can copy files and
everything ok as well... you just can't list the directory contents.
You can view the files on the Windows host without any problem at all.

All the files in the folder are in lower-case, so it is not a case
mangling issue, and none of the files are corrupt.

From experimenting with adding, re-naming and moving files I have
found the following...

1. There are 90 odd files of the same type beginning with the same
sequence of 7 lower-case letters. For security purposes I cant tell
you what the sequence is but for example's sake we can use 'include'.
If you add a text file called 'include.txt' everything works fine. If
you remove it again it does not work any more.
2. If you remove one or two of these files - doesnt seem to matter
which files as long as they begin with 'include' - everything works
ok.
3. I created an exact copy of the directory and experienced the same
issues, except adding a text file did not produce any results, though
deleting and renaming files beginning with 'include' did.

As you can see this is a very strange problem and its looks like some
sort of bug with samba. Does anyone have any ideas?

Many Thanks,

Patrick
 
 
 

1. Strange samba problem

2. Samba and DST: Strange problem

My Samba server 2.2.8a is running on Solaris 2.8 as a daemon (not via inetd)

It has NOT been restarted since January

Since the DST change earlier this month, I have a strange problem.

When I map a drive to a share from a Windows 2000 client machine A, the
modified timestamp on files is off by 1 hour. But when I map to the same
share from another Windows 2000 client machine B, it is fine!

Both machines have the correct DST time right now, both report the
correct time when I do 'net time \\samba_server'

Why would one machine see different timestamps than the other? Also, my
'time offset' parameter in smb.conf is not changed from the default 0

Help? Thanks

3. Best Distro for Samba PDC + Squid Authenication to Samba PDC + Samba File Server

4. Strange way to get LAN to see Samba shares.

5. strange samba behavior

6. Strange samba performance

7. Where are samba-common and samba-client 3.0.2a for RedHat 8.0?

8. [News] Samba 4 Enters Testing Phase, Microsoft Uses 'Puppets' to Fight Samba

9. [Samba] Samba - Windows XP - common directory for users from group

10. SAMBA 2.2 vs 3.0 (was: samba considerations with OS/2 and eCS)

11. Samba X versus Samba SSP?

12. [News] Samba's Tridgell Warns About Patent Trolls and Samba's Allison Speaks About Corrupt OOXML Process

13. Samba connectivity (might be something other than samba?)

14. A few questions regarding samba from a samba and windows rookie

15. [Samba] Samba 3.0.3rc1 available for download