|
|
HP-UX Reference > Nncheck_vxfs(1M)HP-UX 11i Version 2: December 2007 Update |
|
NAMEncheck_vxfs: ncheck — generate pathnames from inode numbers for a VxFS file system SYNOPSISncheck [-a] [-F vxfs] [-i ilist] [-o specific_options] [-s] [-S sector_list] [-V] special ... DESCRIPTIONncheck generates a list of pathnames 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 the range is a single number, the output will refer to the single sector, block, or surface specified by that number. 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 (/.). Optionsncheck_vxfs recogizes the following options:
EXAMPLESReport on all inodes or file system structures containing or referencing sector 20 through 35 (inclusive) in the file system /dev/vg01/rlvol1: ncheck -F vxfs -osector=20-35 /dev/vg01/rlvol1 Same as above but report on all inodes or file system structures referencing any sector in the file system /dev/vg01/rlvol1: ncheck -F vxfs -osector= /dev/vg01/rlvol1 Report on a specified range of block numbers (partial output shown): ncheck -F vxfs -oblock=- /dev/vg00/lvol6 /dev/vg00/lvol6: sectors(348160) blocks(348160) ----------------- ----------------- 0-348159 0-348159 fileset fset mtch match name indx inode indx inode blocks name ---------- ---- ------ ---- ------ ------------- ------------------ STRUCTURAL 1 3 - 35 9-10 <fileset_header> STRUCTURAL 1 4 1 - 11-14 <inode_alloc_unit> STRUCTURAL 1 5 1 37 1296-1303 <inode_list> STRUCTURAL 1 5 1 37 24-31 <inode_list> STRUCTURAL 1 5 1 37 1288-1295 <inode_list> STRUCTURAL 1 5 1 37 16-23 <inode_list> STRUCTURAL 1 6 - - 15 <current_usage_tbl> STRUCTURAL 1 7 - 39 33 <object_loc_tbl> STRUCTURAL 1 8 - 40 34 <device_config> STRUCTURAL 1 9 - 41 40-1063 <intent_log> STRUCTURAL 1 10 - 42 1144-1151 <extent_map> STRUCTURAL 1 10 - 42 1072-1143 <extent_map> STRUCTURAL 1 10 - 42 1064-1071 <extent_map> STRUCTURAL 1 32 - - 32 <state_alloc_bitmap> STRUCTURAL 1 33 - - 1284 <device_label> STRUCTURAL 1 33 - - 0-8 <device_label> STRUCTURAL 1 34 - - 35 <extent_au_summary> STRUCTURAL 1 35 - 3 1280-1281 <fileset_header> STRUCTURAL 1 37 1 5 1296-1303 <inode_list> STRUCTURAL 1 37 1 5 24-31 <inode_list> STRUCTURAL 1 37 1 5 1288-1295 <inode_list> STRUCTURAL 1 37 1 5 16-23 <inode_list> STRUCTURAL 1 39 - 7 1282 <object_loc_tbl> STRUCTURAL 1 40 - 8 1283 <device_config> STRUCTURAL 1 41 - 9 40-1063 <intent_log> STRUCTURAL 1 42 - 10 1144-1151 <extent_map> STRUCTURAL 1 42 - 10 1072-1143 <extent_map> STRUCTURAL 1 42 - 10 1064-1071 <extent_map> STRUCTURAL 1 64 999 - 36-39 <inode_alloc_unit> STRUCTURAL 1 65 999 97 59072-59135 <inode_list> STRUCTURAL 1 65 999 97 1152-1159 <inode_list> STRUCTURAL 1 69 999 - 1160-1167 <bsd_quota> STRUCTURAL 1 97 999 65 59072-59135 <inode_list> STRUCTURAL 1 97 999 65 1152-1159 <inode_list> UNNAMED 999 96 - - 4861 /file1 UNNAMED 999 1807 - - 344387 /file1000 UNNAMED 999 1822 - - 328082 /file2 - - - - - 19766-19769 <free> - - - - - 347192-347194 <free> DIAGNOSTICSWhen the file system structure is not correct, ncheck prints ??? to denote the ``parent'' of a parentless file. A pathname beginning with ... denotes a loop. A pathname beginning with *** denotes a directory entry whose .. (dotdot) entry does not correspond with the directory in which it was found. |
|