File Storage system having separation of components

• US 20030200222A1
• Filed: 05/20/2003
• Published: 10/23/2003
• Est. Priority Date: 09/19/2000
• Status: Abandoned Application

• Current Assignee: Agami Systems, Inc.
• Original Assignee: Agami Systems, Inc.
• Inventors: Qureshi, Waheed, Manczak, Olaf W., Feinberg, George, Nowicki, Kacper, Ramos, Luis
• Application Number:
  US10/442,528
• Publication Number:
  US 20030200222A1
• Time in Patent Office: Days
• US Class Current: 707/100
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 2003/0697 device management, e.g. handlers, drivers, I/O schedulers
• CPC Class Codes: G06F 3/0601 Interfaces specially adapted for storage systems

Abstract

According to one embodiment, a storage system (100) may include an interface component (106) having a number of gateway servers (114), a metadata service component (108) having a number of metadata servers (116), and a content service component (110) that includes a number of storage servers (118). Scalability may be improved by enabling servers to be added to each different component (106, 108 and 110) separately. Availability may be improved as software and/or hardware can be changed for host machine in a component (106, 108 and 110) while the remaining host machines of the component continue to function.

Claims

1. A storage system, comprising:

an interface component that includes a plurality of first computing machines operating as gateway servers, each gateway server receiving storage system access requests from client applications;

a metadata service component that stores metadata for files stored in the storage system, the metadata service component including a plurality of second computing machines operating as metadata servers, the second computing machines being separate from the first computing machines, each metadata server receiving metadata access requests from the interface component; and

a content component that stores files for the storage system, the content component including a plurality of third computing machines operating as storage servers, the third computing machines being separate from the first and second computing machines, each storage server receiving file access requests from the interface component.

2. The storage system of claim 1, wherein:

each gateway server includes

a network interface for processing requests from client applications,

a mapping layer for translating client application requests into a common set of file and metadata access operations,

a gateway application for executing the common set of operations in conjunction with the metadata service component and content component, and

a gateway interface that defines operations for the metadata service component and content component.

3. The storage system of claim 1, wherein:

each metadata server includes

a metadata server interface for receiving defined operations from the interface component, and

a metadata server application for executing defined operations and returning values to the interface component;

wherein

each metadata server can store metadata for a predetermined number of files stored in the content component.

4. The storage system of claim 1, wherein:

each storage server includes

a storage server interface for receiving defined operations from the interface component, and

a storage server application for executing defined operations and returning values to the interface component;

wherein

each storage server can store metadata for a predetermined number of files.

5. The storage system of claim 1, wherein:

the interface component can receive storage system access requests over a first network; and

the interface component, metadata service component, and content component are commonly connected by a second network.

6. The storage system of claim 1, wherein:

the metadata service component includes metadata servers that access different types of storage hardware.

7. The storage system of claim 1, wherein:

the storage service component includes storage servers that access different types of storage hardware.

8. A storage system, comprising:

first computing machines configured to service accesses to stored files and not configured to access metadata for the stored files; and

second computing machines configured to service accesses to metadata for the stored files.

9. The storage system of claim 8, wherein:

the first computing machines are physically connected to file storage equipment that stores the stored files; and

the second computing machines are physically connected to metadata storage equipment that stores metadata for the stored files.

10. The storage system of claim 8, further including:

third computing machines configured to service requests to the storage system from client applications by accessing the first and second computing machines.

11. The storage system of claim 10, wherein:

the first, second and third computing machines are connected to on another by a communication network.

12. The storage system of claim 10, wherein:

each first computing machine may include at least one storage server process that may receive access requests from a requesting third computing machine and return stored file data to the requesting third computing machine.

13. The storage system of claim 10, wherein:

each second computing machine may include at least one metadata server process that may receive access requests from a requesting third computing machine and return metadata to the requesting third computing machine.

14. The storage system of claim 8, wherein:

each second computing machine stores files no greater than 512 bytes in size.

15. A method of operating a storage system, comprising the steps of:

storing files on a first set of machines;

storing metadata for the files on a second set of machines; and

receiving requests for metadata and files on a third set of machines;

wherein

the first, second and third machines are physically separate but connected to one another by a communication network.

16. The method of claim 15, further including:

accessing files stored on the first set of machines through the third set of machines.

17. The method of claim 16, wherein:

accessing files includes the third set of machines mapping requests into common file access operations that are executable by the first set of machines.

20. The method of claim 15, further including:

running storage server processes on a plurality of first computing machines; and

changing the storage server process on at least one of the first computing machines while the storage server processes continue to run on the remaining first computing machines.

21. The method of claim 15, further including:

each first machine being connected to corresponding storage equipment that stores files; and

altering the storage equipment on at least one of the first computing machines while the remaining first computing machines are able to access files on corresponding storage equipment.

22. The method of claim 15, further including:

running metadata server processes on a plurality of second computing machines; and

changing the metadata server process on at least one of the second computing machines while the metadata server processes continue to run on the remaining second computing machines.

23. The method of claim 15, further including:

each second machine being connected to corresponding storage equipment that stores metadata; and

altering the storage equipment on at least one of the second computing machines while the remaining second computing machines are able to access metadata on corresponding storage equipment.

18. The method of claim 154, further including:

accessing metadata stored on the second set of machines through the third set of machines.

19. The method of claim 18, wherein:

accessing metadata includes the third set of machines mapping requests into common metadata access operations that are executable by the second set of machines.