>> On Tue Apr 5 12:06:48 2005 -0400, Steve Langasek <[EMAIL PROTECTED]> wrote:
>> Are these files large?
S> Indeed not; these are typically sized cache files.
>> Can I simply delete all these .tdb files while samba is not running
>> and they will be recreated when samba restarts?
S> Yes, they should be recreated without problem if you delete them; I don't
S> currently see any reason to think that will help in your case, but it
S> shouldn't hurt to try.
I deleted /var/cache/samba/printing/*.tdb with samba stopped, and on
restart, just Nib.tdb and printers.tdb get created, and Windows
clients report 0 files in the queue for Nib, which is correct.
S> The other thing you might want to do, though, is
S> find /var/run/samba/ /var/cache/samba/ /var/lib/samba -name '*.tdb' \
S> -size +1024k
S> and see if there are any other extremely large tdb files on your system
--
S> the other one that was mentioned in one of the reports as getting
corrupted
S> was /var/run/samba/messages.tdb. Do *not* delete any files from
S> /var/lib/samba/, as they are not going to be regenerated for you.
All tdb files were reasonably sized. I have checked messages.tdb
before and always found it to be small.
>> One oddity that has been there for a while is that the printer
>> exported by samba shows up on the Windows XP clients as having 153
>> documents in the queue (I recall 149 as well), even though there are
>> none when I check on the samba machine with lpq, and indeed when I
>> look at the print queue from Windows there is nothing in it.
S> Hmm, maybe that points to a problem in /var/cache/samba/printing/ after
S> all...
That seems to have been cleared up by purging
/var/cache/samba/printing/. Here's an idea: what about a filename
case issue? Notice there was both Nib.tdb and nib.tdb and three
varieties of postscript.tdb. The only printer currently exported is
"Nib".
>> This seems to indicate just about 14% use, and it gives the same
>> numbers or very close each time I run ps.
>> Top and gtop, on the other hand, report numbers consistently in the
>> 80-90% range, fluctuating, and sometimes dipping lower.
>> What's the most helpful way to measure this?
S> Telling me whether the current behavior is causing you problems ;)
I don't think it's really chewing up 90% CPU, despite what top, gtop,
etc. report, because my system doesn't get as sluggish as it seems to
get when something else is using 90% CPU. I could conduct some more
objective tests, like timing some arithmetic when samba is and is not
misbehaving, but regardless of the CPU issue I guess there is solid
evidence that something malfunctions, because whenever gtop is
reporting high usage by smbd, smbd resists regular killing via init.d
script and needs "kill -9".
I've hammered a few minutes on samba since purging the printing tdbs
and haven't gotten it to blow up again. I'll write again if I notice
it has blown up again. Even if the purge really solved it, however,
it seems to me that this bug report (or a derivative) should remain
open: the clutter in /var/cache/samba/printing should either be purged
automatically or it should not cause a problem. I have never noticed
bloated .tdb files, so there may be two separate issues here with
similar misbehavior (high CPU) under similar conditions (sharing
printers).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
