On Wed, Oct 26, 2005 at 10:41:30AM +0100, Stephen Borrill wrote: > On Mon, 4 Jul 2005, Jeremy Allison wrote: > >On Wed, Jun 29, 2005 at 08:19:18AM -0400, Anthony Russello wrote: > >> > >>Hi Jeremy, > >> > >>The same issue occurs when running samba 3.0.14a fresh > >>from samba.org. > > > >As you're doing this on an embedded system as I recall you > >might want to cut down on the stat cache (which can grow > >unlimited on normal systems). To turn it off set : > > > >stat cache = False > > > >To limit the size set : > > > >max stat cache size = XX > > > >(where XX is in 1k units). > > We have a similar problem at one site using a Fox Pro database. The sizes > of the smbd processes continually increases until the server runs out of > swap (3.0.14). We've mitigated this a little by getting them to all log > off overnight and also restarting samba at 8am, but by mid-afternoon the > problem usually re-occurs. The processes get up to 200MB or so if left > unchecked. We've been running with "stat cache = no" for a while which has > made no difference. The DBF files being used by the database (it uses some > nasty file locking to spoof up a multi-user db) are up to around 90MB in > size. > > I cannot be certain, but I believe this problem has only recently started > happening (perhaps with an upgrade from 3.0.10 to 3.0.14?). > > Is there anything I can tweak?
As it's growing can you try doing smbcontrol <pid> pool-usage to get smbd to dump out it's talloc pools. Keep doing it, if one of them grows this may be a clue. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
