Hi all, We're using samba, and we'd tried it with multiple Windows versions: 98, ME, 2000 and XP, in that order. However, when we migrated from 2000 to XP, a problem apeared that was not present in any other Windows version. Everthing works fine, excepting that when I am using the samba shares (browsing, opening files, etc...) from time to time I get a ~30 second lockup. During that time, the Samba shares are unresponsive from that computer (other computers work fine). I imagine this is probably an XP bug (since it doesn't happen in other Windows versions). But I would like to know if anyone has this problem and knows of a solution (from Samba or from XP). Is there a solution to this or do we have to live with it...hopefully not ;) /Dive
On Fri, 31 Jan 2003, Jens Pettersson wrote:> Hi all, > > We're using samba, and we'd tried > it with multiple Windows versions: 98, ME, 2000 and XP, in that order. > However, when we migrated from 2000 to XP, a problem apeared that was not > present in any other Windows version. Everthing works fine, excepting that > when I am using the samba shares (browsing, opening files, etc...) from time > to time I get a ~30 second lockup. During that time, the Samba shares are > unresponsive from that computer (other computers work fine). > > I imagine this is probably an XP bug (since it doesn't happen in other > Windows versions). But I would like to know if anyone has this problem and > knows of a solution (from Samba or from XP). > > Is there a solution to this or do we have to live with it...hopefully not ;)I have seen this with some XP machines also. Send me your smb.conf and I'll see what help can be brought to bare. - John T. -- John H Terpstra Email: jht@samba.org
Hi> from time to time I get a ~30 second lockupSame for me!
On Fri, 14 Feb 2003, lrnobs wrote:> John, > > I posted the following to the Samba list with no replies yet. Can you point > me in the right direction?Larry, I noticed your posting but am very pushed to get some presentations ready so have have had to watch my time carefully. Samba does not do resource/load distribution. If you look at what happens, every MS Windows client connection will spawn it's own instance of smbd. How much CPU time each process gets is determined by the OS. This means that if you want to alter the time sharing control over each smbd then you will need to tune your kernel. This may recompilation of your OS kernel with custom time slice and process prioritization settings. You might care to look at the Linux kernel file ~linux/kernel/sched.c as it documents itself quite well. - John T.> > Thanks, > > Larry Nobs > > > > ---------------------------------------------------------------------------- > -------------------------- > I want to put a Samba server online under RedHat 7.3 to replace an old > Novell server. > > Oplocks is turned off. > > I ran a test last night with Visual FoxPro code like this: > > ************************************************** > do while not flock() && request a file lock > && try again > endo > > get the date and time > insert a record into a shared table > unlock > > start over again > *************************************************** > > I ran this on seven windows pcs simultaneously. > > 1. The record insertions would allow one pc to insert multiple records, for > example 10 in a row before another computer had a chance to do an insertion. > The same test on the Novell server would allow one or two records before it > gave another computer a chance for an insertion. > > 2. After several thousand insertions I had only one pc consuming the time > viewable with the top command. I killed that process but the other pcs > still were not doing insertions. I killed the process on a second pc and > then the rest were free to insert records. > > How can I make the Samba server distribute time more evenly? I suspect that > allowing one pc so much record insertion time to the exclusion of others > created my lock up. > > Thanks, > > Larry Nobs > > > > >-- John H Terpstra Email: jht@samba.org