Re: Incomplete file listing with Samba on ext2fs

2007-11-08 Thread Rainer Schwarze
Rainer Schwarze wrote:
 CyberLeo Kitsana wrote:
 Rainer Schwarze wrote:
 I created 1000 files named file000 ... file0999 in a directory. I
 could see all of them via Windows.

 I created 1000 files named file-.file ... file-0999.file in a
 directory. I could see the first 130 files of them.
 Are you sure this is only happening with ext2fs? You might be running
 into a filename mangling limitation in Samba.
[...]
 However, everything works well when I put the same set of files on a UFS
 volume shared by samba. 

Just an update in case someone looks for the same problem:

On the samba mailing list it was pointed out, that there are problems
with non-UFS shares. In /usr/ports/UPDATING this snippet is included
(which as it looks like I did not read carefully :-) ):

| 20070919:
|   AFFECTS: users of net/samba3
|   AUTHOR: [EMAIL PROTECTED]
[...]
|   Bug #4715 (https://bugzilla.samba.org/show_bug.cgi?id=4715) is NOT
|   fixed yet, although it won't core dump smbd process any more. Still,
|   access to the shares other than UFS is not guaranteed.

Best wishes, Rainer
-- 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Incomplete file listing with Samba on ext2fs

2007-11-06 Thread Rainer Schwarze
CyberLeo Kitsana wrote:
 Rainer Schwarze wrote:
 I created 1000 files named file000 ... file0999 in a directory. I
 could see all of them via Windows.

 I created 1000 files named file-.file ... file-0999.file in a
 directory. I could see the first 130 files of them.
 
 Are you sure this is only happening with ext2fs? You might be running
 into a filename mangling limitation in Samba.

That was my first interpretation after the test case with the filenames.
However, everything works well when I put the same set of files on a UFS
volume shared by samba. When copying the same set of files to another
directory on ext2fs the directory listings are still incomplete. It
happens with the test data as well as with real life file sets. When I
create the files starting at  I can see the files with the number
 to 0128, when I create them starting at 0999 down to , I can
see 0999 to 0871. So I think it doesn't look like filename mangling
problems.

To me it looks like smbd retrieves the first subset of files which fit
into an internal memory block, returns that and does not get the next
subset of files from the directory. I read a problem like that for
another scenario but unfortunately can't locate it any more.

Best wishes, Rainer
-- 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Incomplete file listing with Samba on ext2fs

2007-11-05 Thread Rainer Schwarze
Hi,

I've set up a FreeBSD6.2 machine and moved my file server disk from a
Linux system where it was used before. The disk uses ext2fs. In FreeBSD
I can see all files, when looking at the samba shares from a Windows
2000 system, I do not see all files. I also do not see all files when
using smbclient on FreeBSD.

A test case went like that:

I created 1000 files named file000 ... file0999 in a directory. I
could see all of them via Windows.

I created 1000 files named file-.file ... file-0999.file in a
directory. I could see the first 130 files of them.

I added this to my smb.conf, because I found related information on the
web and this fixed some problems with incomplete directory listing which
I encountered a few days ago:

   dos charset = CP850
   unix charset = UTF-8
   display charset = LOCALE

When I copy my large list of files to a UFS volume, I can see the full
listing via Windows.

Apart from switching the ext2s to ufs, does someone has other
suggestions for solving the problem?
Do you suggest another group for this question?

Thanks in advance and best wishes,
Rainer
-- 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]