Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbatt!ucbvax!CERNVM.BITNET!JCV
From: JCV@CERNVM.BITNET.UUCP
Newsgroups: comp.os.vms
Subject: Re: ACP HEADERFULL error
Message-ID: <8704300338.AA29613@ucbvax.Berkeley.EDU>
Date: Wed, 29-Apr-87 23:39:07 EDT
Article-I.D.: ucbvax.8704300338.AA29613
Posted: Wed Apr 29 23:39:07 1987
Date-Received: Fri, 1-May-87 03:22:50 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 33

I have the impression that all the explanations to the ACP HEADERFULL message
have been wrong somewhere or other. So, to summarize:

The volume INDEXF.SYS contains three parts:

 -  home blocks and other misc. information
 -  indexfile bit map
 -  file headers

The indexfile bitmap indicates which file header blocks are in use. It is
at the beginning of the index file. Its size is specified (or defaulted)
when the volume is initialized and may  o n l y  be changed by re-initializing
the volume. It effectively specifies how large the index file may become.
See HELP INIT DEVICE /MAX_FILES for further information.
(BTW, actual initial allocation for the index file is specified via /HEADER.)

So, what the message wants to say is: No more file header blocks are free
in the index file.
The reasons are:
 -  Too many files
 -  A large number of files require extension header(s) because of:
     -  disk freagmentation or/and
     -  large ACLs

In other cases (device full and index file too fragmented) you will see other
error messages.

The remedy proposed is correct, of course: Restore the disk from BACKUP.
If the reason for the error is that you have too many files, be sure to
initialize the disk with a larger /MAX_FILES and do the restore BACKUP/NOINIT!


  --- Jan Vorbrueggen