PROBLEM: (91901, 93789) (PATCH ID: OSF540-001)
********
advscan can be fooled into thinking everything is OK, when it is not.
If you create a domain and add a volumes to it.  Say the domain is
TEST and two volumes are ${DISK}a and ${DISK}b.  Now do the following:
       mkdir /etc/fdmns/BAD
       mv    /etc/fdmns/test/${DISK}b /etc/fdmns/BAD/
when advscan is run on ${DISK}, it will report everything as ok.
       :
       Actual partitions found:
                              ${DISK}a
                              ${DISK}b

Now when you try to mount the domain, it will fail:
       mount TEST#TEST /mnt
       /etc/fdmns/TEST has 2 links.
       TEST#TEST on /mnt: I/O error

The new behavior will yield:
        Actual partitions found:
                              ${DISK}a
                              ${DISK}b   *** Incorrectly located in ***
                                         /etc/fdmns/BAD
The mount will still fail, but it is now expected.


The other issue will now print an error message like:
        AdvFS I/O error:
            Domain#Fileset: dombac#fsetbac
            Mounted on: /bac
            Volume: /dev/disk/dsk630c
            Tag: 0x000000c1.8001
            Page: 548676
            Block: 2431675264
            Block count: 256
            Type of operation: Write
            Error: 30   (see /usr/include/errno.h)      <<<---NEW
            ...

PROBLEM: (91654, 93118) (PATCH ID: OSF540-066)
********
This patch will fix a rmvol E_PAGE_NOT_MAPPED error seen as follows:

rmvol: Removing volume '/dev/disk/dsk4b' from domain 'test'
rmvol: Can't move file /test/FILE89 pages
rmvol: Error = E_PAGE_NOT_MAPPED (-1035)
rmvol: Can't move file /test/FILE89 metadata
rmvol: Can't remove volume '/dev/disk/dsk4b' from domain 'test'

This patch will also eliminate an ENO_MORE_BLKS error seen when
COWing a to a clone file while a rmvol is in progress.  The following
error will be seen:

WARNING: AdvFS cannot copy-on-write data to a clone file.
WARNING: encountered the following error: ENO_MORE_BLKS (-1040)
WARNING: encountered the following error: ENO_MORE_BLKS (-1040)
WARNING: do not continue using the clone fileset.

PROBLEM: (87802, 84422, 87576, 87802, 90472, 92015, 93597)
******** (PATCH ID: OSF540-135)

This patch addresses one problem. When the system discovers a new device,it
generates a new name for it to create the device special file (dsf). The
instance part, a number, can get quite large when doing many disk backups
using a clone-copy-delete procedure. Since the instance is always increasing,
the names quickly become hard to manage. Also, the backup program must
determine the new numbers each time it runs.
To fix this problem, the dsfmgr program has added a new option that will
minimize (or set) the instance numbers to the lowest possible value.
If your system deletes and creates a large number of devices or deletes and
creates devices often, this patch will help keep the values lower.
For systems that have a fixed configuration except for the backup procedure,
it will mean that each new set of cloned backup devices will always have the
same new names. It can simplify the backup procedure.


 - an illegal input argument causes a core dump
     This usually occurs when no arguments are entered.

 - improper error handling by the stat function
   during boot dsfmgr fails with:
    dsfmgr: NOTE: creating device special files for system at /
    dsfmgr: ERROR: stat( "/dev/disk/dsk19a" ) = kernel database - duplicate
                     device ID's +dsk19a
    /sbin/dn_setup: 1573120 Memory fault - core dumped

 - the move/exchange may cause data errors
     This occurs when it encountered a partial set of device nodes.

 - during boot the following message is seen:
   =============================
  Problem occurred again while booting all nodes of the cluster.
    The problem occurred on two nodes: tcr6b:
  Checking device naming:
  ERROR : DEC_CHW_COMP : /etc/dec_hwc_cdb: invalid database size.
             Is 412648, sb 412408.
  ERROR : DEC_CHW_COMP : /etc/dec_hwc_cdb.bak: invalid backup size.
             Is 412648, sb 412408.
  bcheckrc: Device Naming failed initial check.
      Correct errors and then continue or reboot.
   =============================
    This can be caused by a file update during the dsfmgr read of the file.
    Nothing is wrong and a ^D (ctrl D) will continue the boot again.
    This fix will detect this senerio and the system will boot without any
    operator intervention.

PROBLEM: (SSRT2275) (PATCH ID: OSF540-356)
********
This patch provides protection against a class of  potential security
vulnerabilities called buffer overflows. Buffer overflows are sometimes
exploited in an attempt to subvert the function of a privileged program
and possibly execute commands at the elevated privileges if the program
file has the setuid privilege. This patch allows a system administrator
to enable memory management protections that limit potential buffer
overflow vulnerabilities.