Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!MCMASTER.BITNET!SIBLOCK From: SIBLOCK@MCMASTER.BITNET.UUCP Newsgroups: comp.os.vms Subject: Analyze/Disk/Repair -- Live? Message-ID: <8704140029.AA23692@ucbvax.Berkeley.EDU> Date: Mon, 13-Apr-87 15:55:00 EST Article-I.D.: ucbvax.8704140029.AA23692 Posted: Mon Apr 13 15:55:00 1987 Date-Received: Wed, 15-Apr-87 03:02:17 EST Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 22 Many people have mentioned that they do $Analyze/Disk/Repair s quite often. Can this be done on a 'live' system? I realize the volume is write-locked as repairs are being made, but for how long per repair operation? It would be beneficial to to repairs more often, but not if the system must be made unavailable to the userbase. Stephen J. Siblock, Computing Services Coordinator, Faculty of Science Computing and Information Services McMaster University, SS-149 Hamilton, Ontario, Canada L8S 4M1 (416) 525-9140, x4157. ::::::::::::::::::::::::::::::::::::::::::::::::::: :Bitnet: SIBLOCK@MCMASTER : : SIBLOCK@MCMVM1 : :Memory: 1001111001110110 : : 0011000001110100 : :::::::::::::::::::::::::::::::::::::::::::::::::::