Abstract: A network storage server system includes a distributed object store and a metadata subsystem. The metadata subsystem stores metadata relating to the stored data objects and allows data objects to be located and retrieved easily via user-specified search queries. It manages and allows searches on at least three categories of metadata via the same user interface and technique. These categories include user-specified metadata, inferred metadata and system-defined metadata. Search queries for the metadata can include multi-predicate queries.

Abstract: A first file server for use with a distributed-file system includes a processor configured to determine that an incoming file system communication is associated with a first portion of the distributed-file system associated with a second file server, send a first authorization request to the second file server to request authorization to directly access the first portion of the distributed-file system, analyze a first authorization response from the second file server to determine at least one storage location associated with the first portion of the distributed-file system, determine that an incoming second authorization request received from a third file server is associated with a second portion of the distributed-file system associated with the first file server, obtain data indicative of the second portion of the distributed-file system, and send a second authorization response that includes the data.

Abstract: A distributed object store in a network storage system uses location-independent global object identifiers (IDs) for stored data objects. The global object ID enables a data object to be seamlessly moved from one location to another without affecting clients of the storage system, i.e., “transparent migration”. The global object ID can be part of a multilevel object handle, which also can include a location ID indicating the specific location at which the data object is stored, and a policy ID identifying a set of data management policies associated with the data object. The policy ID may be associated with the data object by a client of the storage system, for example when the client creates the object, thus allowing “inline” policy management. An object location subsystem (OLS) can be used to locate an object when a client request does not contain a valid location ID for the object.

Abstract: A distributed object store in a network storage system uses location-independent global object identifiers (IDs) for stored data objects. The global object ID enables a data object to be seamlessly moved from one location to another without affecting clients of the storage system, i.e., “transparent migration”. The global object ID can be part of a multilevel object handle, which also can include a location ID indicating the specific location at which the data object is stored, and a policy ID identifying a set of data management policies associated with the data object. The policy ID may be associated with the data object by a client of the storage system, for example when the client creates the object, thus allowing “inline” policy management. An object location subsystem (OLS) can be used to locate an object when a client request does not contain a valid location ID for the object.

Abstract: A network storage server system includes a distributed object store and a metadata subsystem. The metadata subsystem stores metadata relating to the stored data objects and allows data objects to be located and retrieved easily via user-specified search queries. It manages and allows searches on at least three categories of metadata via the same user interface and technique. These categories include user-specified metadata, inferred metadata and system-defined metadata. Search queries for the metadata can include multi-predicate queries.

Abstract: A network storage server system includes a distributed object store and a metadata subsystem. The metadata subsystem stores metadata relating to the stored data objects and allows data objects to be located and retrieved easily via user-specified search queries. It manages and allows searches on at least three categories of metadata via the same user interface and technique. These categories include user-specified metadata, inferred metadata and system-defined metadata. Search queries for the metadata can include multi-predicate queries.

Abstract: A file server is provided for use in an association of devices that implements a distributed-file system, the association of devices including file servers that each are configured to control separate segments of the distributed-file system.

Abstract: A network storage server system includes a distributed object store, a presentation layer, a metadata subsystem, and a content management subsystem. The object store has no namespace and provides location-independent addressing of data objects. The presentation layer provides multiple interfaces for accessing data stored in the object store, including a NAS interface and a Web Service interface, and provides at least one namespace for accessing data via the NAS interface or the Web Service interface. The Web Service interface allows access to stored data via the namespace or without using the namespace (“raw object” access). The metadata subsystem stores user-specified and/or system-generated metadata relating to data objects and allows data objects to be identified and retrieved by searching on the metadata.

Abstract: Embodiments described herein describe a file server used in an association with devices to implement a distributed-file system. The file server includes processor that is operative to store a first shadow tree entry providing a pointer to a file system object, where the first shadow tree entry provides an alternative to a first remote ancestor directory to access the file system object in the distributed file system.

Abstract: A method of performing a file system consistency check in a distributed, segmented file system, includes: analyzing primary objects of a first segment of the file system to determine if a first primary object points to a second primary object of a second segment separate from the first segment, storing, if the first primary object points to the second primary object of the second segment, a first indication indicating that the first primary object points to the second primary object of the second segment, the first indication indicating an expected location of the second primary object; analyzing a shadow directory of the selected segment to determine an expected location of a third primary object, and an expected pointer of the third primary object indicative of a location and a name of a fourth primary object, the third primary object being contained in a segment other than the first segment; and storing a second indication indicating the expected location of the third primary object and the expected pointe

Abstract: A network storage server system includes a presentation layer that presents multiple namespaces over the same data stored in an object store, allowing users to simultaneously access data over multiple protocols. The system supports object location independence of the stored data objects by introducing a layer of indirection between directory entries and storage locations of stored data objects. In one embodiment, the directory entry of a data object points to a redirector file that includes an object locator (e.g., an object handle or a global object ID) of the data object. The directory entries of data objects are stored in a directory namespace (e.g., NAS path namespace). In another embodiment, a global object ID of the data object is directly encoded within the directory entry of the data object.

Abstract: A system for implementing a distributed, segmented file system includes file servers that each are configured to control separate segments of the distributed-file system, the file servers including: a memory interface configured to communicate with a memory storing at least one of the segments of the distributed file system; a communication interface coupled to at least another of the file servers; and a processor coupled to the memory interface and the communication interface and configured to control, read, and write to file system objects stored in the memory. The system further includes means for transferring permission for access to a requested file system object from an owner server currently controlling a segment where a requested object resides to an access-requesting server.

Abstract: A system includes storage configured to store file system entities, including directories and files, residing in segments of a distributed, segmented single file system, file servers configured to implement the single file system with separate ones of the file servers controlling metadata of separate ones of the segments, and a controller configured to control storage of files in the file system such that for a master file stored in a first segment, a first replica of the master file will be stored in a second segment that is physically separate from the first segment, the controller being further configured to control storage of directories in the file system such that a single directory will include identifiers for the master file and the first replica.

Abstract: A method of managing segments in a distributed-file system implemented by a plurality of file servers includes determining a segment of the distributed-file system controlled by a first file server for which control is to be migrated, selecting a second file server, that is different from the first file server, to take control of the segment, and moving control of the segment from the first file server to the second file server.

Abstract: An apparatus in a first device of an association of devices includes a processor configured to: communicate with a storage device storing segments of a distributed, segmented single first file system including file system entities residing in segments and including at least portions of one of files and directories, the association of devices including file servers that control metadata of separate segments of the single first file system, including metadata of file system entities residing in the segments; communicate with a backup module configured to backup file system data of a second file system different from a distributed, segmented file system; analyze data in the single first file system to determine data associated with different segments of the single first file system; and present data from the single first file system to the backup module in accordance with what data belong to which segment of the single first file system.

Abstract: A method of performing a file system consistency check in a distributed, segmented file system, includes: analyzing primary objects of a first segment of the file system to determine if a first primary object points to a second primary object of a second segment separate from the first segment, storing, if the first primary object points to the second primary object of the second segment, a first indication indicating that the first primary object points to the second primary object of the second segment, the first indication indicating an expected location of the second primary object; analyzing a shadow directory of the selected segment to determine an expected location of a third primary object, and an expected pointer of the third primary object indicative of a location and a name of a fourth primary object, the third primary object being contained in a segment other than the first segment; and storing a second indication indicating the expected location of the third primary object and the expected pointe

Abstract: Techniques are provided for producing a shadow directory structure for files or directories owned by servers whose parent directories are owned by different servers in a single distributed file system. For each file or directory whose parent directory resides on a remote server, the server owning the file or directory produces a shadow directory structure. The shadow structure may be used in a variety of ways, e.g., to access an orphan when the server owning the orphan's parent directory is offline (e.g., down, failed, or otherwise inaccessible), or to perform a partial file system consistency check (a partial fsck) to verify consistency of segments of the file system.

Abstract: A file system (i) permits storage capacity to be added easily, (ii) can be expanded beyond a given unit, (iii) is easy to administer and manage, (iv) permits data sharing, and (v) is able to perform effectively with very large storage capacity and client loads. State information from a newly added unit is communicated (e.g., automatically and transparently) to central administration and management operations. Configuration and control information from such operations is communicated (e.g., automatically) back down to the newly added units, as well as existing units. In this way, a file system can span both local storage devices (like disk drives) and networked computational devices transparently to clients. Such state and configuration and control information can include globally managed segments as the building blocks of the file system, and a fixed mapping of globally unique file identifiers (e.g., Inode numbers) and/or ranges thereof, to such segments.

Abstract: A file system (i) permits storage capacity to be added easily, (ii) can be expanded beyond a given unit, (iii) is easy to administer and manage, (iv) permits data sharing, and (v) is able to perform effectively with very large storage capacity and client loads. State information from a newly added unit is communicated (e.g., automatically and transparently) to central administration and management operations. Configuration and control information from such operations is communicated (e.g., automatically) back down to the newly added units, as well as existing units. In this way, a file system can span both local storage devices (like disk drives) and networked computational devices transparently to clients. Such state and configuration and control information can include globally managed segments as the building blocks of the file system, and a fixed mapping of globally unique file identifiers (e.g., Inode numbers) and/or ranges thereof, to such segments.

Abstract: A method of managing segments in a distributed-file system implemented by a plurality of file servers includes determining a segment of the distributed-file system controlled by a first file server for which control is to be migrated, selecting a second file server, that is different from the first file server, to take control of the segment, and moving control of the segment from the first file server to the second file server.