Managing Fragments
Scenarios
Fragments refer to incomplete data in a bucket. Data is uploaded to OBS in multipart mode. In the following common and other scenarios, an upload fails and fragments are generated. You need to clear these fragments to free up storage space.
- The network is in poor conditions, and the connection to the OBS server is interrupted frequently.
- The upload task is manually suspended.
- The device is faulty.
- The device is powered off suddenly.
Fragments in OBS consume storage space and are billed based on price rates of storage space. If fragments are generated due to interruptions or failures of multipart upload tasks, you can resume such tasks so that fragments will be cleared, or you can directly clear the fragments to save storage space.
- If a bucket fails to be deleted, check whether all fragments have been deleted. If not, delete all fragments from the bucket.
- If no object exists in the bucket but the fee is still being deducted, check whether there are fragments in the bucket. If yes, delete the fragments to reduce storage costs.
How to Use
Tool |
Method |
---|---|
OBS Console |
OBS Console allows you to batch delete all selected fragments with one click. For details, see Managing Fragments. |
OBS Browser+ |
You can delete all of the selected fragments in a bucket in a batch. Alternatively, you can click Delete All above the list to delete all fragments. |
obsutil |
With obsutil, you can delete the failed or interrupted multipart upload task to delete fragments generated by the task. If a bucket has more than one multipart upload tasks, you need to delete all the multipart upload tasks to delete all fragments in the bucket. For details, see Deleting a Multipart Upload Task. |
API |
You can delete fragments from a bucket through the following procedure:
|
SDKs |
With OBS SDK, fragments are generated when parts of a multipart task are not merged. You can cancel the task to delete generated fragments. The procedure is as follows:
|
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.