Content-type: text/html
verify - checks the AdvFS on-disk metadata structures
/sbin/advfs/verify [-f|-d] [-v|-q] [-t] [-r] [-F] domain_name
Creates a hard link to ``fix'' a lost file in the
/???/lost+found
directory; deletes any directory
entries that do not have associated files; deletes files that have storage
bitmap or extent map problems; corrects inconsistencies in the storage bitmap.
Deletes lost files (that is, files with no directory entry).
Prints file status information. Selecting this option slows
down the
verify
procedure.
Prints minimal file status information.
Displays the mcell totals.
Checks the root domain.
Mounts the filesets of a file domain using the
mount
-d
option if there is a mount failure of the file
domain. Use this option with caution.
The verify command checks on-disk structures such as the bitfile metadata table (BMT), the storage bitmaps, the tag directory and the frag file for each fileset. It verifies that the directory structure is correct and that all directory entries reference a valid file (tag) and that all files (tags) have a directory entry.
The verify command checks the storage bitmap for double allocations and missing storage. It checks that all mcells in use belong to a bitfile and that all bitfiles have all of their mcells.
The verify command checks the consistency of free lists for mcells and tag directories. It checks that the mcells pointed to by tags in the tag directory match the corresponding mcells.
For each fileset in the specified file domain, the
verify
command checks the frag file headers for consistency. For each file that has
a fragment, the frag file is checked to ensure that the frag is marked as
in use.
You must be the root user to use this command.
Unless you are checking the root domain, all filesets in the file domain must be unmounted. The verify command automatically mounts all of the filesets in a file domain individually. If you choose the -r option when you run the verify command on the root domain, all filesets in the root domain must be mounted.
Run the verify command on /root and /usr from a single-user mode. To run the verify command in single-user mode, you must first run a mount update on the root (mount -u /). To run the command from multi-user mode, dismount any file system that you have mounted as /root or /usr and make sure there is no file activity.
If you run the verify command on a fileset that has any other file system (AdvFS or otherwise) mounted on it, an error results. If you have an fileset erroneously labeled as UFS and it overlaps a fileset labeled AdvFS, an error results. You can recover from this error by changing the erroneously-labeled fileset's fstype field from ufs to unused with the disklabel -s command. After changing the disk label, run the verify command.
If the -F option is specified and the verify command is unable to mount a fileset due to a failure of the file domain, the fileset is mounted using the mount -d option. Use this option with extreme caution and only as a last resort when you cannot mount a fileset. The mount -d option mounts an AdvFS fileset without running recovery on the file domain. Mounting without running recovery will cause your file domain to be inconsistent.
If you use the
-F
option, the
verify
command starts some recovery on the file domain before you mount it.
The
verify
utility returns a
0
(zero) on success if it did not find any corruption and a positive integer
on succes if it did find any corruption. The
verify
utility
returns a
-1
on failure.
The following example verifies the file domain dmnx with the filesets setx and sety: # /sbin/advfs/verify dmnx
+++ Domain verification +++
Domain Id 2f9eb70a.000f1db0
Checking disks ...
Checking storage allocated on disk /dev/rz10g
Checking storage allocated on disk /dev/rz10a
Checking mcell list ...
Checking mcell position field ...
Checking tag directories ...
+++ Fileset verification +++
+++ Fileset setx +++
Checking frag file headers ...
Checking frag file type lists ...
Scanning directories and files ...
300
Scanned 307 directories.
Scanning tags ...
1100
Scanned a total of 1135 tags.
Searching for lost files ...
1100
Searched 1135 tags, no lost files found.
+++ Fileset sety +++
Checking frag file headers ...
Checking frag file type lists ...
Scanning directories and files ...
900
Scanned 911 directories.
Scanning tags ...
5100
Scanned a total of 5173 tags.
Searching for lost files ...
5100
Searched 5173 tags, no lost files found.
#