SIBLOCK@MCMASTER.BITNET.UUCP (04/13/87)
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 <VAX 8600, VMS V4>:
: SIBLOCK@MCMVM1 <IBM 4381, CMS R4>:
:Memory: 1001111001110110 :
: 0011000001110100 :
:::::::::::::::::::::::::::::::::::::::::::::::::::weaver@prls.UUCP (Mike Weaver) (04/16/87)
I have done analyze/disk/repair on live filesystems several times and have not had any problems. I generally use /confirm, just because to be careful. This takes about 15 minutes for the system disk, an RP07, and ten minutes for each user disk (RA81). The time presumably varies with the number of files. One nice feature is that batch jobs in progress are only held up and not aborted when the disk is write-locked. Michael Weaver Signetics Microprocessor CAD USENET: pyramid!prls!weaver