samba - Jun 2006 - file download crashes samba

All -

While trying to copy a directory containing a large number of files (
~600 1-5 mb files ) from my samba server to a client machine ( either
mac or windows ) my samba server crashes paralyzing my server machine
and forcing me to reboot it.  Once the behavior occurs I can no longer
ssh into the server or if I happen to be in it already I can't even
stop and restart samba.

Is this a known issue?  Could something be getting out of sync?

I don't believe this is client issue as I can duplicate with both mac
and windows clients easily.  Any ideas resolving this issue would be
great.

Thanks
..Chris

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Christopher Johnson wrote:
> All -
> 
> While trying to copy a directory containing a 
> large number of files (~600 1-5 mb files ) from
> my samba server to a client machine ( either
> mac or windows ) my samba server crashes 
> paralyzing my server machine and forcing me
> to reboot it.  Once the behavior occurs I can
> no longer ssh into the server or if I happen
> to be in it already I can't even stop and
> restart samba.
ERRNotEnoughInformation.

If you a reporting a Samba crash, you have to at
least include OS version, kernel, Samba version,
and hopefully a backtrace (or at least the information
from the log file).



cheers, jerry
====================================================================Samba       
------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
"What man is a man who does not make the world better?"      --Balian

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFEhsL0IR7qMdg1EfYRAnGiAJ9/Th7MoG04h9+V9jg+88MXsAydQgCgpo0l
AdKcoCuc9kWp/XXm+I+pY0I=cgH4
-----END PGP SIGNATURE-----

> While trying to copy a directory containing a large number of files (
> ~600 1-5 mb files ) from my samba server to a client machine ( either
> mac or windows ) my samba server crashes paralyzing my server machine
> and forcing me to reboot it.  Once the behavior occurs I can no longer
> ssh into the server or if I happen to be in it already I can't even
> stop and restart samba.
> I don't believe this is client issue as I can duplicate with both mac
> and windows clients easily.  Any ideas resolving this issue would be
> great.
Given that you can no longer SSH into the server it looks like the
machine is crashing, not Samba.  I've had this problem before with an
early 2.6 kernel (it could've even been 2.6.9) where a bug in my
network card driver (r8169) caused the whole machine to lock up.

This meant that I could trigger the issue with any large network
transfer, it wasn't restricted to Samba.  I'd look down this path
first, as it's pretty uncommon for Samba to be capable of locking up
the entire machine.

Cheers,
Adam.

All -

I've ran some more tests and I think I have come across some good
results.

I decided that if the problem is truly related to my network card
driver on my current system then I should have the same problem using
NFS.  So I configured NFS and mounted it on my mac and was able to
download any directory with any number of files within it without a
problem.

After looking around a bit more I also found posts of people with
problem similar to this using samba.  I'm confident that the problem is
within samba and not my network card driver.

It's great that using NFS works for the mac, but this does not really
address the problem of connecting my windows clients to the linux samba
server.

Any ideas would be great.

..Chris

Adam Nielsen wrote:
> > While trying to copy a directory containing a large number of files (
> > ~600 1-5 mb files ) from my samba server to a client machine ( either
> > mac or windows ) my samba server crashes paralyzing my server machine
> > and forcing me to reboot it.  Once the behavior occurs I can no longer
> > ssh into the server or if I happen to be in it already I can't
even
> > stop and restart samba.
> > I don't believe this is client issue as I can duplicate with both
mac
> > and windows clients easily.  Any ideas resolving this issue would be
> > great.
>
> Given that you can no longer SSH into the server it looks like the
> machine is crashing, not Samba.  I've had this problem before with an
> early 2.6 kernel (it could've even been 2.6.9) where a bug in my
> network card driver (r8169) caused the whole machine to lock up.
>
> This meant that I could trigger the issue with any large network
> transfer, it wasn't restricted to Samba.  I'd look down this path
> first, as it's pretty uncommon for Samba to be capable of locking up
> the entire machine.
>
> Cheers,
> Adam.
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/listinfo/samba