Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ucbvax!ULKYVX.BITNET!SYSMSH
From: SYSMSH@ULKYVX.BITNET.UUCP
Newsgroups: mod.computers.vax
Subject: re: vms 4.5/cluster disk corruption (arg!!)
Message-ID: <8702220224.AA15093@ucbvax.Berkeley.EDU>
Date: Sat, 21-Feb-87 16:31:00 EST
Article-I.D.: ucbvax.8702220224.AA15093
Posted: Sat Feb 21 16:31:00 1987
Date-Received: Sun, 22-Feb-87 05:43:29 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of Louisville
Lines: 21
Approved: info-vax@sri-kl.arpa

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