tag2name(8) System Manager's Manual tag2name(8)
NAME
tag2name - Display the path name of an AdvFS file
SYNOPSIS
/sbin/advfs/tag2name tags_directory/file_tag
/sbin/advfs/tag2name [-r] domain fileset_id file_tag
OPTIONS
Specify the [-r] option to operate on the raw device (character device special file) of the fileset instead of the block device.
OPERANDS
Specifies the name of an AdvFS domain. Specifies the name of an AdvFS fileset using the following format: Specify the -S tag to force the
command to interpret the name you supply as a fileset name. Specify the fileset by entering either the name of the fileset, fileset, or
the file's fileset tag number, -T fileset_tag. Specifies the relative path of the AdvFS tags directory for a fileset. If you do not spec-
ify this directory, the default is mount_point/.tags. Specifies an AdvFS file tag number.
DESCRIPTION
Internally, AdvFS identifies files by tag numbers (similar to inodes in UFS). Internal messages, error messages, and output from diagnostic
utilities usually specify a tag number in place of a file name. Use the tag2name command to determine the name and path of an AdvFS file
that is identified by a tag number.
If you enter an invalid tag number, the command returns the range of the valid tags for the fileset.
Mounted Filesets
Each mounted AdvFS fileset has a directory in its mount point. To obtain a file name, specify the path to the directory for the fileset,
followed by the tag number. The full path name of the corresponding file is displayed to stdout. This syntax uses AdvFS system calls.
Unmounted Filesets
When you use the second form, the utility does not use AdvFS code and does not depend on the filset being mounted. The path name of the
file is relative to the fileset and is displayed on stdout.
One use of the second form is to obtain names of files from a fileset that is unmounted and might produce a domain panic or a system panic
if it were mounted.
NOTES
An active domain, which is a domain with one or more of its filesets mounted, has all of its volumes opened using block device special
files. These devices cannot be opened a second time without first being unmounted. However, the character device special files for the
volumes can be opened more than once while still mounted.
It can be misleading to use the second form of this utility on a domain with mounted filesets. Unlike the first form of the utility, the
second form does not synchronize its read requests with AdvFS file domain read and write requests. To avoid this problem, unmount all the
active filesets in the domain before using the second form of this utility.
For example, the AdvFS can be writing to the disk as the utility is reading from the disk. Therefore, when you run the utility, metadata
may not have been flushed in time for the utility to read it and consecutive reads of the same file page may return unpredictable or con-
tradictory results. [The domain is not harmed.]
RESTRICTIONS
The second form of this utility can fail to open a block device, even when there are no filesets mounted for the domain and the AdvFS dae-
mon, advfsd is running. The daemon, as it runs, activates the domain for a brief time. If the tag2name utility fails in this situation,
run it again.
You must be the root user to use the tag2name utility. The tag you specify must be numeric and greater than 1.
EXAMPLES
The following example displays the file name corresponding to tag 5 in the usr fileset. It assumes the current working directory is /usr: #
/sbin/advfs/tag2name .tags/5
/usr/quota.group The following example displays the file name of the file whose tag is 145 in domain_1 fileset_1: # /sbin/advfs/tag2name
domain_1 fileset_1 145
joe/save/oldfile
FILES
Specifies the command path. Specifies the volumes in the domain.
SEE ALSO
advfs(4)
tag2name(8)