Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!ctnews!pyramid!decwrl!decvax!ucbvax!LBL.ARPA!nagy%43198.hepnet
From: nagy%43198.hepnet@LBL.ARPA
Newsgroups: comp.os.vms
Subject: RE: ACP HEADERFULL error
Message-ID: <8704260019.AA24429@ucbvax.Berkeley.EDU>
Date: Fri, 24-Apr-87 13:55:04 EDT
Article-I.D.: ucbvax.8704260019.AA24429
Posted: Fri Apr 24 13:55:04 1987
Date-Received: Sun, 26-Apr-87 22:38:14 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 27

According to my System Messages manual, plus an understanding of the ODS-2
file structure, I interpret this error as follows:

	- Index file is currently full

	- User is creating a new filee (result of edit, etc.) and so the
	  index file must be extended.

	- Now, one of two things is happening:

		(a) The index file extension chunk can't be allocated because
		    there is no free chunk big enough on the disk.

		OR

		(b) The index file has its own file header, this file contains
		    the map pointers for the index file (obviously).  As I
		    remember, a normal file header has room to map 7 separate
		    file extents.  I also remember that the index file CANNOT
		    be mapped with an extension header; the entire index file
		    must be described by a single file header.

The System Messages manual states that the solution is to compress the disk
with a BACKUP save/restore cycle.  When you do the restore, BACKUP will
initialize the disk and create a new Index file which is big enough to
contain all the existing file headers originally on the disk as a single
chunk of disk space.