Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-unix!ctnews!pyramid!decwrl!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: ACP error HEADERFULL message ?
Message-ID: <870424124713.007@CitHex.Caltech.Edu>
Date: Fri, 24-Apr-87 14:47:13 EDT
Article-I.D.: CitHex.870424124713.007
Posted: Fri Apr 24 14:47:13 1987
Date-Received: Sun, 26-Apr-87 22:39:43 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 34


  >  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 AND	ERROR RECOVERY PROCEDURES manual isn't exactly vague
on this; it merely assumes that you have some knowledge of the FILES-11
ON-DISK-STRUCTURE (LEVEL 2) that isn't normally available.  The info in
the SMAERP manual is:
	The file header map area on the volume is full....
This means that you've exceeded the Maximum files allowed value for the
volume (actually, although it is referred to this way, it is actually the
maximum file headers allowed, which is the upper limit of maximum files
allowed).  This can occur for several reasons:
	1)  You've got a highly fragmented disk, so that every file has
	    lots of file headers associated with it.  In this case the
	    recommended action (compress the disk by doing an image backup
	    and restore) will fix the problem.
	2)  You may have lots of little files.  In this case, the backup
	    and restore won't fix the problem.  Instead, what you have to
	    do is:
	    A) Do an image backup of the disk.
	    B) Initialize the disk with a larger value for max files.
	    C) Restore the backed up files using BACKUP/NOINIT
	3)  The volume may be corrupted.  Lots of luck, you'll need it.
Hope this helps a little.