|
|
|
| Chapter 6 Managing the File System | |
|
|
|
| Performing a Metadata Dump | |
|
|
| 10 Mount the file system as described in Mounting or Unmounting a | ||
|
|
|
| File System on page 108. | |
|
| When using affinities, the StorNext administrator must adhere to the file | |||
| File System |
| |||
Configuration |
| system configuration restrictions listed below to ensure that data | |||
Restrictions |
| management policies execute properly. These restrictions apply only to | |||
|
|
| managed file systems, not to | ||
|
| ||||
|
|
|
| • Taking into account all managed file systems, you cannot use more | |
|
|
|
| than two unique affinity names. However, these two affinity names | |
|
|
|
| can be | |
|
|
|
| • All data stripe groups must have exactly one affinity association, but | |
|
|
|
| several stripe groups can be associated to the same affinity. This | |
|
|
|
| restriction does not apply to exclusive metadata or journal stripe | |
|
|
|
| groups. | |
|
|
|
| • At least one policy class must be created to use the configured | |
|
|
|
| affinities. | |
|
|
|
|
|
|
|
|
|
| Caution: You must designate at least one data stripe group in each |
|
|
|
|
| managed file system as |
|
|
|
|
| this designation, writing to the area of the file system that |
|
|
|
|
| is not associated with any of the affinities will result in an |
|
|
|
|
|
| |
|
|
|
| Deleting affinities from a file system configuration after |
|
|
|
|
| the file system has been in use for a while could result in |
|
|
|
|
| abnormal behavior. Contact the Quantum Technical |
|
|
|
|
| Assistance Center before deleting affinities from a file |
|
|
|
|
| system configuration. |
|
|
|
|
|
|
|
|
|
|
|
|
|
Performing a Metadata Dump
This procedure replaces any existing metadata dump data for the selected file system, and should be run only if the metadata file has been lost or corrupted.
StorNext User’s Guide | 133 |
