4.1; salacl (salvage_acls), revision 4.1, 82/07/08
SALACL (SALVAGE_ACL) -- Salvage an Access Control List.
usage: salacl [(-ns | -no_summary) | (-v | -verify) | (-nm | -no_merge)]
[volume]
FORMAT
SALACL [options] [volume]
SALACL salvages the ACL structure on the volume you specify. It corrects
the reference counts on all ACL objects. Reference counts record the
number of files that use each ACL. After it repairs reference counts,
SALACL merges duplicate ACLs into a single copy, and deletes unused ACLs.
You should run SALACL once a week or so unless you always receive reports
that no reference counts needed repairing (i.e., everything is perfect).
SALACL cannot merge duplicate ACLs on files that are currently in use
(locked). This is always the case for libraries, for example. This is not
especially serious, as the duplication consumes very little disk space.
To merge all possible ACLs on a node, including things like libraries, bring
the node up diskless, mount the volume using MTVOL, and then run
SALACL on the mounted volume.
ARGUMENTS
volume
(optional) Specify the entry directory pathname for the volume whose
ACLs you intend to salvage. Note that SALACL cannot
salvage a volume mounted on a remote node.
Default if omitted: '/' (node entry directory)
OPTIONS
-NS
-NO_SUMMARY Suppress summary information.
-V
-VERIFY Verify only; do not delete or merge any ACLs.
-NM
-NO_MERGE Do not merge duplicate ACLs into a single copy.
EXAMPLE
$ salacl Salvage the ACLs of the current volume.
Warning: unable to merge two equivalent ACLs:
//grover/sys/node_data/pdb - object is in use (OS/file server)
Warning: unable to merge two equivalent ACLs:
//grover/sys/node_data/Shell - object is in use (OS/file server)
ACL objects found: 24
ACL reference counts fixed: 2
ACLs garbage collected: 0
ACLs in use during g.c.: 0
ACLs merged with equivalents: 12