Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!LLL-ICDC.ARPA!oberman
From: oberman@LLL-ICDC.ARPA.UUCP
Newsgroups: mod.computers.vax
Subject: RE VMS: SET VOLUME/REBUILD
Message-ID: <8612071717.AA14745@ucbvax.Berkeley.EDU>
Date: Fri, 5-Dec-86 11:01:00 EST
Article-I.D.: ucbvax.8612071717.AA14745
Posted: Fri Dec  5 11:01:00 1986
Date-Received: Sun, 7-Dec-86 14:34:21 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: "Oberman, Kevin" 
Organization: The ARPA Internet
Lines: 25
Approved: info-vax@sri-kl.arpa

>$ MOUNT/REBUILD  can take about 15 minutes for all our disks after a crash.
>
>In trying to speed up my SYSTARTUP.COM I'm considering $ MOUNT/NOREBUILD for
>all our disk-devices (in a 4 VAX cluster). and doing $ SET VOLUME/REBUILD in a
>batch-job at night. We don't care about inaccurate disk-quota's or unavailable
>free space for some time. 
>
>Are there any undocumented penalties to do this ?
>Is there anyone who has experience with MOUNT/NOREBUILD ?

We have been doing something similar for several months with no bad effects.
We start a batch job during boot to rebuild all of our disks. This minimizes
accesses to the disk before they are rebuilt.

At the SF DECUS a developer mentioned that there appears to be a problem with
SET VOL/REB in certain odd circumstances. The developers don't seem to fully
understand what's happening, but it does, on rare occassion, result in large
pieces of the disk "disappearing". We have not seen that, but large numbers of
accesses to an unrebuilt disk might increase its likelyhood.

					R. Kevin Oberman
					LLNL
					arpa: oberman@lll-icdc.arpa
					(415) 422-6955
------