home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!europa.asd.contel.com!emory!swrinde!sdd.hp.com!elroy.jpl.nasa.gov!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: Re: Fixing SYSTEM-W-HEADERFULL error
- Date: 17 Nov 1992 06:22:05 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 31
- Distribution: world
- Message-ID: <1ea32dINNs2m@gap.caltech.edu>
- References: <BxoMzw.Jx9@irvine.com> <1992Nov16.122136.26119@fripp.ri.cadre.com>,<1992Nov16.153235.958@calmasd.prime.com>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- In article <1992Nov16.153235.958@calmasd.prime.com>, kjb@calmasd.prime.com (Ken Brucker) writes:
- >Be careful on this last step. There's a bug that I know existed back in VMS
- >5.4 and may still be present in Backup. Essentially, it ignores the /noinit
- >when doing an image restore and re-creates the indexf.sys to be just large
- >enough to hold the files that are in the save set.
-
- As has been pointed out many times before, BACKUP has no way of knowing for
- certain with what number of headers the volume was initialized. That number
- simply isn't stored anywhere on the disk.
-
- >I mentioned this to one of the Backup developers at a DECUS a couple of years
- >ago and I think the patched version of Backup that is available via DSNlink
- >contains the fix, but I don't think VMS 5.5-1 does. Although I haven't had
- >reason to test this lately so I don't know if this is still a real problem with
- >the current VMS release.
-
- I understand that it was finally fixed in 5.5-2.
-
- >To get around the bug, do steps 1 to 3 and then do a selective restore to the
- >entire disk.
-
- Of course, this won't work if the disk in question happens to be your system
- disk.
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-