Accelerated access to objects in an object store implemented utilizing a file storage system

• US 10,210,191 B2
• Filed: 03/20/2014
• Issued: 02/19/2019
• Est. Priority Date: 03/20/2014
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Baldwin, Duane M., Olson, John T., Punadikar, Sachin C., Patil, Sandeep R.
• Primary Examiner(s): Perveen, Rehana
• Assistant Examiner(s): Wong, Huen
• Application Number:
  US14/220,921
• Publication Number:
  US 20150269203A1
• Time in Patent Office: 1,797 Days
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/2228 Indexing structures

Abstract

In one embodiment, a method for creating an object includes creating an object in an object store making use of a file system, obtaining an index node (inode) identifier (ID) for an inode associated with the object, creating an object ID for the object, wherein the object ID is unique from any other object IDs in the object store, merging the object ID with the inode ID, and modifying the inode to include at least the object ID. In another embodiment, a system includes a processor and logic integrated with and/or executable by the processor, the logic being configured to: create an object in an object store making use of a file system, obtain an inode ID for an inode associated with the object, create an object ID for the object, the object ID including the inode and modify the inode to include at least the object ID.

Claims

1. A method for creating an object, the method comprising:

creating an object in an object store making use of a file system;

obtaining an index node (inode) identifier (ID) for an inode associated with the object;

creating an object ID for the object, wherein the object ID is unique from any other object IDs in the object store;

merging the inode ID into the object ID to create a merged object ID that includes the inode ID in its entirety, the inode ID being extractable from the merged object ID; and

modifying the inode to include at least the merged object ID.

2. The method as recited in claim 1, further comprising:

receiving a request to create the object in the object store from a remote system prior to creating the object; and

sending the merged object ID for the object to the remote system after creating the object.

3. The method as recited in claim 1, further comprising:

modifying the inode to include a path name for the object to provide search parameters for the object,

wherein a totality of the inode ID is appended to a beginning or an end of the object ID to create the merged object ID.

4. The method as recited in claim 1, further comprising adding the object ID and a path name for the object to extended attributes of the inode.

5. The method as recited in claim 1, further comprising merging second metadata with the merged object ID, the second metadata comprising object storage search parameters, wherein the object ID has the inode ID appended thereto to create the merged object ID.

6. A computer program product for accessing an object, the computer program product comprising a computer readable storage medium having program code embodied therewith, the program code readable and/or executable by a processor to cause the processor to:

extract, by the processor, an index node (inode) identifier (ID) in its entirety from an object ID associated with an object stored in an object store making use of a file system;

access, by the processor, an inode associated with the inode ID and determine an object ID stored therein;

determine, by the processor, whether the object ID from the inode matches the object ID associated with the object from which the inode ID was extracted; and

perform, by the processor, an operation on the object.

7. The computer program product as recited in claim 6, wherein the program code readable and/or executable by the processor further causes the processor to:

receive a request to access the object stored in the object store from a remote system; and

send results of accessing the object after performing the operation thereon to the remote system.

8. The computer program product as recited in claim 7, wherein the request includes the object ID associated with the object to be accessed, and the operation to perform on the object.

9. The computer program product as recited in claim 6, wherein the operation to perform on the object includes at least one of reading, writing, and modifying, and wherein a totality of the inode ID is appended to the object ID.

10. The computer program product as recited in claim 6, wherein the program code readable and/or executable by the processor further causes the processor to determine a path name from the inode in response to a determination that the path name is required for further processing of the object.

11. A system, comprising a processor and logic integrated with and/or executable by the processor, the logic being configured to:

create an object in an object store making use of a file system;

obtain an index node (inode) identifier (ID) for an inode associated with the object;

create an object ID for the object, the object ID including the inode ID in its entirety, wherein the object ID is unique from any other object IDs in the object store and the inode ID is extractable from the object ID; and

modify the inode to include at least the object ID.

12. The system as recited in claim 11, wherein the logic is further configured to:

receive a request to create the object in the object store from a remote system prior to creating the object; and

send the object ID for the object to the remote system after creating the object.

13. The system as recited in claim 11, wherein the logic is further configured to modify the inode to include a path name for the object.

14. The system as recited in claim 11, wherein the logic is further configured to add the object ID and a path name for the object to extended attributes of the inode.

15. The system as recited in claim 11, wherein the object ID has the inode ID appended thereto, and wherein a totality of the inode ID is appended to a beginning or an end of the object ID.

16. The system as recited in claim 11, wherein the logic is further configured to:

extract the inode ID from the object ID associated with the object stored in the object store;

access the inode associated with the inode ID and determine an object ID stored therein;

determine whether at the object ID from the inode matches the object ID associated with the object from which the inode ID was extracted; and

perform an operation on the object when the object ID from the inode matches the object ID associated with the object from which the inode ID was extracted.

17. The system as recited in claim 16, wherein the logic is further configured to:

receive a request to access the object stored in the object store from a remote system; and

send results of accessing the object after performing the operation thereon to the remote system.

18. The system as recited in claim 17, wherein the request includes the object ID associated with the object to be accessed, and the operation to perform on the object.

19. The system as recited in claim 16, wherein the operation to perform on the object includes at least one of reading, writing, and modifying.

20. The system as recited in claim 16, wherein the logic is further configured to determine a path name from the inode in response to a determination that the path name is required for further processing of the object.