Document revision date: 19 July 1999

The user data packet contains an accounting message sent by the $SNDJBC system service.

Figure C-8 shows the format of the user data packet. Table C-12 describes the fields contained in the packet. See Section C.1.2.1 for information on the packet header.

Figure C-8 Format of a User Data Packet

Table C-12 Data Field in a User Data Packet

Symbolic Offset	Description
ACR$T_USER_DATA	Up to 255 bytes of data (counted string).

ANALYZE/DISK_STRUCTURE performs the verification of a volume or volume set in eight distinct stages. During these stages, ANALYZE/DISK_STRUCTURE compiles information that is used in reporting errors and performing repairs.

Before ANALYZE/DISK_STRUCTURE can proceed with each stage, it must perform the following four initialization functions:

• Read the device name, validate access to the device, and save the device name
• Read the user-specified file names for the /LIST and /USAGE qualifiers, if specified, and open the files
• Assign all appropriate channels to the device being checked
• Write-lock the volume set to prevent simultaneous updates

The following sections describe the eight stages that ANALYZE/DISK_STRUCTURE goes through while verifying a disk. These descriptions assume that you specified the /REPAIR qualifier in the command. An annotated ANALYZE/DISK_STRUCTURE listing is included at the end of this appendix.

D.1 Stage 1

In Stage 1, ANALYZE/DISK_STRUCTURE gathers various volume information (such as cluster size, volume labels, and the number of volumes in the set) from several reserved files, verifies the information for accuracy, reports all discrepancies, and corrects problems discovered during this stage.

ANALYZE/DISK_STRUCTURE identifies the volume and all the characteristics of that volume by using the parameters of the home block in INDEXF.SYS. When ANALYZE/DISK_STRUCTURE confirms this information, it builds a current version of VOLSET.SYS in memory and reads and verifies the status control block (SCB) of BITMAP.SYS.

ANALYZE/DISK_STRUCTURE then compares the volume-set attributes for the version of VOLSET.SYS in memory to the attributes listed in the version of VOLSET.SYS resident on the volume, reports discrepancies, and corrects errors.

D.2 Stage 2

In Stage 2, ANALYZE/DISK_STRUCTURE copies the current version of QUOTA.SYS into working memory, and establishes the structure on which another QUOTA.SYS file is built during subsequent stages. In Stage 7, these copies are compared with each other and inconsistencies are reported.

D.3 Stage 3

Stage 3 checks consist of ANALYZE/DISK_STRUCTURE operations that use the reserved file INDEXF.SYS. During Stage 3, ANALYZE/DISK_STRUCTURE opens INDEXF.SYS, reads each file header, and completes the following steps:

• Validates each file's FID, and confirms that all files can be retrieved through the FID
• Validates the header and the revision date of each file
• Validates any extension headers of each file
• Confirms that each segment number reflects the proper sequence of extension headers

ANALYZE/DISK_STRUCTURE also performs the following operations during Stage 3:

• Builds a map of header linkage so that ambiguities can be detected
• Determines the high block (HIBLK) and end-of-file block (EFBLK) record attributes and compares these values with the recorded values in INDEXF.SYS
• Checks the high-water mark (HIWATERMARK)

While performing these checks, ANALYZE/DISK_STRUCTURE builds several maps that it uses in subsequent stages. Table D-1 briefly describes each map built in Stage 3.

Table D-1 Stage 3 Maps

Bitmap	Function
Valid file numbers	The current state of the bitmap for INDEXF.SYS
Lost file numbers	All the valid file numbers not yet found in a directory
Directory files	List of all directory files
Extension linkages	List of all valid extension headers
Multiply allocated clusters	List of all clusters that are referenced by more than one header
Allocated clusters	All allocated clusters on the volume (or volume set)
System map	The new storage bitmap
Valid file backlink	A map of all valid file backlinks
Invalid backlink	A map of all invalid backlinks

D.4 Stage 4

In Stage 4, ANALYZE/DISK_STRUCTURE builds a current version of BITMAP.SYS using the maps built during Stage 3. In addition, ANALYZE/DISK_STRUCTURE reports any discrepancies between the headers' maps and the storage bitmap. In Stage 4, ANALYZE/DISK_STRUCTURE performs the following operations:

• Copies BITMAP.SYS into working memory
• Compares the corrected version of BITMAP.SYS with a map built from INDEXF.SYS

• Writes a corrected version of BITMAP.SYS to disk
• Reports multiply allocated clusters

In this stage, ANALYZE/DISK_STRUCTURE completes a pass of all entries in the invalid backlink map. ANALYZE/DISK_STRUCTURE searches the directory hierarchy of the volume to confirm that all files included in INDEXF.SYS are retrievable through the directory structure. In addition, ANALYZE/DISK_STRUCTURE identifies lost directories and attempts to reestablish valid backlinks to those directories.

In Stage 5, ANALYZE/DISK_STRUCTURE performs the following operations:

• Confirms the locations of all directories listed in the directory map (compiled in Stage 3) and the subsequent files in those directories
• Enters all directories indicated as lost and locates a valid parent (if any)

Stage 6 is essentially a cleanup operation for lost file headers. Following Stage 5, ANALYZE/DISK_STRUCTURE is left with a list of files that are truly lost---files that have backlinks to nonexistent directories. These files were not traceable through the directory structure. ANALYZE/DISK_STRUCTURE is also left with a list of files with bad backlinks; these files are traceable through the directory structure, but the backlinks of the files do not point back to the directory that contains them.

During Stage 6, ANALYZE/DISK_STRUCTURE performs the following operations:

• Checks the backlink map to locate all files with invalid backlinks, then repairs backlinks
• Checks the lost file bitmap for lost files and places lost files in [SYSLOST] if you specified /REPAIR
• If you specified the /USAGE qualifier, creates an entry for each lost file

In this stage, ANALYZE/DISK_STRUCTURE compares the values stored in the quota file built during Stage 2 with those stored in the reserved file QUOTA.SYS. During Stage 7, ANALYZE/DISK_STRUCTURE opens QUOTA.SYS and performs the following operations:

• Compares the block usage for each UIC listed in QUOTA.SYS to parallel statistics listed in the copy of QUOTA.SYS built in Stage 2
• Modifies QUOTA.SYS such that values in QUOTA.SYS match values in the copy built in Stage 2
• Closes QUOTA.SYS

Throughout the first seven stages, ANALYZE/DISK_STRUCTURE places operations that cannot be performed during a particular stage on a deferred list. The list includes FIDs sorted by operation. In Stage 8, ANALYZE/DISK_STRUCTURE performs all operations stored on the deferred list. In Stage 8, ANALYZE/DISK_STRUCTURE performs the following operations:

• Removes an FID from the deferred list, renames the file, and adds the file to SYSLOST.DIR or to a user-specified directory
• Updates QUOTA.SYS to reflect all additional blocks used by the UIC that received the lost file
• Updates VOLSET.SYS to correct inconsistencies discovered during previous ANALYZE/DISK_STRUCTURE stages

The following example is an annotated sample of an ANALYZE/DISK_STRUCTURE session. The command used to generate this example did not include the /REPAIR qualifier.

%VERIFY-I-BADHEADER, file (487,173,1) MAIL$0004008EEAEE0572.MAI;1 (1) invalid file header %VERIFY-I-BADHEADER, file (531,112,1) MAIL$0004008EEFBB198B.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (589,104,1) MAIL$0004008EEAF199B9.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (604,157,1) MAIL$0004008EF12C3B28.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (674,247,1) MAIL$0004008EF6053C9B.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (688,41,1) MAIL$0004008EF608AFF4.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (689,135,1) MAIL$0004008EEE445A31.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (750,71,1) MAIL$0004008EEED19ADF.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (753,217,1) MAIL$0004008EE7C4A017.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (780,236,1) MAIL$0004008EF777ACA8.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (852,57,1) MAIL$0004008EF06C15F6.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (856,44,1) MAIL$0004008EE7D2520D.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1059,42,1) MAIL$0004008EEB045608.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1134,76,1) MAIL$0004008EE9EC806D.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1316,147,1) MAIL$0004008EEEDA734F.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1350,74,1) MAIL$0004008EE89BA8B0.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1351,64,1) MAIL$0004008EEB09B036.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1490,104,1) MAIL$0004008EE8B448B0.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1493,106,1) LASTNOTIC.NIL;1 invalid file header %VERIFY-I-BADHEADER, file (1548,204,1) MAIL$0004008EF7B4D1B8.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1613,61,1) MAIL$0004008EECEE4BA5.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1812,81,1) MAIL$0004008EE7DF05EC.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1848,26,1) MAIL$0004008EF78659B9.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1983,34119,1) MAIL$0004008EE7E49C13.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (1987,33907,1) REMIND.CAL;9 invalid file header %VERIFY-I-BADHEADER, file (2196,123,1) MAIL$0004008EE6FA2DC9.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (2372,125,1) MAIL$0004008EF06339F9.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (2569,67,1) MAIL$0004008EF2BF0C15.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (2605,72,1) MAIL$0004008EE856FC73.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (2616,70,1) MAIL$0004008EF063C04F.MAI;1 invalid file header %VERIFY-I-BADHEADER, file (2774,29818,1) LASTNOTIC.NIL;1 invalid file header %VERIFY-I-ALLOCCLR, blocks incorrectly marked allocated (2) LBN 442398 to 445538, RVN 1 %VERIFY-I-BADHEADER, file (487,0,1) MAIL$0004008EEAEE0572.MAI;1 (3) invalid file header %VERIFY-I-LOSTEXTHDR, file (487,0,1) lost extension file header %VERIFY-I-BADHEADER, file (531,0,1) MAIL$0004008EEFBB198B.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (531,0,1) lost extension file header %VERIFY-I-BADHEADER, file (589,0,1) MAIL$0004008EEAF199B9.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (589,0,1) lost extension file header %VERIFY-I-BADHEADER, file (604,0,1) MAIL$0004008EF12C3B28.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (604,0,1) lost extension file header %VERIFY-I-BADHEADER, file (674,0,1) MAIL$0004008EF6053C9B.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (674,0,1) lost extension file header %VERIFY-I-BADHEADER, file (688,0,1) MAIL$0004008EF608AFF4.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (688,0,1) lost extension file header %VERIFY-I-BADHEADER, file (689,0,1) MAIL$0004008EEE445A31.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (689,0,1) lost extension file header %VERIFY-I-BADHEADER, file (750,0,1) MAIL$0004008EEED19ADF.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (750,0,1) lost extension file header %VERIFY-I-BADHEADER, file (753,0,1) MAIL$0004008EE7C4A017.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (753,0,1) lost extension file header %VERIFY-I-BADHEADER, file (780,0,1) MAIL$0004008EF777ACA8.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (780,0,1) lost extension file header %VERIFY-I-BADHEADER, file (852,0,1) MAIL$0004008EF06C15F6.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (852,0,1) lost extension file header %VERIFY-I-BADHEADER, file (856,0,1) MAIL$0004008EE7D2520D.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (856,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1059,0,1) MAIL$0004008EEB045608.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1059,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1134,0,1) MAIL$0004008EE9EC806D.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1134,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1316,0,1) MAIL$0004008EEEDA734F.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1316,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1350,0,1) MAIL$0004008EE89BA8B0.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1350,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1351,0,1) MAIL$0004008EEB09B036.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1351,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1490,0,1) MAIL$0004008EE8B448B0.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1490,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1493,0,1) LASTNOTIC.NIL;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1493,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1548,0,1) MAIL$0004008EF7B4D1B8.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1548,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1613,0,1) MAIL$0004008EECEE4BA5.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1613,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1812,0,1) MAIL$0004008EE7DF05EC.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1812,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1848,0,1) MAIL$0004008EF78659B9.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1848,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1983,0,1) MAIL$0004008EE7E49C13.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (1983,0,1) lost extension file header %VERIFY-I-BADHEADER, file (1987,0,1) REMIND.CAL;9 invalid file header %VERIFY-I-LOSTEXTHDR, file (1987,0,1) lost extension file header %VERIFY-I-BADHEADER, file (2196,0,1) MAIL$0004008EE6FA2DC9.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (2196,0,1) lost extension file header %VERIFY-I-BADHEADER, file (2372,0,1) MAIL$0004008EF06339F9.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (2372,0,1) lost extension file header %VERIFY-I-BADHEADER, file (2569,0,1) MAIL$0004008EF2BF0C15.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (2569,0,1) lost extension file header %VERIFY-I-BADHEADER, file (2605,0,1) MAIL$0004008EE856FC73.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (2605,0,1) lost extension file header %VERIFY-I-BADHEADER, file (2616,0,1) MAIL$0004008EF063C04F.MAI;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (2616,0,1) lost extension file header %VERIFY-I-BADHEADER, file (2774,0,1) LASTNOTIC.NIL;1 invalid file header %VERIFY-I-LOSTEXTHDR, file (2774,0,1) lost extension file header %VERIFY-I-BADDIRENT, invalid file identification in directory entry [ALLWAY]NOTES.LOG;25 (4) %VERIFY-I-BADDIRENT, invalid file identification in directory entry [BLAIN.BOOTS]LOADER.OBJ;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [BLAIN.BOOTS]SYSGEN.OBJ;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [BLAIN]MAIL_20600841.TMP;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [BLAIN]NETSERVER.LOG;181 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [BLAIN]NETSERVER.LOG;180 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [BLAIN]NETSERVER.LOG;179 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [BLAIN]NETSERVER.LOG;178 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [BLAIN]NETSERVER.LOG;170 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [BOEMUS.MAIL]MAIL$0004008EF94A72A0.MAI;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [BOEMUS]NETSERVER.LOG;10 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [BOEMUS]UPDATE.LOG;1 %VERIFY-I-BACKLINK, incorrect directory back link [CALGON.GER]OBJ.DIR;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [CALGON]T.TMP;1 %VERIFY-I-BACKLINK, incorrect directory back link [CLABIN.BACKUP.TMPSRC]BACKDEF.SDL;1 %VERIFY-I-BACKLINK, incorrect directory back link [CLABIN.BACKUP.TMPSRC]COMMON.REQ;1 %VERIFY-I-BACKLINK, incorrect directory back link [CLABIN.BACKUP.TMPSRC]DUMMY.MSG;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [CLABIN.NMAIL]NMAIL.LOG;77 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [CLABIN.NMAIL]NMAIL.LOG;76 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [DESIN.8800]2840HT86.GNC;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [DESIN.8800]2840TP86.GNC;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [DOWNE.MAIL]MAIL$0004008EF94A79B3.MAI;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [DOWNE.PRO]MORT.OBJ;15 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [DOWNE.PRO]OUTPUT.LOG;36 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [DOWNE.PRO]OUTPUT.LOG;35 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [DOWNE.PRO]OUTPUT.LOG;34 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [DOWNE.PRO]OUTPUT.LOG;33 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [DOWNE.PRO]OUTPUT.LOG;32 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [DOWNE.PRO]OUTPUT.LOG;31 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [DOWNE.PRO]OUTPUT.LOG;30 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [GAMBLE]CONFLICTS.LIS;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [GAMBLE.DOC]SMP.LOCK;6 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [GAMBLE]NETSERVER.LOG;5 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [GAMBLE.NMAIL]NMAIL.LOG;22 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [GAMBLE.NMAIL]NMAIL.LOG;21 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [GILLEY.MAIL]MAIL$0004008EF94A7B70.MAI;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [GILLEY]NETSERVER.LOG;657 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [GILLEY]NETSERVER.LOG;656 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [HALL]2.LOG;33 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [HALL]2.LOG;32 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [HALL]2.LOG;31 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [HALL]2.LOG;30 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [HALL]2.LOG;29 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [HALL]2.LOG;28 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [HALL]2.LOG;27 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [HALL]2.LOG;26 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [HALL]2.LOG;25 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [HALL]2.LOG;24 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [NAMOLLY]NETSERVER.LOG;2 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [NAMOLLY]NETSERVER.LOG;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [RUSS]082654.LOG;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [SCHROEDER.LOGIN]NETSERVER.LOG;17 %VERIFY-I-BADDIR, directory [SYSLOST.BOOTS] has invalid format %VERIFY-I-BADDIRENT, invalid file identification in directory entry [THOEN]NETSERVER.LOG;374 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [THOEN]NETSERVER.LOG;373 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [THOEN]NETSERVER.LOG;367 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [THOMAS.MAIL]MAIL$0004008EF94D75EB.MAI;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [THOMAS.MAIL]MAIL$0004008EF955DDF3.MAI;1 %VERIFY-I-BADDIRENT, invalid file identification in directory entry [THOMAS.MAIL]MAIL$0004008EFD118B44.MAI;1 %VERIFY-I-LOSTSCAN, due to directory errors, lost files will not be entered (5) %VERIFY-I-INCQUOTA, QUOTA.SYS indicates 69663 blocks used, actual use is 69740 blocks for [11,402] (6) %VERIFY-I-INCQUOTA, QUOTA.SYS indicates 1764 blocks used, actual use is 1770 blocks for [12,12] %VERIFY-I-INCQUOTA, QUOTA.SYS indicates 0 blocks used, actual use is 31 blocks for [11,720]

1. ANALYZE/DISK_STRUCTURE has completed the first two stages, and is beginning Stage 3. Stage 1 involves collection and verification of various volume information. ANALYZE/DISK_STRUCTURE found no problems with volume information. In Stage 2, ANALYZE/DISK_STRUCTURE copies the current version of QUOTA.SYS to working memory, and builds the structure on which a new copy is built during subsequent stages. The first error message is produced by Stage 3. Stage 3 uses the reserved file INDEXF.SYS to locate a variety of file problems. Here, Stage 3 detects a number of invalid file headers. Note that the error message includes the FID and the file name.
2. This error message is produced during Stage 4, during which ANALYZE/DISK_STRUCTURE builds a current version of BITMAP.SYS, resolves multiple references to extension headers, and corrects discrepancies in the map sections of headers. Here, ANALYZE/DISK_STRUCTURE has found that the specified logical blocks on the specified relative volume were marked allocated in the storage bit map, but were not allocated to a file.
3. This message marks the beginning of Stage 5. Here, messages stating "lost extension file header" and "invalid file header" indicate that ANALYZE/DISK_STRUCTURE is performing a pass of all entries placed on the invalid backlink map. This map was created in Stage 3.
4. This message marks the beginning of the second phase of Stage 5, in which ANALYZE/DISK_STRUCTURE confirms that all files in INDEX.SYS are retrievable through the directory structure. Here, the series of "invalid file identification..." messages indicates those directory entries that did not contain a valid file identification.
5. This message is produced by Stage 6, which is essentially a cleanup phase for lost files. This message indicates that ANALYZE/DISK_STRUCTURE encountered errors during the directory scan that were reported in previous messages. As a result, the file is not entered in directory [SYSLOST].
6. Here, ANALYZE/DISK_STRUCTURE begins Stage 7, in which it compares values stored in the quota file built during Stage 2 with values in the reserved file QUOTA.SYS. The last three messages here indicate discrepancies between the two files.
   Note that no messages were produced during Stage 8. During Stage 8, ANALYZE/DISK_STRUCTURE executes all operations placed on the deferred list, and if you specified /REPAIR, updates QUOTA.SYS and VOLSET.SYS as necessary.

	privacy and legal statement
6048PRO_075.HTML