Reporting file extents

Multi-volume file system feature provides the capability for file-to-volume mapping and volume-to-file mapping via the fsmap and fsvmap commands. The fsmap command reports the volume name, logical offset, and size of data extents, or the volume name and size of indirect extents associated with a file on a multi-volume file system. The fsvmap command maps volumes to the files that have extents on those volumes.

See the fsmap(1M) and fsvmap(1M) manual pages.

The fsmap command requires open() permission for each file or directory specified. Root permission is required to report the list of files with extents on a particular volume.

The following examples show typical uses of the fsmap and fsvmap commands.

Example of using the fsmap command

Example of using the fsvmap command

  1. Report the extents of files on multiple volumes:
      # fsvmap /dev/vx/rdsk/fstest/testvset vol1 vol2
      vol1  /.
      vol1  /ns2
      vol1  /ns3
      vol1  /file1
      vol2  /file1
      vol2  /file2
  2. Report the extents of files that have either data or metadata on a single volume in all Storage Checkpoints, and indicate if the volume has file system metadata:
      # fsvmap -mvC /dev/vx/rdsk/fstest/testvset vol1
      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