SYSMSH@ULKYVX.BITNET.UUCP (02/22/87)
Oh no....Mr. Bill!!
I've been running 4.5 in a cluster for a couple of months and have
not seen the disk corruption problem. I saw the message about the
ACP parameters being non-standard causing this. I have set many of
the ACP parameters to non-standard values and each cluster node has
different sizes depending on its memory. I have NOT changed the
following ACP parameters that deal with cache-ing:
ACP_FIDCACHE
ACP_EXTCACHE
ACP_EXTLIMIT
I'd like some other cluster sites running 4.5 that do fiddle with
ACP parameters to check theirs. Maybe we can narrow it down to a
specific one not to mess with? Just speculating - perhaps it is
the obvious ACP_EXT* parameters if the extents are getting wasted.
Mark Hittinger/systems programmer iv/ocis south center
University of Louisville/Louisville, Ky 40292
sysmsh%ulkyvx.bitnet@wiscvm.wisc.edu