[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

1921.0. "ALL-IN-1 X FILE HEADER!!!!" by VAXRIO::WILLECKE (Operations Analyst) Tue Dec 08 1992 20:21

    HELP! I have ALL-IN-1 V2.4 running and it has 3 mail areas distributed
    between 3 disks. One area is in ALL-IN-1 disk with SDAF_E size 98k
    blocks the second area (OA$SHARA) is in another disk w/ SDAF_A size
    175k,  the third area (in a diferent disk) is still small. 
    
    ALL-IN-1 just KILLED my two disks (RA90). They have more than 1000000 
    free blocks but there is no more space in the file header. Yesterday, I 
    initialized a disk, duplicated the max_files and today I'm having the 
    same problem in OA$SHARA area.... File header full!
    
    How can I fix this problem? I don't have enough disks to create
    ALL-IN-1 areas and lost the disk! 
    
    Thanks,
    Valeria.
T.RTitleUserPersonal
Name		DateLines
1921.1We make lots of files...IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeWed Dec 09 1992 17:3612
    Because we (ALL-IN-1) tend to create lots of tiny (3 block or less)
    files containing quick mail messages etc., then the normal defaults
    that VMS engineering choose for the number of files on a disc are often
    too small.
    
    The good news is that you can fix the number of file headers, the bad
    news is that you have to reinitialise the disc to do it. So out to tape
    and back time...
    
    Bad luck it happening to two discs at once!
    
    Graham
1921.2HEADERFULL MessageSEDTU5::Glyn-DaviesWed Dec 09 1992 17:4511
I had a similar problem when trying to install ALL-IN-1 V3 at a customer 
site last night. 

The installation had been going for about 4 hours, and had been at the

'Moving files to target directories ... ' for about 1 hour when I got a 
VMS HEADERFULL error message and the installation aborted.

Does anybody know what I have to do before trying to re-install.

Glyn
1921.3Basically do it again...IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeWed Dec 09 1992 18:0011
    Is this an upgrade?
    
    Yes - Follow instructions in Installation Guide about renaming
    directories back to their old names.
    
    No - Do it again.
    
    Some people like to tidy up newly created accounts, directories etc.,
    but it isn't strictly necessary.
    
    Graham
1921.4From STARSOASS::PCMIKE::lamberson_mTue Dec 15 1992 14:3362
File Header Full' Message When Attempting to Send Mail

PRODUCT: ALL-IN-1 V2.3, V2.4

When you attempt to send a mail message in ALL-IN-1 you will receive the
following message:

 "Error copying to file OA$SHAREx:Z...WPL"

A GOLD MESSAGE ({GOLD W}) displays the message:

  "File Header full"

Most often this error is caused by the failure to extend the index file for the
volume, INDEXF.SYS. VMS restricts INDEXF.SYS to 1 file header. It cannot have
an extension header. When this occurs, no new files can be created on the disk
volume (containing OA$SHAREx directory in this case).

This can also occur if the maximum number of files allowed on the device have
been reached. The setting of "MAXIMUM FILES" on the device is set at a default
level determined by the formula:

    TOTAL BLOCKS on device divided by (CLUSTER SIZE plus 1) times 2

This symptom and error message are actually an indication of a VMS problem on
the system.  For more detailed information regarding this error message, refer
to the VMS STARS database article titled:

 "SYSTEM-F-HEADERFULL Error Creating or Extending a File"

You can verify the maximum files allowed for a device from DCL using the
command:

 $SHOW DEV/FULL device:

As a temporary alternative, you can purge and/or delete files from this volume.

The maximum number of files allowed for the device must be increased if it has
been reached.  This can only be accomplished by re-initializing the disk with a
higher value for the MAXIMUM_FILES qualifier (also refer to the HEADERS
qualifier for information on file headers allocated).

If the index file, INDEXF.SYS, can no longer be extended, this may be
temporarily alleviated by deleting some files from the volume.  This will free
the headers associated with the deleted files for reuse, eliminating the need
to extend the index file.

NOTE:  This is only a temporary solution. The problem will most likely reoccur
shortly. The volume should be compressed as soon as possible by restoring an
IMAGE BACKUP to the disk on which the error occurred. Be aware of a restriction
when performing image backup when the /HEADERS is used to initialize a device.
Refer to VMS article: "BACKUP/IMAGE/NOINITIALIZE Writes Over Pre-Extended
INDEXF.SYS"

E.g.:

 1. Perform an image backup on this device

 2. $INITIALIZE dev:/MAXIMUM_FILES=x "VOLUME LABEL"

 3.  Restore the backup of the device from Step 1 with the /NOINIT qualifier