| 1 | .TH mmunlinkfileset 04/06/06 |
|---|
| 2 | mmunlinkfileset Command |
|---|
| 3 | .SH "Name" |
|---|
| 4 | .PP |
|---|
| 5 | \fBmmunlinkfileset\fR - Removes the junction to the a GPFS |
|---|
| 6 | fileset. |
|---|
| 7 | .SH "Synopsis" |
|---|
| 8 | .PP |
|---|
| 9 | \fBmmunlinkfileset\fR \fIDevice\fR {\fIFilesetName\fR | |
|---|
| 10 | \fB-J\fR \fIJunctionPath\fR} \fB[-f]\fR |
|---|
| 11 | .SH "Description" |
|---|
| 12 | .PP |
|---|
| 13 | The \fBmmunlinkfileset\fR command removes the junction to the |
|---|
| 14 | fileset. The junction can be specified by path or by naming the fileset |
|---|
| 15 | that is its target. The unlink fails if there are files open in the |
|---|
| 16 | fileset, unless the \fB-f \fR flag is specified. The root fileset |
|---|
| 17 | may not be unlinked. |
|---|
| 18 | .PP |
|---|
| 19 | \fBAttention:\fR If you are using the TSM Backup Archive client you |
|---|
| 20 | must use caution when you unlink filesets that contain data backed up by |
|---|
| 21 | TSM. TSM tracks files by pathname and does not track filesets. |
|---|
| 22 | As a result, when you unlink a fileset, it appears to TSM that you deleted the |
|---|
| 23 | contents of the fileset. Therefore, the TSM Backup Archive client |
|---|
| 24 | inactivates the data on the TSM server which may result in the loss of backup |
|---|
| 25 | data during the expiration process. |
|---|
| 26 | .PP |
|---|
| 27 | For information on GPFS filesets, see the chapter |
|---|
| 28 | \fIPolicy-based data management for |
|---|
| 29 | GPFS\fR in |
|---|
| 30 | \fIGeneral Parallel File |
|---|
| 31 | System: Advanced Administration Guide\fR. |
|---|
| 32 | .SH "Parameters" |
|---|
| 33 | .PP |
|---|
| 34 | .RS +3 |
|---|
| 35 | \fB\fIDevice\fR |
|---|
| 36 | \fR |
|---|
| 37 | .RE |
|---|
| 38 | .RS +9 |
|---|
| 39 | The device name of the file system that contains the fileset. |
|---|
| 40 | .PP |
|---|
| 41 | File system names need not be fully-qualified. \fBfs0\fR is as |
|---|
| 42 | acceptable as \fB/dev/fs0\fR. |
|---|
| 43 | .RE |
|---|
| 44 | .PP |
|---|
| 45 | .RS +3 |
|---|
| 46 | \fB\fIFilesetName\fR |
|---|
| 47 | \fR |
|---|
| 48 | .RE |
|---|
| 49 | .RS +9 |
|---|
| 50 | Specifies the name of the fileset to be removed. |
|---|
| 51 | .RE |
|---|
| 52 | .PP |
|---|
| 53 | .RS +3 |
|---|
| 54 | \fB-J \fIJunctionPath\fR |
|---|
| 55 | \fR |
|---|
| 56 | .RE |
|---|
| 57 | .RS +9 |
|---|
| 58 | Specifies the name of the junction to be removed. |
|---|
| 59 | .PP |
|---|
| 60 | A junction is a special directory entry that connects a name in a directory |
|---|
| 61 | of one fileset to the root directory of another fileset. |
|---|
| 62 | .RE |
|---|
| 63 | .SH "Options" |
|---|
| 64 | .PP |
|---|
| 65 | .RS +3 |
|---|
| 66 | \fB-f |
|---|
| 67 | \fR |
|---|
| 68 | .RE |
|---|
| 69 | .RS +9 |
|---|
| 70 | Forces the unlink to take place even though there may be open |
|---|
| 71 | files. This option forcibly closes any open files, causing an |
|---|
| 72 | \fBerrno\fR of \fBESTALE\fR on their next use of the file. |
|---|
| 73 | .RE |
|---|
| 74 | .SH "Exit status" |
|---|
| 75 | .PP |
|---|
| 76 | .PP |
|---|
| 77 | .RS +3 |
|---|
| 78 | \fB0 |
|---|
| 79 | \fR |
|---|
| 80 | .RE |
|---|
| 81 | .RS +9 |
|---|
| 82 | Successful completion. |
|---|
| 83 | .RE |
|---|
| 84 | .PP |
|---|
| 85 | .RS +3 |
|---|
| 86 | \fBnonzero |
|---|
| 87 | \fR |
|---|
| 88 | .RE |
|---|
| 89 | .RS +9 |
|---|
| 90 | A failure has occurred. |
|---|
| 91 | .RE |
|---|
| 92 | .SH "Security" |
|---|
| 93 | .PP |
|---|
| 94 | You must have root authority to run the \fBmmunlinkfileset\fR |
|---|
| 95 | command. |
|---|
| 96 | .PP |
|---|
| 97 | You may issue the \fBmmunlinkfileset\fR command from any node in the |
|---|
| 98 | GPFS cluster. |
|---|
| 99 | .PP |
|---|
| 100 | When using the \fBrcp\fR and \fBrsh\fR commands for remote |
|---|
| 101 | communication, a properly configured \fB.rhosts\fR file must exist |
|---|
| 102 | in the root user's home directory on each node in the GPFS |
|---|
| 103 | cluster. If you have designated the use of a different remote |
|---|
| 104 | communication program on either the |
|---|
| 105 | \fBmmcrcluster\fR |
|---|
| 106 | or the |
|---|
| 107 | \fBmmchcluster\fR command, you must |
|---|
| 108 | ensure: |
|---|
| 109 | .RS +3 |
|---|
| 110 | .HP 3 |
|---|
| 111 | 1. Proper authorization is granted to all nodes in the GPFS cluster. |
|---|
| 112 | .HP 3 |
|---|
| 113 | 2. The nodes in the GPFS cluster can communicate without the use of a |
|---|
| 114 | password, and without any extraneous messages. |
|---|
| 115 | .RE |
|---|
| 116 | .SH "Examples" |
|---|
| 117 | .RS +3 |
|---|
| 118 | .HP 3 |
|---|
| 119 | 1. This command indicates the current configuration of filesets for file |
|---|
| 120 | system \fBgpfs1\fR: |
|---|
| 121 | .sp |
|---|
| 122 | .nf |
|---|
| 123 | mmlsfileset gpfs1 |
|---|
| 124 | .fi |
|---|
| 125 | .sp |
|---|
| 126 | The system displays output similar to: |
|---|
| 127 | .sp |
|---|
| 128 | .nf |
|---|
| 129 | Filesets in file system 'gpfs1': |
|---|
| 130 | Name Status Path\ |
|---|
| 131 | root Linked /gpfs1\ |
|---|
| 132 | fset1 Linked /gpfs1/fset |
|---|
| 133 | .fi |
|---|
| 134 | .sp |
|---|
| 135 | .sp |
|---|
| 136 | This command unlinks fileset \fBfset1\fR from file system |
|---|
| 137 | \fBgpfs1\fR: |
|---|
| 138 | .sp |
|---|
| 139 | .nf |
|---|
| 140 | mmunlinkfileset gpfs1 fset1 |
|---|
| 141 | .fi |
|---|
| 142 | .sp |
|---|
| 143 | .sp |
|---|
| 144 | The system displays output similar to: |
|---|
| 145 | .sp |
|---|
| 146 | .nf |
|---|
| 147 | Fileset 'fset1' unlinked. |
|---|
| 148 | .fi |
|---|
| 149 | .sp |
|---|
| 150 | .sp |
|---|
| 151 | To confirm the change, issue this command: |
|---|
| 152 | .sp |
|---|
| 153 | .nf |
|---|
| 154 | mmlsfileset gpfs1 |
|---|
| 155 | .fi |
|---|
| 156 | .sp |
|---|
| 157 | .sp |
|---|
| 158 | The system displays output similar to: |
|---|
| 159 | .sp |
|---|
| 160 | .nf |
|---|
| 161 | Filesets in file system 'gpfs1': |
|---|
| 162 | Name Status Path\ |
|---|
| 163 | root Linked /gpfs1\ |
|---|
| 164 | fset1 Unlinked -- |
|---|
| 165 | .fi |
|---|
| 166 | .sp |
|---|
| 167 | .HP 3 |
|---|
| 168 | 2. This command indicates the current configuration of filesets for file |
|---|
| 169 | system \fBgpfs1\fR: |
|---|
| 170 | .sp |
|---|
| 171 | .nf |
|---|
| 172 | mmlsfileset gpfs1 |
|---|
| 173 | .fi |
|---|
| 174 | .sp |
|---|
| 175 | The system displays output similar to: |
|---|
| 176 | .sp |
|---|
| 177 | .nf |
|---|
| 178 | Filesets in file system 'gpfs1': |
|---|
| 179 | Name Status Path\ |
|---|
| 180 | root Linked /gpfs1\ |
|---|
| 181 | fset1 Linked /gpfs1/fset1 |
|---|
| 182 | .fi |
|---|
| 183 | .sp |
|---|
| 184 | .sp |
|---|
| 185 | This command unlinks junction path \fB/gpfs1/fset1\fR from file system |
|---|
| 186 | \fBgpfs1\fR: |
|---|
| 187 | .sp |
|---|
| 188 | .nf |
|---|
| 189 | mmunlinkfileset gpfs1 -J /gpfs1/fset1 |
|---|
| 190 | .fi |
|---|
| 191 | .sp |
|---|
| 192 | .sp |
|---|
| 193 | The system displays output similar to: |
|---|
| 194 | .sp |
|---|
| 195 | .nf |
|---|
| 196 | Fileset 'fset1' unlinked. |
|---|
| 197 | .fi |
|---|
| 198 | .sp |
|---|
| 199 | .sp |
|---|
| 200 | To confirm the change, issue this command: |
|---|
| 201 | .sp |
|---|
| 202 | .nf |
|---|
| 203 | mmlsfileset gpfs1 |
|---|
| 204 | .fi |
|---|
| 205 | .sp |
|---|
| 206 | .sp |
|---|
| 207 | The system displays output similar to: |
|---|
| 208 | .sp |
|---|
| 209 | .nf |
|---|
| 210 | Filesets in file system 'gpfs1': |
|---|
| 211 | Name Status Path\ |
|---|
| 212 | root Linked /gpfs1\ |
|---|
| 213 | fset1 Unlinked -- |
|---|
| 214 | .fi |
|---|
| 215 | .sp |
|---|
| 216 | .RE |
|---|
| 217 | .SH "See also" |
|---|
| 218 | .PP |
|---|
| 219 | mmchfileset Command |
|---|
| 220 | .PP |
|---|
| 221 | mmcrfileset Command |
|---|
| 222 | .PP |
|---|
| 223 | mmdelfileset Command |
|---|
| 224 | .PP |
|---|
| 225 | mmlinkfileset Command |
|---|
| 226 | .PP |
|---|
| 227 | mmlsfileset Command |
|---|
| 228 | .SH "Location" |
|---|
| 229 | .PP |
|---|
| 230 | \fB/usr/lpp/mmfs/bin\fR |
|---|