[16] | 1 | .TH mmlinkfileset 02/16/06 |
---|
| 2 | mmlinkfileset Command |
---|
| 3 | .SH "Name" |
---|
| 4 | .PP |
---|
| 5 | \fBmmlinkfileset\fR - Creates a junction that references the root |
---|
| 6 | directory of a GPFS fileset. |
---|
| 7 | .SH "Synopsis" |
---|
| 8 | .PP |
---|
| 9 | \fBmmlinkfileset\fR \fIDevice\fR \fIFilesetName\fR |
---|
| 10 | \fB[-J\fR \fIJunctionPath\fR\fB]\fR |
---|
| 11 | .SH "Description" |
---|
| 12 | .PP |
---|
| 13 | The \fBmmlinkfileset\fR command creates a junction at |
---|
| 14 | \fIJunctionPath\fR that references the root directory of |
---|
| 15 | \fIFilesetName\fR. The junction is a special directory entry, much |
---|
| 16 | like a POSIX hard link, that connects a name in a directory of one fileset, |
---|
| 17 | the parent, to the root directory of a child fileset. From the |
---|
| 18 | user's viewpoint, a junction always appears as if it were a directory, |
---|
| 19 | but the user is not allowed to issue the \fBunlink\fR or \fBrmdir\fR |
---|
| 20 | commands on a junction. Instead, the |
---|
| 21 | \fBmmunlinkfileset\fR command must |
---|
| 22 | be used to remove a junction. |
---|
| 23 | .PP |
---|
| 24 | If \fIJunctionPath\fR is not specified, the junction is created in the |
---|
| 25 | current directory with the name \fIFilesetName\fR. The user may use |
---|
| 26 | the \fBmv\fR command on the directory to move to a new location in the |
---|
| 27 | parent fileset, but the \fBmv\fR command is not allowed to move the |
---|
| 28 | junction to a different fileset. |
---|
| 29 | .PP |
---|
| 30 | For information on GPFS filesets, see the chapter |
---|
| 31 | \fIPolicy-based data management for |
---|
| 32 | GPFS\fR in |
---|
| 33 | \fIGeneral Parallel File |
---|
| 34 | System: Advanced Administration Guide\fR. |
---|
| 35 | .SH "Parameters" |
---|
| 36 | .PP |
---|
| 37 | .RS +3 |
---|
| 38 | \fB\fIDevice\fR |
---|
| 39 | \fR |
---|
| 40 | .RE |
---|
| 41 | .RS +9 |
---|
| 42 | The device name of the file system that contains the fileset. |
---|
| 43 | .PP |
---|
| 44 | File system names need not be fully-qualified. \fBfs0\fR is as |
---|
| 45 | acceptable as \fB/dev/fs0\fR. |
---|
| 46 | .RE |
---|
| 47 | .PP |
---|
| 48 | .RS +3 |
---|
| 49 | \fB\fIFilesetName\fR |
---|
| 50 | \fR |
---|
| 51 | .RE |
---|
| 52 | .RS +9 |
---|
| 53 | Specifies the name of the fileset to be linked. It must not already |
---|
| 54 | be linked into the namespace. |
---|
| 55 | .RE |
---|
| 56 | .PP |
---|
| 57 | .RS +3 |
---|
| 58 | \fB-J \fIJunctionPath\fR |
---|
| 59 | \fR |
---|
| 60 | .RE |
---|
| 61 | .RS +9 |
---|
| 62 | Specifies the name of the junction. The name must not already |
---|
| 63 | exist, and must not already be linked into the namespace. The name must |
---|
| 64 | not already exist, and must not already be linked into the namespace. |
---|
| 65 | .PP |
---|
| 66 | A junction is a special directory entry that connects a name in a directory |
---|
| 67 | of one fileset to the root directory of another fileset. |
---|
| 68 | .RE |
---|
| 69 | .SH "Exit status" |
---|
| 70 | .PP |
---|
| 71 | .PP |
---|
| 72 | .RS +3 |
---|
| 73 | \fB0 |
---|
| 74 | \fR |
---|
| 75 | .RE |
---|
| 76 | .RS +9 |
---|
| 77 | Successful completion. |
---|
| 78 | .RE |
---|
| 79 | .PP |
---|
| 80 | .RS +3 |
---|
| 81 | \fBnonzero |
---|
| 82 | \fR |
---|
| 83 | .RE |
---|
| 84 | .RS +9 |
---|
| 85 | A failure has occurred. |
---|
| 86 | .RE |
---|
| 87 | .SH "Security" |
---|
| 88 | .PP |
---|
| 89 | You must have root authority to run the \fBmmlinkfileset\fR |
---|
| 90 | command. |
---|
| 91 | .PP |
---|
| 92 | You may issue the \fBmmlinkfileset\fR command from any node in the GPFS |
---|
| 93 | cluster. |
---|
| 94 | .PP |
---|
| 95 | When using the \fBrcp\fR and \fBrsh\fR commands for remote |
---|
| 96 | communication, a properly configured \fB.rhosts\fR file must exist |
---|
| 97 | in the root user's home directory on each node in the GPFS |
---|
| 98 | cluster. If you have designated the use of a different remote |
---|
| 99 | communication program on either the |
---|
| 100 | \fBmmcrcluster\fR |
---|
| 101 | or the |
---|
| 102 | \fBmmchcluster\fR command, you must |
---|
| 103 | ensure: |
---|
| 104 | .RS +3 |
---|
| 105 | .HP 3 |
---|
| 106 | 1. Proper authorization is granted to all nodes in the GPFS cluster. |
---|
| 107 | .HP 3 |
---|
| 108 | 2. The nodes in the GPFS cluster can communicate without the use of a |
---|
| 109 | password, and without any extraneous messages. |
---|
| 110 | .RE |
---|
| 111 | .SH "Examples" |
---|
| 112 | .PP |
---|
| 113 | This command links fileset \fBfset1\fR in file system \fBgpfs1\fR to |
---|
| 114 | junction path \fB/gpfs1/fset1\fR: |
---|
| 115 | .sp |
---|
| 116 | .nf |
---|
| 117 | mmlinkfileset gpfs1 fset1 -J /gpfs1/fset1 |
---|
| 118 | .fi |
---|
| 119 | .sp |
---|
| 120 | .PP |
---|
| 121 | The system displays output similar to: |
---|
| 122 | .sp |
---|
| 123 | .nf |
---|
| 124 | Fileset 'fset1' linked at '/gpfs1/fset1'. |
---|
| 125 | .fi |
---|
| 126 | .sp |
---|
| 127 | .PP |
---|
| 128 | To confirm the change, issue this command: |
---|
| 129 | .sp |
---|
| 130 | .nf |
---|
| 131 | mmlsfileset gpfs1 |
---|
| 132 | .fi |
---|
| 133 | .sp |
---|
| 134 | .PP |
---|
| 135 | The system displays output similar to: |
---|
| 136 | .sp |
---|
| 137 | .nf |
---|
| 138 | Filesets in file system 'gpfs1': |
---|
| 139 | Name Status Path\ |
---|
| 140 | root Linked /gpfs1\ |
---|
| 141 | fset1 Linked /gpfs1/fset1 |
---|
| 142 | .fi |
---|
| 143 | .sp |
---|
| 144 | .SH "See also" |
---|
| 145 | .PP |
---|
| 146 | mmchfileset Command |
---|
| 147 | .PP |
---|
| 148 | mmcrfileset Command |
---|
| 149 | .PP |
---|
| 150 | mmdelfileset Command |
---|
| 151 | .PP |
---|
| 152 | mmlsfileset Command |
---|
| 153 | .PP |
---|
| 154 | mmunlinkfileset Command |
---|
| 155 | .SH "Location" |
---|
| 156 | .PP |
---|
| 157 | \fB/usr/lpp/mmfs/bin\fR |
---|
| 158 | .PP |
---|