ncheck_vxfs(1M)ncheck_vxfs(1M)NAMEncheck_vxfs - generate path names from inode numbers for a VxFS file
[ generic_options ]
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 num‐
ber or two numbers separated by a hyphen (-). The range is inclusive.
If you enter a hyphen and omit the first number, the range begins at
zero. If you omit the second number, the range ends at the end of the
Names of directory files are followed by slash dot (/.).
Supported by the generic command. See ncheck(1M).
Specifies the VxFS file system type.
Allow printing of the names dot
and dot dot which are ordinarily suppressed.
Limit the report to the files on the inode list,
ilist, that follows. The ilist must be separated
by commas without spaces.
Specifies options specific to the VxFS file system type.
specific_options is a list of suboptions or key‐
Prints the path name containing file system block
Prints information on all inodes containing or ref‐
erencing block numbers
in the specified range. The output for‐
mat is the same as that for but the units
used are file system blocks instead of
Lists the files residing in the specified Storage
Specifies the device ID.
Used for multi-volume file systems. If
the option is not specified, is run on
all available devices. If is specified,
all subsequent block or sector ranges are
scanned for the device specified by
Prints mode information (used in conjunction with
Reports on all inodes containing or referencing the
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
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,
treats the list of bad sectors as input
to the option and produces a list con‐
taining or referencing inodes.
Report only on special files and regular files with set-user-
This option may be used to detect violations
of security policy.
Report on files containing or referencing the specified sec‐
Output consists of the fileset name, fileset
index, inode number, and pathname of file or
file type if a structural inode or attribute
inode. Sectors not allocated to any file or
file system structure are reported as Sectors
not part of the file system are reported as
Unused or irrelevant fields are printed as
sector_list consists of one or more ranges of
sector numbers, separated by commas without
intervening spaces. Multiple options accumu‐
Prints the completed command, but does not perform any
Report on all inodes or file system structures containing or referenc‐
ing sector 20 through 35 (inclusive) in the file system
The following command is same as above, but reports on all inodes or
file system structures referencing any sector in the file system:
Report on a specified range of block numbers (partial output shown):
ncheck -F vxfs -oblock=- /dev/vx/rdsk/vset5
fileset fset mtch match devid/
name indx inode indx inode blocks name
---------- ---- ------ ---- ------ ------------- ------------------
STRUCTURAL 1 3 - 35 0/9-0/10 <fileset_header>
STRUCTURAL 1 4 1 - 0/11-0/14 <inode_alloc_unit>
STRUCTURAL 1 5 1 37 0/7440-0/7447 <inode_list>
STRUCTURAL 1 5 1 37 0/24-0/31 <inode_list>
STRUCTURAL 1 5 1 37 0/7432-0/7439 <inode_list>
STRUCTURAL 1 5 1 37 0/16-0/23 <inode_list>
STRUCTURAL 1 6 - - 0/15 <current_usage_tbl>
UNNAMED 999 25 - - 2/80-2/84 /exec.h
UNNAMED 999 26 - - 2/86-2/87 /exechdr.h
- - - - - 0/6808 <free>
- - - - - 0/6823-0/6975 <free>
List the files in the Storage Checkpoint named on the device
Report all inodes and file system structures referencing any sector in
the device with devid 2 in the file system
When the file system structure is not correct, 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.
SEE ALSOsort(1), fsckptadm(1M), fsck_vxfs(1M), ncheck(1M), fs_vxfs(4).