HP Tru64 Unix Release Notes for Version 5.1B-6 (5900-1150)

# /sbin/advfs/fixfdmn domain_name
fixfdmn: Checking the RBMT.
fixfdmn: Clearing the log on volume /dev/disk/dsk10c.
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: Checking for frag overlaps.
fixfdmn: Checking for BMT mcell orphans.
fixfdmn: Checking for file overlaps.
fixfdmn: Checking the directories.
fixfdmn: Checking the frag file(s).
fixfdmn: Checking the quota files.
fixfdmn: Checking the SBM.
fixfdmn: Completed.
You can use this command proactively before the RBMT grows to prevent the problem from
occurring, or you can use it after the problem occurs.
In summary, the following domains are not in danger:
• Version 3 domains
• Domains created under Version 5.1B-6
• Domains with RBMT files that are not longer than one page
The showfile and showdmn commands can provide information about your domains.
Use the showdmn command to find out what volumes a domain has. For example:
# /sbin/showfdmn domain_name
Id Date Created LogPgs Version Domain Name
447350cd.000eba90 Tue May 23 11:13:33 2006 512 4 domain_name
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 71132000 71121632 0% on 256 256 /dev/disk/dsk4c
Use the showfile command to determine if an RBMT file has more than one page. To do this,
select any mounted fileset from the domain in question, find the mount point for the fileset, and
enter the following command. (Note that .tags/M-6 represents volume 1. Subsequent volumes
are incremented by a factor of six, so that volume 2 uses .tags/M-12, volume 3 uses
.tags/M-18, and so on.) For example:
# /usr/sbin/showfile mountpoint/.tags/M-6
Id Vol PgSz Pages XtntType Segs SegSz I/O Perf File
fffffffa.0000 1 16 1 simple ** ** ftx 100% M-6
See the fixfdmn(8), showfile(8), and showfile(8) reference pages for information about using these
commands.
Possible Errors Seen After Kit Installation
The following problems have been known to occur after Version 5.1B-4 has been installed:
• The Common Data Security Architecture (CDSA), IP Security Protocol (IPsec), or Single
Sign-On (SSO) do not work.
• The following error message is displayed during boot time:
CSSM_ModuleLoad: CSSM error 4107
If you experience these problems, make sure that the following command line has been executed:
Installation Release Notes 19