PROBLEM:  (QAR 62648,QAR 62577)    (Patch ID: OSF440-040)
********
This enhancement for the /sbin/advfs/verify utility allows it to detect loops
in the list of free frags kept in the frags file.

PROBLEM:  (QAR 67989, QAR 71541)    (Patch ID: OSF440-183)
********

This patch prevents the corruption of the file system when the verify 
command is invoked with the '-r' and '-f' flags on an active domain.
Now, 
when the user specifies the -r flag with either the -f or the -d flag,
the 
command returns a usage message.

PROBLEM:  (69193, 75226, 71876, 75211) (PATCH ID: OSF440-330)
********

This patch fixes the following  /sbin/advfs/verify command problems:

1.)  Verify  fails to complete on a large number of files. After the
command is terminated, filesets are left mounted. An error message like the
following is produced:

                insert_set_tag: can't get bitfile set params
               error: -1093, E_NO_SUCH_BF_SET (-1093)
               set tag: 7.32772 (0x00000007.0x00008004)

2.) Verify  will core dump when an offset into mountd[] array that is
used to pull out the fileset name is corrupted.  The fix  is  not use
the corrupted number as an offset into the mounted[] array, but
instead use the bogus offset to produce an error.

3.) Verify  incorrectly reports errors on BMT's that have multiple
extent records for domains created with the mkfdmn -p switch.  This can
produce an error message like the following:

                Checking mcell list ...
                    set_mcell_position: position field already set
                    disk: 2, mcell id (page.cell): 0.7
                    set tag: -2.0 (0xfffffffe.0x00000000)
                    tag: -12.0 (0xfffffff4.0x00000000)

4.) Verify fails when lseeking on very large domains. The fix is instead
of multimultiplying two 'ints' and assigning them into a long, causing
a '32' bit roll over error, typecast one of the 'ints' to 'long' then
perfom the multiplication.

PROBLEM: (EVT18628A, 59132) (PATCH ID: OSF440-585)
********
This patch modifies advfs kernel code and several utilities.
AdvFS will no longer panic with the following error:
ADVFS EXCEPTION : panic cpu(0) : bad frag free list.
The code is modified so that during frag allocation when advfs determines
that the frag group header's free list has been corrupted, it stops using
it and marks it BAD. It is then removed from the free list so no more
allocations can take place AND no deallocations are performed. The verify,
shfragbf and vfragpg programs are modified to report BAD frag groups.