.TH mmfileid 03/02/06 mmfileid Command .SH "Name" .PP \fBmmfileid\fR - Determines which files are located on areas of a disk that are damaged or considered to be suspect. .PP \fBAttention:\fR Use this command only when directed by the IBM Support Center. .PP \fB Synopsis\fR .PP \fBmmfileid\fR \fIDevice\fR {\fB -d\fR [\fINodeName\fR]:{\fIDiskName\fR|\fIDiskNum\fR|\fB BROKEN\fR}:[\fIPhysAddr1\fR[-\fIPhysAddr2\fR]] | \fB -F\fR \fIDescFile\fR} [\fB-o\fR \fIOutputFile\fR] [\fB-f\fR \fINumThreads\fR] [\fB-t\fR \fIDirectory \fR] .PP \fBDescription\fR .PP Use the \fBmmfileid\fR command to determine which files are located on areas of a disk that are damaged or considered to be suspect. Before running \fBmmfileid\fR, the user must run a disk analysis utility and obtain the disk sector numbers that are suspect or known to be damaged. These sectors are input to the \fBmmfileid\fR command. To run the \fBmmfileid\fR command, you must specify the physical volume name of the disk, the GPFS disk ID number, or the keyword \fBBROKEN\fR to find all files with broken addresses resulting in the loss of data. The output of the command is a list of inodes and names of files that are located on the input disk sectors. .PP The output can be redirected to a file (using the \fB-o\fR flag) and sorted on the inode number, using the \fBsort\fR command. The \fBmmfileid\fR command output contains one line for each inode found to be located on the corrupt disk sector. The file name is relative to the root of the file system in which it resides. The command output has this format: .sp .nf inode_number Logical_Disk_Address snapshotid filename .fi .sp .PP Only one instance of \fBmmfileid\fR may be active on a GPFS cluster at any given time. The \fBmmfileid\fR command will not work for a file system owned and controlled by another GPFS cluster. .PP \fB Parameters\fR .PP .RS +3 \fB\fIDevice\fR\fR .RE .RS +9 The device name for the file system on which this utility is to be run. This must be the first parameter and is required. .RE .PP .RS +3 \fB\fB-d\fR [\fINodeName\fR]:{\fIDiskName\fR|\fI DiskNum\fR|\fBBROKEN\fR}:[\fIPhysAddr1\fR[-\fIPhysAddr2 \fR]] .PP \fR .RE .RS +9 .PP .RS +3 \fB\fINodeName\fR\fR .RE .RS +9 Specifies a node in the GPFS cluster that has access to the disk in question. .RE .PP .RS +3 \fB\fIDiskName\fR\fR .RE .RS +9 Specifies the physical volume name of the disk. .RE .PP .RS +3 \fB\fIDiskNum\fR\fR .RE .RS +9 Specifies the GPFS disk ID number of the disk as currently displayed by the \fBmmlsdisk -L\fR command. .RE .PP .RS +3 \fBBROKEN\fR .RE .RS +9 Specifies to find all files that have broken addresses resulting in lost data. .RE .PP .RS +3 \fB\fIPhysAddr1\fR[-\fIPhysAddr2\fR]\fR .RE .RS +9 Specified the range of physical disk addresses, as reported by the error logging utility, for the disk that has encountered a failure. The default value for \fIPhysAddr1\fR is zero. The default value for \fIPhysAddr2\fR is the value for \fIPhysAddr1\fR. .PP If both \fIPhysAddr1\fR and \fI PhysAddr2\fR are zero, the entire disk is searched. .RE .RE .PP .RS +3 \fB-F \fIDescFile\fR\fR .RE .RS +9 Specifies a file containing a list of disks and corresponding disk addresses, for the file system on which the \fBmmfileid\fR command is to be run. The file uses the same conventions as the \fB-d\fR option. .PP The format of the file is: .sp .nf #optional comment line nodename1:hdisk1:PhysAddr1-PhysAddr2 nodename1:hdisk1:PhysAddr3-PhysAddr4 nodename3:hdisk2:PhysAddr1-PhysAddr2 nodename1:hdiskn:PhysAddr1-PhysAddr2 .fi .sp .PP For example: .sp .nf :gpfs1nsd :10:27645856 :BROKEN .fi .sp .RE .PP .RS +3 \fB-f \fINumThreads\fR\fR .RE .RS +9 Specifies the number of worker threads that are to be created by the \fB mmfileid\fR command. .PP The default is value 16. The minimum value is 1. If \fInumThreads\fR is less than 2, only the main process performs work. The maximum value can be as large as is allowed by the operating system \fB pthread_create\fR function for a single process. A suggested value is twice the number of disks in the file system. If an error occurs creating a worker thread, \fBmmfileid\fR exits with an error. .RE .PP .RS +3 \fB-o \fIOutputFile\fR\fR .RE .RS +9 Specifies the name of a file for the \fBmmfileid\fR command to write its output. If not specified, output is sent to standard output. .RE .PP .RS +3 \fB-t \fIDirectory\fR\fR .RE .RS +9 Specifies the directory to use for the \fBmmfileid\fR temporary files and the sort program intermediate files. The default directory is \fB /tmp\fR. .RE .PP \fBExit status\fR .PP .PP .RS +3 \fB0\fR .RE .RS +9 Successful completion. .RE .PP .RS +3 \fBnonzero\fR .RE .RS +9 A failure has occurred. .RE .PP \fBSecurity\fR .PP You must have root authority to run the \fBmmfileid\fR command. .PP This command must be invoked on a file system that is not running an excessive number of reads and writes. Excessive file system activity will produce incorrect results. .PP \fB Examples\fR .PP Assume that a disk analysis tool reported that \fB hdisk6\fR, \fBhdisk7\fR, \fBhdisk8\fR, and \fB hdisk9\fR contained bad sectors. This command: .sp .nf mmfileid /dev/gpfsB -F addr.in .fi .sp .PP where \fBaddr.in\fR contains this: .sp .nf k148n07:hdisk9:2206310-2206810 k148n07:hdisk8:2211038-2211042 k148n07:hdisk8:2201800-2202800 k148n01:hdisk6:2921879-2926880 k148n09:hdisk7:1076208-1076610 .fi .sp .PP produces output similar to this: .sp .nf Address 2201958 is contained in the Block allocation map (inode 1) Address 2206688 is contained in the ACL Data file (inode 4, snapId 0) Address 2211038 is contained in the Log File (inode 7, snapId 0) 14336 1076256 0 /gpfsB/tesDir/testFile.out 14344 2922528 1 /gpfsB/x.img .fi .sp .PP The lines starting with Address are special GPFS files. If your output contains any of these lines, \fBdo not\fR attempt to replace or repair the indicated files. Call the IBM Support Center for assistance. This output indicates that files \fB/gpfsB/tesDir/testFile.out\fR and \fB /gpfsB/x.img\fR are located on bad sector areas. .PP The format for each line of output is as follows: .sp .nf inode_number Logical_Disk_Address snapshotid filename .fi .sp .PP \fBSee also\fR .PP The section on \fIDisk media failure\fR in \fIGeneral Parallel File System: Problem Determination Guide\fR. .PP \fBLocation\fR .PP \fB