Browse Prior Art Database

Efficient Container Deletion

IP.com Disclosure Number: IPCOM000248327D
Publication Date: 2016-Nov-15
Document File: 2 page(s) / 19K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to improve the container deletion process by requiring the end user to ensure that the storage container is empty before deleting the actual container.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 56% of the total text.

Page 01 of 2

Efficient Container Deletion

When using "container mode" in data source name (DSN) memory, more than one container may be stored using the same backing-vault to store all the objects. All containers using the same backing vault share the same storage namespace. This can complicate tasks such as container deletion, because identifying which slices are associated with which containers cannot necessarily be done by inspecting the name alone. This can make bulk container deletion slower than deleting vaults.

The novel solution is a method to improve the container deletion process by requiring the end user to ensure that the storage container is empty before deleting the actual container.

To implement this method in a preferred embodiment:

1. Encode a unique container serial number within each object's SourceName A. Dispersed objects are identified via a unique name known as a SourceName

    B. Each SourceName has a routable and non-routable component C. This change proposes leaving a serial number that is unique to the container (e.g., 4-8 bytes) within the name that individual data source (ds) units can efficiently identify 2. Establish a protocol for communicating container deletion between ds processing units and ds memory units 3. Mark a container as deleted
A. Each container has its own metadata object that requires lookup before any read or write operation. A field could indicate the visibility or deletion status of a container.

B. Each container also has its own n...