Peer-to-peer redundant file server system and methods

• US 9,740,707 B2
• Filed: 09/14/2012
• Issued: 08/22/2017
• Est. Priority Date: 04/29/2008
• Status: Expired due to Fees

• Current Assignee: Overland Storage Incorporated (Silicon Valley Technology Partners LLC)
• Original Assignee: Overland Storage Incorporated (Silicon Valley Technology Partners LLC)
• Inventors: Lacapra, Francesco, Steele, Peter Wallace, Sartirana, Bruno, Hua, Ernest Ying Sue, Lin, I Chung Joseph, Li, Samuel Sui-Lun, Diller, Nathanael John, Ramsdell, Thomas Reynold, Nguyen, Don, Tran, Kyle Dinh
• Primary Examiner(s): Nguyen, Thuong
• Application Number:
  US13/619,689
• Publication Number:
  US 20130018928A1
• Time in Patent Office: 1,803 Days
• Field of Search: 709219, 709248, 370261, 370400, 370350
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/1834 implemented based on peer-to-peer networks, e.g. gnutella p2p communication protocols H04L67/104
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• 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

Peer-to-peer redundant file server system and methods include clients that determine a target storage provider to contact for a particular storage transaction based on a pathname provided by the filesystem and a predetermined scheme such as a hash function applied to a portion of the pathname. Servers use the same scheme to determine where to store relevant file information so that the clients can locate the file information. The target storage provider may store the file itself and/or may store metadata that identifies one or more other storage providers where the file is stored. A file may be replicated in multiple storage providers, and the metadata may include a list of storage providers from which the clients can select (e.g., randomly) in order to access the file.

Claims

1. A method for maintaining peer set nodes of a computer file storage system, a peer set comprising a plurality of storage nodes that are each implemented on different storage servers of the computer file storage system, the method comprising:

identifying, with a microprocessor of the computer file storage system, a plurality of waiting nodes associated with a current peer set via producing, at a root node, an updated list of the current peer set nodes, wherein at least a portion of file data content stored by the peer set is to be synchronized across two or more storage nodes of the peer set; and

establishing, with the microprocessor of the computer file storage system, a hierarchy and role distribution among the identified waiting nodes via conducting a dialog among the identified plurality of waiting nodes, the dialog comprising;

transmitting merge messages from the root node to each of the plurality of waiting nodes of the current peer set, wherein the merge messages contain descriptors of waiting nodes associated with the current peer set, and wherein each of the plurality of waiting nodes is configured to, in response to receiving the merge message from the root, pass the received merge message to at least a portion of the remaining waiting nodes of the current peer set, and

transmitting invitations from each of the plurality of waiting nodes to each of the other waiting nodes of the current peer set, each invitation triggering a receiving waiting node to respond by sending an acknowledgment to a corresponding sending waiting node.

2. A method according to claim 1, wherein identifying the waiting nodes associated with the current peer set of nodes comprises:

receiving, by a waiting node, from the root node, a message containing descriptors of waiting nodes associated with the current peer set.

3. A method according to claim 1, wherein the dialog further comprises:

receiving at the root node, via a designated waiting node of the current peer set, a notification that all pairs of waiting nodes of current peer set have exchanged invitation and acknowledgment messages, in response to a determination that a dialog indicator is positive;

wherein the dialog indicator is determined to be positive if each of waiting nodes received acknowledgments from each of remaining waiting nodes, and wherein the dialog indicator is determined to be negative otherwise.

4. A method according to claim 3, further comprising:

allocating replacement nodes for the current peer set if the dialog indicator is negative.

5. A method according to claim 1, wherein conducting the dialog further comprises:

passing messages received from the root node by each of waiting nodes to at least a portion of the remaining waiting nodes.

6. A computer file storage system, comprising:

a plurality of storage servers each implementing one or more storage nodes;

a peer set comprising a plurality of storage nodes that are each implemented on different storage servers of the computer file storage system, wherein at least a portion of file data content stored by the peer set is to be synchronized across two or more storage nodes of the peer set; and

a root node for maintaining peer set nodes of the computer file storage system, comprising one or more microprocessors, the root node being configured to;

identify a plurality of waiting nodes associated with the current peer set via producing an updated list of the current peer set nodes; and

establish a hierarchy and role distribution among the identified plurality of waiting nodes via a dialog conducted among the identified plurality of waiting nodes, wherein the dialog comprises;

transmitting merge messages from the root node to each of the plurality of waiting nodes of the current peer set, wherein the merge messages contain descriptors of waiting nodes associated with the current peer set, and wherein each of the plurality of waiting nodes is configured to, in response to receiving the merge message from the root, pass the received merge message to at least a portion of the remaining waiting nodes of the current peer set, and

transmitting invitations from each of the plurality of waiting nodes to each of the other waiting nodes of the current peer set, each invitation triggering a receiving waiting node to respond by sending an acknowledgment to a corresponding sending waiting node.