PROBLEM 1
---------
Fixfdmn does not properly handle domains with multi-page 
RBMT files.  Error messages are of the type:

fixfdmn: Gathering volume information.
fixfdmn: Opening directory '/etc/fdmns/hsv1a-fs01'.
fixfdmn: Opening the volumes.
fixfdmn: Setting volume '/dev/disk/dsk1101a' to volume number 1.
fixfdmn: Checking the RBMT.
fixfdmn: Found corruptions in next RBMT page mcell.
fixfdmn: Found the transaction log on volume /dev/disk/dsk1101a.
fixfdmn: Mcell (1,0,0) is corrupt.
fixfdmn: Mcell (1,0,4) is corrupt.
fixfdmn: Loading subsystem extents.
fixfdmn: Can't convert page 12 to an LBN, valid range is 0 to 12.
fixfdmn: Can't convert [R]BMT page 12 to LBN.
fixfdmn: Error collecting subsystem extents.

PROBLEM 2
---------
When growing an AdvFS volume, if there are multiple extents 
representing an SBM, fixfdmn does not work on all the SBM extents.
Error messages are of the type:

 fixfdmn: Checking the RBMT.
 fixfdmn: XOR value for SBM Page 6 is not correct.
 fixfdmn: XOR value for SBM Page 7 is not correct.
 fixfdmn: XOR value for SBM Page 107334860 is not correct.
 fixfdmn: Unable to find the starting block of the SBM.

PROBLEM 3
---------
Fixfdmn fails when a clone's original fileset is missing a tag 
which is present in the clone fileset.

PROBLEM 4
---------
Running fixfdmn only on a clone fileset always fails with an error.
Error messages are of the type:

#fixfdmn  new clone
 fixfdmn: Checking the RBMT.
 fixfdmn: Clearing the log on volume /dev/disk/dsk5c.
 fixfdmn: Checking the BMT mcell data.
 fixfdmn: Checking the deferred delete list.
 fixfdmn: Checking the root tag file.
 fixfdmn: Checking the tag file(s).
 fixfdmn: Checking the mcell nodes.
 fixfdmn: Checking the BMT chains.
 fixfdmn: Checking the frag file group headers.
 fixfdmn: Error correcting the BMT chains on fileset clone.
 fixfdmn is not able to continue, no changes
     made to domain, exiting.


PROBLEM 5
---------
Fixfdmn exits when it encounters a domain with more than 
one root tag file.  Error messages are of the type: 

fixfdmn: Unable to continue, more than one root tag file.


PROBLEM 6
---------
When fixfdmn is run with an invalid fileset argument,
the user is prompted if they wish to exit or run it against 
all the filesets in the domain.  If they decide to exit, 
fixfdmn continues anyway.  Error messages are of the type:

fixfdmn: Unable to find the requested fileset 'not_a_fileset',
         Do you want to continue? ([y]/n) n
fixfdmn: Checking the SBM.


PROBLEM 7
---------
Fixfdmn does not properly handle domains with multi-page RBMT files 
that have their last page full and need to grow. Domains of this type 
will domain panic when being activated (mounting the first fileset).  
Error messages are of the type: 

WARNING: file tag -6 in fileset "" has > 64K extent mcells.

PROBLEM 8
---------
Fixfdmn can hang during low memory conditions with the following message.

"fixfdmn: Can't allocate x bytes.
Do you want fixfdmn to try this allocation again?"


