This is a problem I get with various versions of Samba, up to and including 2.0.7. (The version shipped with Debian.) I have an NT machine (4.0, service-pack 3 using NTFS) exporting a filesystem to Linux through smbmount. Specific directories are not browsable. By that I mean that "ls *" comes up blank, however if you know the filename, "ls foo.txt" will still find the file and you can access it without problems. I do not have a simple test case for which ones have trouble, here is what I know. All of them have several thousand entries. A list of random files that long is OK. If I create an organized list I am OK. If I play around too much with the files in a directory, it becomes OK (at least for a bit). But I have a list of several thousand filenames where if I create a new directory, put files with those names in it, and then try to read it from Linux, I come up blank. Other NT machines have no problems with these directories. My current production workaround is to zip the directory in NT, then copy the zip file and unzip in Linux. Ideas? Ben ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
On Wed, 28 Jun 2000, Ben Tilly wrote:> This is a problem I get with various versions of Samba, up to and including > 2.0.7. (The version shipped with Debian.)It's not in smbmount, it's in smbfs. What kernel version are you using? It should be fixed in 2.2.14 and up. It is NOT fixed in 2.3/2.4-test since that smbfs code has not received the fixes made to 2.2.> I mean that "ls *" comes up blank, however if you know the filename, "ls > foo.txt" will still find the file and you can access it without problems.You should get an error message from smbfs in your syslog.> I do not have a simple test case for which ones have trouble, here is what I > know. All of them have several thousand entries. A list of random filesIf you want to play with it here is a zip I made when I ran into this (the 569 files are all supposed to be empty). http://www.hojdpunkten.ac.se/054/samba/samba-dir.zip /Urban
Urban Widmark wrote:> >On Wed, 28 Jun 2000, Ben Tilly wrote: > > > This is a problem I get with various versions of Samba, up to and >including > > 2.0.7. (The version shipped with Debian.) > >It's not in smbmount, it's in smbfs. What kernel version are you using? It >should be fixed in 2.2.14 and up. It is NOT fixed in 2.3/2.4-test since >that smbfs code has not received the fixes made to 2.2. >2.2.12. That sounds like it> > > I mean that "ls *" comes up blank, however if you know the filename, "ls > > foo.txt" will still find the file and you can access it without >problems. > >You should get an error message from smbfs in your syslog.I did.> > I do not have a simple test case for which ones have trouble, here is >what I > > know. All of them have several thousand entries. A list of random >files > >If you want to play with it here is a zip I made when I ran into this (the >569 files are all supposed to be empty). > >http://www.hojdpunkten.ac.se/054/samba/samba-dir.zip >Thanks greatly. Time to file a report with Debian then. Thanks, Ben ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Peter Samuelson wrote:> > >[Ben Tilly <ben_tilly@hotmail.com>] > > Thanks greatly. Time to file a report with Debian then. > >Urban said the bug is fixed with kernel 2.2.14. If you're running >potato or woody (and you must be, for Samba 2.0.7), newer kernel images >have been available for a long time. About two days ago, Herbert Xu >released images for 2.2.17pre6. (2.2.16 had known security problems.)I am perfectly aware of that, and stated it in my bug report: http://cgi.debian.org/cgi-bin/bugreport.cgi?bug=66361 Cheers, Ben ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
On 27 June, Ben Tilly reported that smbmount (linux as client to NT boxes) had trouble listing large directories on Windows NT servers. Here's his message:> I have an NT machine (4.0, service-pack 3 using NTFS) exporting a > filesystem to Linux through smbmount. Specific directories are not > browsable. By that I mean that "ls *" comes up blank, however if > you know the filename, "ls foo.txt" will still find the file and you > can access it without problems.> I do not have a simple test case for which ones have trouble, here is > what I know. All of them have several thousand entries. A list of > random files that long is OK. If I create an organized list I am > OK. If I play around too much with the files in a directory, it > becomes OK (at least for a bit). But I have a list of several > thousand filenames where if I create a new directory, put files with > those names in it, and then try to read it from Linux, I come up > blank.I have had a very similar problem, in my case connecting to a network appliances toaster, rather than to an NT server. I think this may be the same problem Kenneth Oakeson reported on 29 June. I have a little more information. Here's what I find in /var/log/messages when this happens: Jun 15 10:46:41 mn65-zippy kernel: smb_proc_readdir_long: Looping in FIND_NEXT?? Jun 15 10:46:41 mn65-zippy kernel: smb_refill_dircache: readdir failed, result=-5 I am using using samba 2.0.7 on RedHat with Kernel 2.2.14-smp. A follow-up message from Urban Widmark indicated that this is a kernel (smbfs) problem and should be fixed in 2.2.14, however this is not my experience. Any suggestions? Thanks! Robert