| [16] | 1 | .TH mmdelsnapshot 02/16/06 |
|---|
| 2 | mmdelsnapshot Command |
|---|
| 3 | .SH "Name" |
|---|
| 4 | .PP |
|---|
| 5 | \fBmmdelsnapshot\fR - Deletes a GPFS snapshot. |
|---|
| 6 | .SH "Synopsis" |
|---|
| 7 | .PP |
|---|
| 8 | \fBmmdelsnapshot\fR \fIDevice\fR \fIDirectory\fR |
|---|
| 9 | .SH "Description" |
|---|
| 10 | .PP |
|---|
| 11 | Use the \fBmmdelsnapshot\fR command to delete a GPFS snapshot. |
|---|
| 12 | .PP |
|---|
| 13 | Once the \fBmmdelsnapshot\fR command has been issued, the snapshot is |
|---|
| 14 | marked for deletion and cannot be recovered. |
|---|
| 15 | .PP |
|---|
| 16 | If the node from which the \fBmmdelsnapshot\fR command is issued fails, |
|---|
| 17 | you must reissue the command from another node in the cluster to complete the |
|---|
| 18 | deletion. Prior to reissuing a subsequent \fBmmdelsnapshot\fR |
|---|
| 19 | command, the file system may be recovered, mounted, and updates may continue |
|---|
| 20 | to be made and the |
|---|
| 21 | \fBmmcrsnapshot\fR command may be |
|---|
| 22 | issued. However, the |
|---|
| 23 | \fBmmrestorefs\fR and |
|---|
| 24 | \fBmmdelsnapshot\fR commands may not be issued on other snapshots until the |
|---|
| 25 | present snapshot is successfully deleted. |
|---|
| 26 | .PP |
|---|
| 27 | If the \fBmmdelsnapshot\fR command is issued while a conflicting command |
|---|
| 28 | is running, the \fBmmdelsnapshot\fR command waits for that command to |
|---|
| 29 | complete. Conflicting operations include: |
|---|
| 30 | .RS +3 |
|---|
| 31 | .HP 3 |
|---|
| 32 | 1. Other snapshot commands on the same snapshot |
|---|
| 33 | .HP 3 |
|---|
| 34 | 2. Adding, deleting, replacing disks in the file system |
|---|
| 35 | .HP 3 |
|---|
| 36 | 3. Rebalancing, repairing, reducing disk fragmentation in a file system |
|---|
| 37 | .RE |
|---|
| 38 | .PP |
|---|
| 39 | Any files open in the snapshot will be forcibly closed. The |
|---|
| 40 | user will receive an \fBerrno\fR of \fBESTALE\fR on the next file |
|---|
| 41 | access. |
|---|
| 42 | .SH "Parameters" |
|---|
| 43 | .PP |
|---|
| 44 | .RS +3 |
|---|
| 45 | \fB\fIDevice\fR |
|---|
| 46 | \fR |
|---|
| 47 | .RE |
|---|
| 48 | .RS +9 |
|---|
| 49 | The device name of the file system for which the snapshot is to be |
|---|
| 50 | deleted. File system names need not be fully-qualified. |
|---|
| 51 | \fBfs0\fR is just as acceptable as \fB/dev/fs0\fR. |
|---|
| 52 | .PP |
|---|
| 53 | This must be the first parameter. |
|---|
| 54 | .RE |
|---|
| 55 | .PP |
|---|
| 56 | .RS +3 |
|---|
| 57 | \fB\fIDirectory\fR |
|---|
| 58 | \fR |
|---|
| 59 | .RE |
|---|
| 60 | .RS +9 |
|---|
| 61 | The snapshot subdirectory to be deleted. |
|---|
| 62 | .RE |
|---|
| 63 | .SH "Options" |
|---|
| 64 | .PP |
|---|
| 65 | NONE |
|---|
| 66 | .SH "Exit status" |
|---|
| 67 | .PP |
|---|
| 68 | .PP |
|---|
| 69 | .RS +3 |
|---|
| 70 | \fB0 |
|---|
| 71 | \fR |
|---|
| 72 | .RE |
|---|
| 73 | .RS +9 |
|---|
| 74 | Successful completion. |
|---|
| 75 | .RE |
|---|
| 76 | .PP |
|---|
| 77 | .RS +3 |
|---|
| 78 | \fBnonzero |
|---|
| 79 | \fR |
|---|
| 80 | .RE |
|---|
| 81 | .RS +9 |
|---|
| 82 | A failure has occurred. |
|---|
| 83 | .RE |
|---|
| 84 | .SH "Security" |
|---|
| 85 | .PP |
|---|
| 86 | You must have root authority to run the \fBmmdelsnapshot\fR |
|---|
| 87 | command. |
|---|
| 88 | .PP |
|---|
| 89 | You may issue the \fBmmdelsnapshot\fR command from any node in the GPFS |
|---|
| 90 | cluster. |
|---|
| 91 | .PP |
|---|
| 92 | When using the \fBrcp\fR and \fBrsh\fR commands for remote |
|---|
| 93 | communication, a properly configured \fB.rhosts\fR file must exist |
|---|
| 94 | in the root user's home directory on each node in the GPFS |
|---|
| 95 | cluster. If you have designated the use of a different remote |
|---|
| 96 | communication program on either the |
|---|
| 97 | \fBmmcrcluster\fR |
|---|
| 98 | or the |
|---|
| 99 | \fBmmchcluster\fR command, you must |
|---|
| 100 | ensure: |
|---|
| 101 | .RS +3 |
|---|
| 102 | .HP 3 |
|---|
| 103 | 1. Proper authorization is granted to all nodes in the GPFS cluster. |
|---|
| 104 | .HP 3 |
|---|
| 105 | 2. The nodes in the GPFS cluster can communicate without the use of a |
|---|
| 106 | password, and without any extraneous messages. |
|---|
| 107 | .RE |
|---|
| 108 | .SH "Examples" |
|---|
| 109 | .PP |
|---|
| 110 | To delete the snapshot \fBsnap1\fR, for the file system \fBfs1\fR, |
|---|
| 111 | issue this command: |
|---|
| 112 | .sp |
|---|
| 113 | .nf |
|---|
| 114 | mmdelsnapshot fs1 snap1 |
|---|
| 115 | .fi |
|---|
| 116 | .sp |
|---|
| 117 | .PP |
|---|
| 118 | The output is similar to this: |
|---|
| 119 | .sp |
|---|
| 120 | .nf |
|---|
| 121 | Deleting snapshot files... |
|---|
| 122 | Delete snapshot snap1 complete, err = 0 |
|---|
| 123 | .fi |
|---|
| 124 | .sp |
|---|
| 125 | .PP |
|---|
| 126 | Before issuing the command, the directory structure would appear similar |
|---|
| 127 | to: |
|---|
| 128 | .sp |
|---|
| 129 | .nf |
|---|
| 130 | /fs1/file1 |
|---|
| 131 | /fs1/userA/file2 |
|---|
| 132 | /fs1/userA/file3 |
|---|
| 133 | /fs1/.snapshots/snap1/file1 |
|---|
| 134 | /fs1/.snapshots/snap1/userA/file2 |
|---|
| 135 | /fs1/.snapshots/snap1/userA/file3 |
|---|
| 136 | .fi |
|---|
| 137 | .sp |
|---|
| 138 | .PP |
|---|
| 139 | After the command has been issued, the directory structure would appear |
|---|
| 140 | similar to: |
|---|
| 141 | .sp |
|---|
| 142 | .nf |
|---|
| 143 | /fs1/file1 |
|---|
| 144 | /fs1/userA/file2 |
|---|
| 145 | /fs1/userA/file3 |
|---|
| 146 | /fs1/.snapshots |
|---|
| 147 | .fi |
|---|
| 148 | .sp |
|---|
| 149 | .SH "See also" |
|---|
| 150 | .PP |
|---|
| 151 | mmcrsnapshot Command |
|---|
| 152 | .PP |
|---|
| 153 | mmlssnapshot Command |
|---|
| 154 | .PP |
|---|
| 155 | mmrestorefs Command |
|---|
| 156 | .PP |
|---|
| 157 | mmsnapdir Command |
|---|
| 158 | .SH "Location" |
|---|
| 159 | .PP |
|---|
| 160 | \fB/usr/lpp/mmfs/bin\fR |
|---|
| 161 | .PP |
|---|
