home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.vms:17574 vmsnet.misc:984
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!bu.edu!BUDSGA.BU.EDU
- From: TEWKSBURY@BUDSGA.BU.EDU (Chip Tewksbury)
- Newsgroups: comp.os.vms,vmsnet.misc
- Subject: V5.5-2 update warning
- Message-ID: <100832@bu.edu>
- Date: 6 Nov 92 14:31:10 GMT
- Sender: news@bu.edu
- Followup-To: comp.os.vms
- Organization: BOSTON UNIVERSITY, OFFICE OF INFORMATION TECHNOLOGY
- Lines: 34
- X-News-Reader: VMS NEWS 1.24
-
- The following is an excerpt from a DSIN article regarding a potential
- corruption problem resulting from the VMS V5.5-2 update procedure in
- conjunction with the MOVEFILE ACP subfunction -- i.e., disk defragmenters.
-
- Chip Tewksbury.
-
- ======================================================================
- After the VMS V5.5-2 upgrade procedure, SYS$LOADABLE_IMAGES:SYS.EXE
- will not have the "MoveFile disabled" attribute set.
-
- If a defragmentation product which uses MOVEFILE on the system disk
- decided to move SYS.EXE, there is a low risk probability that file
- corruption could occur on the system disk.
-
- NOTE: This can only happen if a "SET TIME" command was issued after
- SYS.EXE was moved, as the $SETIME system service writes
- directly to the original Logical Block Number (LBN) of SYS.EXE
- without looking it up each time.
-
- SOLUTION:
-
- To reset SYS.EXE to "MoveFile disabled", perform the following steps
- immediately after the VMS V5.5-2 upgrade procedure:
-
- 1. Log into the SYSTEM account.
- 2. Type the following at the DCL prompt:
-
- $ @SYS$SYSTEM:SETFILENOMOVE SYS$SYSDEVICE
-
- NOTE: This command file ensures that all critical system files
- have the "MoveFile disabled" attribute set.
-
- 3. Reboot your system. If you are running a VAXcluster system,
- reboot all cluster nodes.
-