[Samba] Samba server slow down after serving more than casual data
samba at tlinx.org
Mon Oct 31 13:37:19 MDT 2011
> It seems like the use of samba triggers something on the server that
> brings it to a crawl and affects everything.
> I can copy data back and forth using NFS for hours and never see the
> issue unless I use samba.
So samba is running the background just fine and hours
later the 'system becomes slow'...
> Any suggestions or help in debugging this issue?
First, find out what is causing the slowdown.
Is samba eating all of your CPU, is it flooding your network?
Or is it saturating the disk so other processes can't get their I/O]
done in any reasonable time.
If you have perl5.10 or greater on your system,
I'll pass along a little status prog ... it's *dated*, but still
mostly works. (a 'new version' has been underconstruction well..
at least since last March, but stalled in June due to other problems).
Will show at a glance your top partitions (though recently under newer
kerns, is showing some '<unknown>' -- haven't tracked it down -- but then
haven't touched it for almost 5 months...)...
consuming doing I/O, the top processes, and the usage on your network.
It will automatically try to run as root (via sudoing to itslf), upon
running it, so if you don't have sudo setup to allow you to sudo and run
arbitrary commands then you'll have to run the thing as root.
But, obviously, the code is included, you can inspect to see that it
meets your safety -- but it needs root to be able to read all the
processes I/O stats and find out where the I/O is going... Runs mostly
by lots of inspections of 'proc'.
There's no built help but while it's running it can take 5 keys:
-+dpq, + & - modify the pause time between updates (dft=7s), 'd' and 'p'
toggle display of devices/processes, q = quit (or control-c!).
I took all the 'use' calls to my local libs and packed em into 1 file,
so it seems to run standalone.
If you find it worthless, buggy or annoying send it to /dev/null...
just that in a situation like this between 'top' and this, I can usually
pin down where my slowness is coming from. But I haven't looked at this
codes since lst march and not at a derivative of the code since last June,
so any questions you'd have about operation...or bugs...I'd be going in as
cold as you would in trying to figure them out.
A "WAG"** on my part: ....after a while one or more computers begin
indexing the drive and hammering it..... using BW and disk.
**-Wild ass Guess
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
More information about the samba