Home > Veritas Storage Foundation™ File System Manual Pages


Maintenance Commands

Table of contents


ncheck_vxfs - generate path names from inode numbers for a VxFS file system


ncheck [ -V vxfs ] [ -i ilist ] [ -a ] [ -s ]
[ -o m,device=devid,b=block, [ block=block_range ],
[ sector=sector_range ], [ surface=[ sector_range ],]
| ckpt=ckpt_name ] special ...




ncheck generates a list of path names corresponding to inode numbers for files in a specified VxFS file system.

You can specify a range for some options. A range can be a single number, or two numbers separated by a hyphen (-). The range is inclusive. If you enter a hyphen and omit the first number (- number), the range begins at zero. If you omit the second number, the range ends at the end of the file system.

Names of directory files are followed by slash dot (/.).

Cluster File System Issues

No cluster issues; command operates the same on cluster file systems.


-o specific_options
Specifies options specific to the VxFS file system type. specific_options is a list of suboptions or keyword/attribute pairs.
Prints the path name containing file system block number block.
Prints information on all inodes containing or referencing block numbers in the specified range. The output format is the same as that for -o sector=, but the units used are file system blocks instead of sectors.
Lists the files residing in the specified Storage Checkpoint.
Specifies the device ID. Useful for multi-volume file systems.
Prints mode information (used in conjunction with -i generic option).
Reports on all inodes containing or referencing the sectors in sector_range. The output includes the inode number, fileset index of the inode, sectors contained, and the path name or inode type. Inodes searched include structural inodes and attribute inodes, so a path name is only generated when the sector is contained by a file. If the sector is not contained in any file, ``
'' is displayed for the inode type. Multiple -o sector= options accumulate.
surface= [ sector_range]
Performs a surface analysis. If a sector_range is specified, performs a surface analysis only for that range. All the sector are read and if the read of a sector fails, its sector number is printed. If any bad sectors are found, ncheck treats the list of bad sectors as input to the -o sector=sector_range option and produces a list containing or referencing inodes.


Report on all inodes or file system structures containing or referencing sector 20 through 35 (inclusive) in the file system

ncheck -V vxfs -osector=20-35  /dev/vx/rdsk/vol1

Same as above but report on all inodes or file system structures referencing any sector in the file system

ncheck -V vxfs -osector= /dev/vx/rdsk/vol1

Report on a specified range of block numbers (partial output shown):

ncheck -V vxfs -oblock=- /dev/vx/rdsk/vol05 

sectors(800000)         blocks(400001)         
-----------------       -----------------      
0-799999                0-400000               

fileset    fset        mtch  match               
name       indx  inode indx  inode blocks        name
---------- ---- ------ ---- ------ ------------- ------------------
STRUCTURAL    1      -    -      - 0-7           <reserved>
STRUCTURAL    1      -    -      - 8             <device_label>
STRUCTURAL    1      -    -      - 1049-1087     <reserved>
STRUCTURAL    1      -    -      - 9-16          <object_loc_tbl>
STRUCTURAL    1      -    -      - 1041-1048     <object_loc_tbl>
STRUCTURAL    1      -    -      - 17-1040       <intent_log>
STRUCTURAL    1      -    -      - 1088          <alloc_unit_hdr>
. . .
STRUCTURAL    1     38    1      6 1154-1161     <inode_list>
STRUCTURAL    1     39  999      7 1162-1169     <inode_list>
UNNAMED     999      4    -      - 3188-3189     /file1
UNNAMED     999      4    -      - 1255-1302     /file1
List the files in the Storage Checkpoint named checkpoint1 on the device /dev/vx/rdsk/dg1/vol1:

ncheck -V vxfs -o ckpt=checkpoint1 /dev/vx/rdsk/dg1/vol1


When the file system structure is not correct, ncheck prints three question marks ( ??? ) to denote the ``parent'' of a parentless file. A path name beginning with dot dot dot () indicates a loop. A path name beginning with three asterisks ( *** ) denotes a directory entry whose dot dot (..) entry does not correspond with the directory in which it was found.


ncheck, sort, fsckptadm(1M), fsck_vxfs(1M), fs_vxfs(4)

Last updated: 01 April 2006
Copyright ©2009 Symantec Corporation
All rights reserved.