How do I read the FAU Listing of Most Fragmented Files?
Here is a sample FAU output:
102: (370,71,1:53) [PHAPPL.PCARS.DATA]PCARS049.DAT;1
102: (370,71,1:52) [PHAPPL.PCARS.DATA]PCARS049.DAT;1
102: (370,71,1:54) [PHAPPL.PCARS.DATA]PCARS049.DAT;1
40: (370,71,1:55) [PHAPPL.PCARS.DATA]PCARS049.DAT;1
The first number, 102, is the number of fragments the file is broken into. The number of fragments a file contains all depends upon whether or not it is contiguous. All files will contain at least one fragment. Contiguous files will always have one fragment. Files that contain no fragments at all are called zero length files.
Every file is assigned a file identification number when it is created. The file ID comprises 3 numbers. The first number, 370, is the file index number. The file index is a direct pointer into the array of file headers in the INDEXF.SYS file.
The second number, 71, refers to the number of times this file index number has been used, with the exception that the first 9 reserved system files have a different numbering scheme.
The third number, 1, is the relative volume number. This number is either 0 or 1 for non-bound volume sets. In a bound volume set these numbers will relate to the specific disk in the volume set. The primary disk in the volume set will always be 1.
The :53,:52,:54,:55 are the extension header count. The extension header count is the actual number of the extended file header. In the example above these would be the 53
rd
, 52
nd
, 54
th
and 55
th
file headers. These additional file headers are needed when the primary file header no longer has room to store the needed information. NOTE: The extension header count may not appear in your FAU output.
This example indicates that this file is extremely fragmented. In order for VMS to create another file header for a file, the first one must be used up or full. The information here indicates that this file has at least 55 additional file headers and these headers contain 102 fragments each. At one time this file must have had over 5500 fragments.
If this FAQ helped, please let us know. If you didn't find the answer to your question here please e-mail
|
