It fills until the db reaches a 'sync' point. Something like a number of 
clients backing up concurrently but not as yet completed can fill up the log 
file.

>>> DWood2 AT CHW DOT EDU 12/06/00 10:49AM >>>
My recovery log filled up and crashed the server this morning. I have the
recovery log in "Normal" mode - NOT "Roll Forward" mode. I was under the
impression that the recovery log would not fill up and crash the system
while in normal mode. The log is 1.5 GB and the DB is 13.5 GB. We do a full
DB backup once a day, sometimes twice. When I restarted the server the log
showed up as 0.1% utilized. Does anyone have any idea as to what might cause
the log to fill up? I am running TSM 3.7.3 on Solaris. Thanks,
-Dwight
=======================================================================