fsvmap(1M)fsvmap(1M)NAMEfsvmap - map volumes of VxFS file systems to files
AVAILABILITY
VRTSvxfs
SYNOPSIS
/opt/VRTS/bin/fsvmap [ -mdv ] [ -c checkpoint | -C ]
mount_point_or_vset [ volume ... ]
DESCRIPTION
The fsvmap command was introduced to verify Dynamic Storage Tiering
allocation policies.
The fsvmap command maps one or more volumes to the files that have
extents on those volumes. By default, the output is limited to the
default fileset.
The fsvmap command can report information on disabled volumes, as long
as those volumes contain no metadata. That is, the volumes must be
dataonly. See the fsvoladm(1m) manual page for information on dataonly
volumes. The information on disabled volumes can be used to determine
which files are or would be affected by the loss of a dataonly volume,
both before and after the volume is lost.
NOTES
The fsvmap command only operates on VxFS multi-volume file systems.
The fsvmap command considers extents for any extended attribute inodes
to be associated with the file that owns those attributes.
Unprintable characters in file names are translated into a sequence of
printable characters so that each file is guaranteed to be displayed on
a single line. The sequence is //0xXX, where XX is a hex sequence of
the character's ASCII value. Since // is not a valid sequence in a
filename, the format is unambiguous. For example, in the following
output:
Data UNNAMED /file with embedded//0x0anewline //0x0a repre‐
sents an embedded newline character.
Use the fsmap command to report extent information for files on a VxFS
file system. The functionality of fsmap is the reverse of fsvmap.
The fsvmap command does not print any information for empty files.
Cluster File System Issues
No cluster issues; command operates the same on cluster file systems.
OPTIONS-C Displays output for all Storage Checkpoints as well as the
default fileset.
-c checkpoint
Limits the output to files in the specified Storage Check‐
points.
-d Disables the translation of unprintable characters. Each
filename is printed without being translated, and is both
prefixed and suffixed by // to allow detection of when the
filename begins and ends. For example, a filename with a
newline character displays as follows:
Data UNNAMED ///file with embedded
newline//
-m Reports metadata for each file.
-v Verbose output.
ARGUMENTS
mount_point_or_vset
Specifies the mount point of a file system or a file system's
volume set device.
volume Limits the output to files on the specified volumes. If no
volumes are specified, fsvmap reports information for all
volumes in the file system's volume set. If only one volume
is specified, the volume name is suppressed in the output.
See EXAMPLES.
EXAMPLES
To report files that have extents on a single volume:
# fsvmap /dev/vx/rdsk/fstest/testvset vol1
/.
/ns2
/ns3
/file1
To report files that have extents on any of multiple volumes:
# fsvmap /dev/vx/rdsk/fstest/testvset vol1 vol2
vol1 /.
vol1 /ns2
vol1 /ns3
vol1 /file1
vol2 /file1
vol2 /file2
To report files from all Storage Checkpoints that have extents on a
single volume:
# fsvmap-C /dev/vx/rdsk/fstest/testvset vol1
UNNAMED /.
UNNAMED /file1
UNNAMED /ns2
UNNAMED /ns3
c1 /file1
To report files that have extents, either data or metadata, on a single
volume:
# fsvmap-m /dev/vx/rdsk/fstest/testvset vol1
Data /.
Data /file1
Meta /file1
Data /ns2
Data /ns3
Meta /has_dattr
To report files from all Storage Checkpoints that have data or metadata
extents on any volume in the file system and indicate if the volume has
file system metadata:
# fsvmap-mvC /dev/vx/rdsk/fstest/testvset
Meta STRUCTURAL vol1 //volume has filesystem metadata//
Data UNNAMED vol1 /.
Data UNNAMED vol1 /ns2
Data UNNAMED vol1 /ns3
Data UNNAMED vol1 /file1
Meta UNNAMED vol1 /file1
SEE ALSOfsmap(1M), fsvoladm(1M), vxvset(1M)VxFS 5.0 7 Jan 2008 fsvmap(1M)
