 |
Click this button to go to the index for this section. |
advscan(8)
NAME
advscan - Locate AdvFS volumes on disk devices
SYNOPSIS
/sbin/advfs/advscan [-g] [-a] [-r] [-f domain_name]
devices... disk_group...
PARAMETERS
devices
Specifies the device names of disks to scan for AdvFS volumes.
disk_group
Specifies the Logical Storage Manager (LSM) disk groups to scan for
AdvFS volumes.
FLAGS
-g List the AdvFS volumes in the order they are found on each disk device
or LSM disk group.
-a Scans all devices found in any /etc/fdmns domain as well as those in
the command line.
-r Re-creates missing domains. The domain name is created from the device
names or LSM disk group names.
-f domain_name
Fixes the domain count and the links in the /etc/fdmns directory for
the named domain.
DESCRIPTION
The advscan command locates AdvFS volumes (disk partitions or LSM volumes)
that are in AdvFS domains.
Given the AdvFS volumes, you can re-create or fix the /etc/fdmns directory
of a named domain or LSM disk group. For example, if you have moved disks
to a new system, moved disks around in a way that has changed device
numbers, or have lost track of where the AdvFS domains are, you can use
this command to locate them.
Another use of the advscan command is to repair AdvFS domains when you have
broken them. For example, if you mistakenly delete the /etc/fdmns
directory, delete a domain directory in the /etc/fdmns directory, or delete
links from a domain directory under the /etc/fdmns directory, you can use
the advscan command to fix the problem.
The advscan command accepts a list of disk device names and/or LSM disk
groups names and searches all the disk partitions to determine which
partitions are part of an AdvFS domain.
You can run the advscan command to rebuild all or part of your /etc/fdmns
directory or you can rebuild it manually by supplying all the names of the
AdvFS volumes in a domain.
If the -g flag is not set, the AdvFS volumes are listed as they are grouped
in domains. Set the flag to list the AdvFS volumes in the order they are
found on each disk.
Run the advscan command with the -r flag set to re-create missing domains
from the /etc/fdmns directory, missing links, or the entire /etc/fdmns
directory.
Although the advscan command will rebuild the /etc/fdmns directory
automatically, DIGITAL recommends that you always keep a hard-copy record
of the current /etc/fdmns directory.
To determine if a disk partition is part of an AdvFS domain, the advscan
command performs the following functions:
· Reads the first two pages of a partition to determine if it is an
AdvFS volume and to find the domain information.
· Reads the disk label to sort out overlapping partitions. The size of
overlapping partitions are examined and compared to the domain
information to determine which partitions are in the domain. These
partitions are reported in the output.
· Reads the boot block to determine if the partition is AdvFS root
bootable.
The advscan command displays the date the domain was created, the on-disk
structure version, and the last known or current state of the volume.
In order to mount an AdvFS file system into a domain, the domain must be
consistent. An AdvFS domain is consistent when the number of physical
partitions or volumes with the correct domain ID are equal to both the
domain volume count (which is a number stored in the domain) and the number
of links to the partitions that are in the /etc/fdmns directory.
Domain inconsistencies can occur in diverse ways. Use the -f flag to
correct domain inconsistencies.
If you attempt to mount an inconsistent domain, a message similar to the
following will appear on the console:
# Volume count mismatch for domain dmnz.
dmnz expects 2 volumes, /etc/fdmns/dmnz has 1 links.
RESTRICTIONS
You must be the root user to use this command.
EXAMPLES
The following are examples of the output from the advscan command.
The following example scans devices rz3 and diskgroup rootdg for AdvFS
partitions:
# advscan rz3 rootdg
Scanning devices /dev/rrz3 /dev/rvol/rootdg
Found domains:
usr_domain
Domain Id 30a91a42.0001e060
Created Tue Nov 14 14:37:54 1995
Domain volumes 2
/etc/fdmns links 2
Actual partitions found:
rz3g
rootdg.vol03
The following example scans devices found in /etc/fdmns. It uses the -g
option to list partitions in the order they are found on the disks rather
than grouping them into domains and matching them with the /etc/fdmns
directory.
# advscan -a -g
scanning disks /dev/rrz2 /dev/rrz3 /dev/rvol/rootdg
Partition Domain Id
/dev/rrz2a 30a919ff.000ec470 V3, mounted, bootable
1 volume in domain
Created Tue Nov 14 14:36:47 1995
Last mount Wed Dec 31 16:00:04 1969
/dev/rrz2g 30a91a32.0007c250 V3, mounted
1 volume in domain
Created Tue Nov 14 14:37:38 1995
Last mount Thu Nov 30 17:14:16 1995
/dev/rrz3a 30abe160.00028eff V3, never mounted
1 volume in domain
Created Thu Nov 16 17:12:00 1995
/dev/rrz3g 30a91a42.0001e060 V3, mounted
1 volume in domain
Created Tue Nov 14 14:37:54 1995
Last mount Thu Nov 30 17:14:17 1995
rootdg.vol01 30c62c74.00036750 V3, dismounted
2 volumes in domain
Created Wed Dec 6 15:51:16 1995
Last mount Wed Dec 6 17:16:06 1995
rootdg.vol02 30c62c74.00036750 V3, dismounted
Created Wed Dec 6 15:51:16 1995
Last mount Wed Dec 6 17:16:06 1995
For the following example, two domains using device rz3 and diskgroup
rootdg were removed from the /etc/fdmns directory. The advscan command
scans device rz3 and diskgroup rootdg and then re-creates the missing
domains.
# advscan -r rz3 rootdg
Scanning disks /dev/rrz3 /dev/rvol/rootdg
Found domains:
*unknown*
Domain Id 30a91a42.0001e060
Created Tue Nov 14 14:37:54 1995
Domain volumes 1
/etc/fdmns links 0
Actual partitions found:
rz3g*
*unknown*
Domain Id 30c62c74.00036750
Created Wed Dec 6 15:51:16 1995
Domain volumes 2
/etc/fdmns links 0
Actual partitions found:
rootdg.vol01*
rootdg.vol02*
Creating /etc/fdmns/domain_rz3g/
linking rz3g
Creating /etc/fdmns/domain_rootdg.vol01_rootdg.vol02/
linking rootdg.vol01
linking rootdg.vol02
FILES
/sbin/advfs/advscan
Specifies the command path.
RELATED INFORMATION
fstab(4), disklabel(8)