home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!gatech!paladin.american.edu!auvm!IUBVM.BITNET!PRUSSELL
- Message-ID: <VM-UTIL%92112012043045@OHSTVMA.ACS.OHIO-STATE.EDU>
- Newsgroups: bit.listserv.vm-util
- Date: Fri, 20 Nov 1992 11:40:30 EST
- Sender: VM Utilities Discussion List <VM-UTIL@OHSTVMA.BITNET>
- From: Paul Russell <PRUSSELL@IUBVM.BITNET>
- Subject: Re: dmsacp112serror.help|
- In-Reply-To: Message of Thu, 19 Nov 1992 17:47:25 GRW from <ISKAR2@TRMARUNV>
- Lines: 11
-
- If you don't have a current backup of this mdisk, or if you want to try
- to recover files that were created/changed after the backup, you might
- try accessing the disk in read-only mode, then copying files to another
- mdisk using the CMS COPYFILE command. Files that cannot be recovered
- directly from the corrupted mdisk will have to be restored from backups.
- I encountered a similar problem a few years ago. The user's 191 mdisk
- could not be accessed in write mode without encountering the DMS112
- error, however, it could be accessed in read-only mode. I think we were
- able copy all but one file from the corrupted mdisk to a new mdisk.
-
- Good luck! pdr
-