Depending on the problem, you might want to confirm where object data is being stored. For example, you might want to verify that the ILM policy is performing as expected and object data is being stored where intended.
Before you begin
- You must be signed in to the Grid Management Interface using a supported browser.
- To perform this task, you need specific access permissions. For details, see information about controlling system access with administration user accounts and groups.
- You must have an object identifier, which can be one of:
- S3 bucket and key: When an object is ingested through the S3 interface, the client application uses a bucket and key combination to store and identify the object.
For details, see the S3 Implementation Guide.
- Swift container and object: When an object is ingested through the Swift interface, the client application uses a container and object combination to store and identify the object.
For details, see the Swift Implementation Guide.
- S3 bucket and key: When an object is ingested through the S3 interface, the client application uses a bucket and key combination to store and identify the object.
Steps
- Type the S3 bucket/key or Swift container/object in the Object field.
- Click Look Up. The object metadata lookup results appear. This page lists the following types of information:
- System metadata, including the object ID, the object name, the name of the container, the tenant account name or ID, the logical size of the object, the date and time the object was first created, and the date and time the object was last modified.
- Any custom user metadata key-value pairs associated with the object.
- For S3 objects, any object tag key-value pairs associated with the object.
- For replicated object copies, the current storage location of each copy, including the name of the grid node and the full path to the disk location of the object.
- For erasure-coded object copies, the current storage location of each fragment, including the name of the grid node and the type of fragment (data or parity).
- For segmented objects, a list of object segments including segment identifiers and data sizes. For objects with more than 100 segments, only the first 100 segments are shown.
- All object metadata in the unprocessed, internal storage format.
The following example shows the object metadata lookup results for an S3 test object that is stored using both replication and erasure coding.
