Yes, the problem is circumvented by turning off schedule log pruning (simply
comment out
SCHEDLOGRETENTION line in dsm.opt).

There is a bug in the schedule log pruning code which ignores end of file on the
schedule log and continues to write to the prune log until the disk fills up
(and has the added affect of chewing up CPU utilization).

I apologise for all of the problems which got into the field in this PTF
for the Win32 client.

There was unusual amount of new function in this PTF for the Win32 client
(UNC support, Registry support for Win95, etc.) and some things just got
overlooked.

All I can say is that most of these problems have either been fixed or are
being worked on,
and that we will be refreshing the ftp server with these fixes as soon as
possible.

Also, for whatever it's worth, the developers who follow this list take
personally
responsibility for following up on any reported problems and are committed to
doing
whatever is necessary to improve the quality of the product in the future.


Pete Tanenhaus, ADSM NT Client Development
---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 08/24/98
4/98
11:01 AM ---------------------------


ADSM-L AT VM.MARIST DOT EDU on 08/24/98 07:47:51 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Win32 client bug!!


Can someone tell me if this problem be circumvented by specifying that
pruned log entries are to be Discarded?  I.e.,

SCHEDLOGRETENTION 30 D

The APAR does not indicate anything about this, but I figured if the
problem has to do with the pruning log getting too large that specifying a
"D" to discard the pruned entries might just be a workaround.

We unfortunately need to deploy a V3 NT client (for NT servers that backup
Mac filespaces).  We view this bug as a serious one, and not pruning the
log file will lead to other problems on the server.

Thanks.
..Paul

PS: I don't have an NT system handy to try this on, or I'd have tried it
myself!
--
At 10:21 AM 8/19/98 -0400, you wrote:
At 10:21 AM 8/19/98 -0400, you wrote:
>It's a known problem. Please turn off schedule log pruning for now until
we can
>get it fixed.
>
>Pete Tanenhaus, ADSM NT Client Development
>---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 08/19/98
>10:08 AM ---------------------------
>
>
>ADSM-L AT VM.MARIST DOT EDU on 08/19/98 03:30:03 AM
>Please respond to ADSM-L AT VM.MARIST DOT EDU
>To: ADSM-L AT VM.MARIST DOT EDU
>cc:
>Subject: Win32 client bug!!
>
>
>Dear ADSM-ers!
>This is a warning for all Windows 32 client 3.1.05 users!
>If you use the dsmsched.log pruning option this can cause your filespace to
>fill up completely.
>Yesterday I installed the 3.1.05 client on 3 Windows NT machines. After the
>backup the ADSM scheduler starts pruning the dsmsched.log which never
>finishes. It created a dsmprun.log which took up all the available free disk
>space!
>This sounds like a serious bug in the ADSM client code.
>Kindest regards,
>Eric van Loon
>
>
>
>