Red Hat Bugzilla – Bug 416151
Directory listing fails. Only half is given on some dirs, but no error at client side!
Last modified: 2007-12-08 09:25:42 EST
Description of problem:
When certain directories are listed only part of the contents are listed.
Sometimes one file (the last to be sent?) is look strange (chopped name, or
zero-sized). Note that is is on the clientside, where no error is received. I
thought I been hacked when half of my files went missing!
Version-Release number of selected component (if applicable):
The problem began with the lasted update of samba.
Hard to tell since I do not know why it happen.
Steps to Reproduce:
1. List a directory on samba server. (Tested with Vista and XP client)
2. Look for a file with an incorrect name or size.
3. Check fileproperties on incorrect file. Should fail.
Some files are missing in the listing, and at least one file is displayed
incorrect. I really can't understand why it only happens on some directories,
and not all.
Complete and correct directory listing transfered and displayed.
Created attachment 281651 [details]
Deleted all files in log directory, and then done one access (which fails, se above)
Been playing around some more. This problem has to do with large directory
listings. Adding files to an directory will get samba listing to fail at a
Here is a better way to reproduce:
1 Create directory "Test" in a share.
2 Create file "Test.txt" in the directory.
3 Copy file (Ctrl-C) "Test.txt", and paste it.
There will now be two files, "Test.txt" and "Test - Kopia".
4 Mark and copy all files (Ctrl-C) and paste.
(Step 2: "Test.txt", "Test - Kopia.txt", "Test - Kopia - Kopia.txt",
"Test - Kopia (2).txt")
5 Run step 4 until directory contains 128 files. (7 steps totaly)
Results: Listing is crippled once again. Only 97 files are shown at client,
and one of the files is not displayed correctly, and all operations on it fails.
(file do not exist).
When deleting files in directory test, there comes a point where listing become
correct and complete.
Same problem as 410441. Sorry for bothering. SOLVED.
*** This bug has been marked as a duplicate of 410441 ***