Object file system

• US 9,189,493 B2
• Filed: 09/26/2014
• Issued: 11/17/2015
• Est. Priority Date: 08/31/2010
• Status: Active Grant

• Current Assignee: DataDirect Networks Incorporated
• Original Assignee: DataDirect Networks Incorporated
• Inventors: Olderdissen, Jan, Olster, Dan, Robertson, Craig, Schafer, Doug, Fellinger, Dave
• Primary Examiner(s): ALAM, SHAHID AL
• Application Number:
  US14/498,917
• Publication Number:
  US 20150019598A1
• Time in Patent Office: 417 Days
• Field of Search: 707/823
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1076 Parity data used in redundant arrays of independent storages, e.g. in RAID systems
• CPC Class Codes: G06F 16/18 File system types
• CPC Class Codes: G06F 16/1847 specifically adapted to static storage, e.g. adapted to flash memory or SSD
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 2211/1038 LFS, i.e. Log Structured File System used in RAID systems with parity
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

An object based file system for storing and accessing objects is disclosed. The file system may be implemented as a method in hardware, firmware, software, or a combination thereof. The method may include receiving from an application program an object write request. A selected storage node on which to store the object may be selected, including identifying a least busy storage node and/or a least full storage node. The object and the object write request may be sent to the selected storage node. A write success message may be received from the selected storage node. The successful writing of the object may be reported to the application program.

Claims

1. A method for accessing objects comprising:

object access software on a server receiving from an application program an object write request, the write request including an object comprised of object data and meta data

the object access software selecting a best storage node from a plurality of storage nodes on which to store the object including identifying and evaluating among a least busy storage node, a most used storage node and a least full storage node of the plurality of storage nodes

the object access software selecting additional storage nodes from the plurality of storage nodes on which to store the object

the object access software sending the object and the object write request to the best storage node

the object access software sending the object and the object write request to the additional storage nodes

the object access software receiving a first write success message from the best storage node, the first write success message including an object identifier, the object identifier including a version identifier, a location identifier and a unique identifier

the object access software reporting successful writing of the object to the application program including providing the object identifier to the application program

the object access software receiving additional write success messages from the additional storage nodes

the object access software recognizing the addition of a new storage node

the object access software automatically adapting to the new storage node including redistributing objects from a more full node of the plurality of storage nodes to the new storage node.

2. The method of claim 1 further comprising:

the object access software receiving a read request for a requested object specifying the object identifier

the object access software selecting to obtain the requested object from among the best storage node, the new storage node and the additional storage nodes according to criteria including a shortest path, a highest speed connection, and a least accessed.

3. The method of claim 1 wherein each storage node includes a plurality of storage media.

4. The method of claim 3 wherein the storage media are one or more selected from the group including hard disk drives, silicon storage devices and magnetic tape devices.

5. The method of claim 1 wherein each storage node runs a local file system.

6. The method of claim 1 wherein the meta data includes at least one selected from the group including an object creator, object owner, access permissions, and a creation time.

7. The method of claim 1 further comprising:

the object access software storing the object identifier and the meta data for the object in a database.

8. A non-transitory storage medium having instructions stored thereon which when executed by a processor cause the processor to perform actions comprising:

receiving from an application program an object write request, the write request including an object comprised of object data and meta data

selecting a best storage node from a plurality of storage nodes on which to store the object including identifying and evaluating among a least busy storage node, a most used storage node and a least full storage node of the plurality of storage nodes

selecting additional storage nodes from the plurality of storage nodes on which to store the object

sending the object and the object write request to the best storage node

sending the object and the object write request to the additional storage nodes

receiving a first write success message from the best storage node, the write success message including an object identifier, the object identifier including a version identifier, a location identifier and a unique identifier

reporting successful writing of the object to the application program including providing the object identifier

receiving additional write success messages from the additional storage nodes

recognizing the addition of a new storage node

automatically adapting to the new storage node including redistributing objects from a more full node of the plurality of storage nodes to the new storage node.

9. The non-transitory storage medium of claim 8 have further instructions stored thereon which when executed by the processor cause the processor to perform further actions including:

receiving a read request for a requested object specifying the object identifier

selecting to obtain the requested object from among the best storage node, the new storage node and the additional storage nodes according to criteria including a shortest path, a highest speed connection, and a least accessed.

10. The non-transitory storage medium of claim 8 wherein each storage node includes a plurality of storage media.

11. The non-transitory storage medium of claim 10 wherein the storage media are one or more selected from the group including hard disk drives, silicon storage devices and magnetic tape devices.

12. The non-transitory storage medium of claim 8 wherein each storage node runs a local file system.

13. The non-transitory storage medium of claim 8 wherein the meta data includes at least one selected from the group including an object creator, object owner, access permissions, and a creation time.

14. The non-transitory storage medium of claim 8 have further instructions stored thereon which when executed by the processor cause the processor to perform further actions including:

storing the object identifier and the meta data for the object in a database.

15. A computing device to manage a plurality of storage arrays of storage devices, the computing device comprising:

a processor;

a memory coupled with the processor;

a storage medium having instructions stored thereon which when executed cause the computing device to perform actions comprising;

receiving from an application program an object write request, the write request including an object comprised of object data and meta data

selecting a best storage node from a plurality of storage nodes on which to store the object including identifying and evaluating among a least busy storage node, a most used storage node and a least full storage node of the plurality of storage nodes

selecting additional storage nodes from the plurality of storage nodes on which to store the object

sending the object and the object write request to the best storage node

sending the object and the object write request to the additional storage nodes

receiving a first write success message from the best storage node, the write success message including an object identifier, the object identifier including a version identifier, a location identifier and a unique identifier

reporting successful writing of the object to the application program including providing the object identifier

receiving additional write success messages from the additional storage nodes

recognizing the addition of a new storage node

automatically adapting to the new storage node including redistributing objects from a more full node of the plurality of storage nodes to the new storage node.

16. The computing device of claim 15 wherein the storage medium has further instructions stored thereon which when executed cause the computing device to perform further actions comprising:

receiving a read request for a requested object specifying the object identifier

selecting to obtain the requested object from among the best storage node, the new storage node and the additional storage nodes according to criteria including a shortest path, a highest speed connection, and a least accessed.

17. The computing device of claim 15 wherein each storage node includes a plurality of storage media.

18. The computing device of claim 17 wherein the storage media are one or more selected from the group including hard disk drives, silicon storage devices and magnetic tape devices.

19. The computing device of claim 15 wherein each storage node runs a local file system.

20. The computing device of claim 15 wherein the meta data includes at least one selected from the group including an object creator, object owner, access permissions, and a creation time.

21. The computing device of claim 15 wherein the storage medium has further instructions stored thereon which when executed cause the computing device to perform further actions comprising:

storing the object identifier and meta data for the object in a database.