PROBLEM: (90555) (PATCH ID: OSF520-186) ******** This patch fixes a rmvol failure that would be seen as an E_PAGE_NOT_MAPPED error when no more space is available for user data migration to another volume in the domain. The error would appear like the following: # rmvol -F dsk2b rmvol_dmn1 rmvol: Removing volume '/dev/disk/dsk2b' from domain 'rmvol_dmn1' rmvol: Can't move file /rmvol_fset1/file12 pages rmvol: Error = E_PAGE_NOT_MAPPED (-1035) rmvol: Can't move file /rmvol_fset1/file12 metadata rmvol: Can't remove volume '/dev/disk/dsk2b' from domain 'rmvol_dmn1' PROBLEM: (90914) (PATCH ID: OSF520-231) ******** The vdf and showfdmn commands might incorrectly claim that you have the error showfdmn: No such file or directory This will occur when, for example, you create a domain with two volumes. Now you remove the initial volume, When you issue either the vdf or "showfdmn -mk" commands, the error will appear. PROBLEM: (91062) (PATCH ID: OSF520-320) ******** Change the rmvol error messages to more accurately reflect why rmvol failed. Change showfdmn so that it does not say it succeeded when it failed. PROBLEM: (90796) (PATCH ID: OSF520-355) ******** advscan incorrectly processes concatenated options (e.g. -ar vs. -a -r). For instance, if -ar is specified, the second argument (-r) will not be processed (in this case, the recreating of domains will not be done). PROBLEM: (87862) (PATCH ID: OSF520-467) ******** Problem: Using LSM volumes greater than 1Tb in an AdvFS domain can cause various problems from spurious errors to possible filesystem corruption or panics. This patch fixes this problem. Problem: AdvFS cannot use volumes greater than 2Tb, even though they can be constructed with LSM. Before this fix, there was no warning if the user tried to use such a volume in an AdvFS domain. Now a warning is issued. PROBLEM: (93805) (PATCH ID: OSF520-562) ******** A potential security vulnerability has been discovered, where under certain circumstances, system integrity may be compromised. This may be in the form of improper file or privilege management. Compaq has corrected this potential vulnerability. PROBLEM: (91901, 93789) (PATCH ID: OSF520-680) ******** 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: (84422, 87576, 87802, 90472, 92015, 93597) (PATCH ID: OSF520-658) ******** This patch fixes many problems with dsfmgr including: command argument parsing, messages and error handling. This patch makes all release versions of dsfmgr functionally the same. Problems: - 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: (91654, 93118) (PATCH ID: OSF520-798) ******** 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.