Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!sri-unix!ctnews!pyramid!decwrl!decvax!ucbvax!YALE.ARPA!LEICHTER-JERRY From: LEICHTER-JERRY@YALE.ARPA Newsgroups: comp.os.vms Subject: Re: ACP error HEADERFULL message ? Message-ID: <8704260005.AA24250@ucbvax.Berkeley.EDU> Date: Sat, 25-Apr-87 19:06:18 EDT Article-I.D.: ucbvax.8704260005.AA24250 Posted: Sat Apr 25 19:06:18 1987 Date-Received: Sun, 26-Apr-87 22:38:02 EDT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Distribution: world Organization: The ARPA Internet Lines: 48 Since the past two-three days, we have been having problems on one of our user-disks Users get errors doing any file editing related tasks The message is of the form ACP-I-CRE file create failed SYSTEM-HEADERFULL file header full The manual on System messages and also the RMS file application messages are vague on this... ??? We are running VMS 4.4 on 11/780 Also SHO DEV DR gives sufficient space free on all disks including the SYSTEM disk . The System Messages book (V4.2, the most recent I have around) has the following to say: Explanation: The file header map area ... is full and cannot be extended. This error occurs only when the file header extension is inhibited, for example, when the index file is extended. Rather terse - you have to know how ODS 2, the VMS file system, works to make any sense of it at all. Basically, file headers are stored in the index file, and the index file bitmap keeps track of which entries in the index file are in use. The index file includes an entry for itself - for the most part, it looks like a normal file - and the index file bitmap, too. Either of these can, under normal conditions, be extended. This error apparently occurs when both have to be extended. I don't claim to understand the details, but from the text of the error message - and from personal experience - I'd say this is a very rare occurance. The System Messages book goes on to say: User Action: Compress the volume by copying it with BACKUP. That should fix the problem. As a temporary work-around, deleting a bunch of files will free up some file headers, which could then most likely be re-used. (Since I've never seen this error, I can't say for certain - it could be that a disk in this state just remains unable to accept new files even if headers are freed up. But it's worth a try if re-building the disk RIGHT NOW would be a big headache.) -- Jerry -------