Distributed object-based storage system that uses pointers stored as object attributes for object analysis and monitoring

1. In a distributed object-based storage system that includes a plurality of object storage devices, and one or more clients that access distributed, object-based files from the object storage devices, each of said files being comprised of a plurality of object components residing on different object storage devices, a method for identifying files that are missing components, comprising:

for at least one component of each file, storing on the object storage device storing the component a single pointer having a count value in an attribute field of the component, wherein the count value of the single pointer corresponds to a maximum number of components for the file, and wherein the single pointer points to a further component of the file such that a last single component points back to a first single component to form a ring, and the last single component is different from the first single component, and the single pointer in the last component includes a value of the first component; and

for each file, using at least one network node to retrieve a list of components in the file and attempt to retrieve from an attribute field of at least one component of the file, the count value of the single pointer corresponding to the maximum number of components of the file; and

for each file, if the count value of the single pointer corresponding to the maximum number of components of the file was successfully retrieved from an attribute field of at least one component of the file, using at least one network node to compare the number of components on the list to the count value of the single pointer and determine that the file has the missing components if the file has fewer components than the count value of the single pointer.

2. The method of claim 1 , wherein a file is identified as having a metadata inconsistency if the attempt to retrieve the count value from an attribute field of at least one component of the file is unsuccessful.

3. In a distributed object-based storage system that includes a plurality of object storage devices, and one or more clients that access distributed, object-based files from the object storage devices, each of said files being comprised of a plurality of object components residing on different object storage devices, a system for identifying files that are missing components, comprising:

at least one server that, for at least one component of each file, stores on the object storage device storing the component a single pointer having a count value in an attribute field of the component, wherein the count value of the single pointer corresponds to a maximum number of components for the file, and wherein the single pointer points to a further component of the file such that a last single component points back to a first single component to form a ring, and the last single component is different from the first single component, and the single pointer in the last component includes a value of the first component; and

wherein, for each file, the at least one server retrieves a list of components in the file and attempts to retrieve from an attribute field of at least one component of the file the count value corresponding to the maximum number of components of the file; and

wherein, for each file, the at least one server compares the number of components on the list to the count value of the single pointer and determines that the file has the missing components if the file has fewer components than the count value.

4. The system of claim 3 , wherein the at least one server identifies a file as having at least one missing component if the attempt to retrieve the count value from an attribute field of at least one component of the file is unsuccessful.