Managing cloud storage for distributed file systems

Description

TECHNICAL FIELD

The present invention relates generally to file systems, and more particularly, but not exclusively, to managing file systems in cloud computing environments.

BACKGROUND

Modern computing often requires the collection, processing, or storage of very Large data sets or file systems. Accordingly, to accommodate the capacity requirements as well as other requirements, such as, high availability, redundancy, latency/access considerations, or the like, modern file systems may be very large or distributed across multiple hosts, networks, or data centers, and so on. File systems may include many storage volumes that may be subject to failure.

In some cases, file systems may be hosted or implemented in cloud computing environments. Accordingly, similar to conventional file systems, one or more virtualized components of file systems in cloud environments may experience various types of failures associated with one or more virtualized component, including storage volumes. Failures in cloud environments may introduce complications or considerations that may be different than those experienced in conventional file system operating in non-cloud environments. Thus, it is with respect to these considerations and others that the present invention has been made.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the present innovations are described with reference to the following drawings. In the drawings, like reference numerals refer to like parts throughout the various figures unless otherwise specified. For a better understanding of the described innovations, reference will be made to the following Detailed Description of Various Embodiments, which is to be read in association with the accompanying drawings, wherein:

FIG. 1 illustrates a system environment in which various embodiments may be implemented;

FIG. 2 illustrates a schematic embodiment of a client computer;

FIG. 3 illustrates a schematic embodiment of a network computer;

FIG. 4 illustrates a logical architecture of a system for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments;

FIG. 5 illustrates a logical schematic of a cloud computing environment for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments;

FIG. 6 illustrates a logical schematic of a cloud computing environment for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments;

FIG. 7 illustrates a logical schematic of a cloud computing storage volume for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments;

FIG. 8 illustrates an overview flowchart for a process for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments;

FIG. 9 illustrates a flowchart for a process for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments;

FIG. 10 illustrates a flowchart for a process for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments; and

FIG. 11 illustrates a flowchart for a process for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

Various embodiments now will be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific exemplary embodiments by which the invention may be practiced. The embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the embodiments to those skilled in the art. Among other things, the various embodiments may be methods, systems, media or devices. Accordingly, the various embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense.

Throughout the specification and claims, the following terms take the meanings explicitly associated herein, unless the context clearly dictates otherwise. The phrase “in one embodiment” as used herein does not necessarily refer to the same embodiment, though it may. Furthermore, the phrase “in another embodiment” as used herein does not necessarily refer to a different embodiment, although it may. Thus, as described below, various embodiments may be readily combined, without departing from the scope or spirit of the invention.

In addition, as used herein, the term “or” is an inclusive “or” operator, and is equivalent to the term “and/or,” unless the context clearly dictates otherwise. The term “based on” is not exclusive and allows for being based on additional factors not described, unless the context clearly dictates otherwise. In addition, throughout the specification, the meaning of “a,” “an,” and “the” include plural references. The meaning of “in” includes “in” and “on.”

For example embodiments, the following terms are also used herein according to the corresponding meaning, unless the context clearly dictates otherwise.

As used herein the term, “engine” refers to logic embodied in hardware or software instructions, which can be written in a programming language, such as C, C++, Objective-C, COBOL, Java™, PHP, Perl, JavaScript, Ruby, VBScript, Microsoft .NET™ languages such as C#, or the like. An engine may be compiled into executable programs or written in interpreted programming languages. Software engines may be callable from other engines or from themselves. Engines described herein refer to one or more logical modules that can be merged with other engines or applications, or can be divided into sub-engines. The engines can be stored in non-transitory computer-readable medium or computer storage device and be stored on and executed by one or more general purpose computers, thus creating a special purpose computer configured to provide the engine.

As used herein the terms “file system object” refers to entities stored in a file system. These may include files, directories, or the like. In this document for brevity and clarity all objects stored in a file system may be referred to as file system objects.

As used herein the terms “file path,” “file system path,” or “hierarchical file system path,” and so on refer to file system information that corresponds to the logical or physical locations of file system objects within file systems. File system clients may employ file system paths to refer to specific file system objects within a file system. For example, file paths may include fields or values that correspond to the hierarchy of directories in the file system that correspond to the location of the file system object. In some cases, the name or label of the file may be considered path of the file system path. Also, often file system paths may be human readable.

As used herein the terms “block,” or “file system object block” refer to the file system data objects that comprise a file system object. For example, small sized file system objects, such as, directory objects or small files may be comprised of a single block. Whereas, larger file system objects, such as large document files may be comprised of many blocks. Blocks usually are arranged to have a fixed size to simplify the management of a file system. This may include fixing blocks to a particular size based on requirements associated with underlying storage hardware, such as, solid state drives (SSDs) or hard disk drives (HDDs), or the like. However, file system objects, such as, files may be of various sizes, comprised of the number of blocks necessary to represent or contain the entire file system object.

As used herein the terms “document object,” or “document” refer to file system objects that may be considered a file. Accordingly, document objects may include one or more blocks that represent one combined file. The term document may be used to distinguish file system objects that are files from file system objects that may represent directories, folders, blocks, or the like. Documents have one or more content blocks that store the data comprising the document. Herein, documents may represent file that store any type of compressed or uncompressed data, such as, text, binary data, media (e.g., video files, music files, images, sound files, or the like), application documents (e.g., word processing files, databases, programs, libraries, or the like), structured documents, or the like. Herein documents may be considered to be stored in a file system rather than an object store. Documents may be considered to be associated file system paths or other file system meta-data that may be irrelevant or unavailable on object stores.

As used herein the term “storage volume” refers to virtualized data stores provided by cloud computing environments. Various attributes or features of storage volumes may vary depending on the cloud computing environment. However, in general, storage volumes may be considered to be logically similar to physical storage devices, such as, hard drives, solid states drives, network drives, or the like. Cloud computing environments provide APIs or other interfaces that enable programmatic provisioning of storage volumes. Also, among other things, cloud computing environment provide APIs or other interfaces that enable programmatic assignment/association of storage volumes with one or more virtualized network computers in the cloud computing environment.

As used herein the term “healthy storage volume” refers to a storage volume that is operating within expected performance parameters as determined by one or more metrics.

As used herein the term “unhealthy storage volume” refers to a storage volume that is not operating within expected performance parameters as determined by one or more metrics.

As used herein the term “configuration information” refers to information that may include rule based policies, pattern matching, scripts (e.g., computer readable instructions), or the like, that may be provided from various sources, including, configuration files, databases, user input, built-in defaults, or the like, or combination thereof.

The following briefly describes embodiments of the invention in order to provide a basic understanding of some aspects of the invention. This brief description is not intended as an extensive overview. It is not intended to identify key or critical elements, or to delineate or otherwise narrow the scope. Its purpose is merely to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

Briefly stated, various embodiments are directed to managing data in a file system. In one or more of the various embodiments, the file system that includes a plurality of storage nodes and a plurality of storage volumes may be provided such that each storage node may be coupled to a portion of the plurality of storage volumes, and such that each storage node may be a compute instance in a cloud computing environment and each storage volume may be a data store in the cloud computing environment.

In one or more of the various embodiments, one or more metrics associated with each storage volume may be monitored.

In one or more of the various embodiments, in response to the one or more metrics exceeding a threshold value, further actions may be performed, including: determining one or more storage volumes in the plurality of storage volumes that are disabled based on the one or more metrics that exceed the threshold value; updating metadata associated with the one or more storage volumes to indicate that the one or more storage volumes are unhealthy; decoupling the one or more unhealthy storage volumes from one or more storage nodes coupled to the one or more unhealthy storage volumes; determining one or more replacement storage volumes based on the metadata associated with the one or more unhealthy storage volumes; updating other metadata associated with the one or more replacement storage volumes to indicate that the one or more replacement storage volumes are healthy storage volumes; and coupling the one or more healthy storage volumes with the one or more storage nodes that were coupled to the one or more unhealthy storage volumes.

In one or more of the various embodiments, determining the one or more replacement storage volumes may include: generating a query based on the metadata associated with the one or more unhealthy storage volumes; employing the query to determine one or more uncoupled healthy storage volumes in the cloud computing environment, wherein the metadata associated with the one or more unhealthy storage volumes matches the other metadata associated with the one or more uncoupled preexisting healthy storage volumes; and providing the one or more healthy storage volumes as at least a portion of the one or more replacement storage volumes.

In one or more of the various embodiments, determining the one or more replacement storage volumes may include, in response to a quantity of the one or more unhealthy storage volumes exceeding a quantity of one or more preexisting uncoupled healthy storage volumes, performing further actions, including: provisioning one or more additional uncoupled storage volumes from the cloud computing environment that match the one or more unhealthy storage volumes; updating metadata associated with the one or more uncoupled storage volumes to indicate that the one or more additional uncoupled storage volumes are uncoupled healthy storage volumes; and providing the one or more uncoupled healthy storage volumes as the one or more replacement storage volumes.

In one or more of the various embodiments, coupling the one or more healthy storage volumes with the one or more storage nodes may include: determining one or more storage slots associated with the one or more storage nodes based on the file system, wherein each storage slot corresponds to a fraction of a storage capacity of the file system; and associating the one or more health storage volumes with the one or more storage slots, wherein each healthy storage volume is employed to provide the fraction of the storage capacity that corresponds to its associated storage slot.

In one or more of the various embodiments, monitoring the one or more metrics associated with each storage volume may include querying each storage node of the plurality of storage nodes for one or more values of the one or more metrics that are associated a portion of the plurality of storage volumes that are coupled to the queried storage node, wherein the one or more values of the one or more metrics are based on error information provided to each storage node by the cloud computing environment.

In one or more of the various embodiments, the metadata associated with the one or more storage volumes may include one or more of a storage cluster identifier, a storage slot identifier, and a field for storing a value that indicates that a storage volume is healthy or unhealthy.

In one or more of the various embodiments, determining the one or more replacement storage volumes may include: determining one or more storage volumes that may be missing from the plurality of storage volumes based on the one or more metrics; providing storage volume information associated with the one or more missing storage volumes based on querying the one or more storage nodes; generating replacement metadata based on the storage volume information; provisioning one or more additional uncoupled storage volumes from the cloud computing environment based on the replacement metadata; updating metadata associated with the one or more additional uncoupled storage volumes to indicate that the one or more additional uncoupled storage volumes are uncoupled healthy storage volumes; and providing the one or more uncoupled healthy storage volumes as the one or more replacement storage volumes.

Illustrated Operating Environment

FIG. 1 shows components of one embodiment of an environment in which embodiments of the invention may be practiced. Not all of the components may be required to practice the invention, and variations in the arrangement and type of the components may be made without departing from the spirit or scope of the invention. As shown, system 100 of FIG. 1 includes local area networks (LANs)/wide area networks (WANs)—(network) 110, wireless network 108, client computers 102-105, application server computer 116, file system management server computer 118, cloud computing environment 120, or the like.

At least one embodiment of client computers 102-105 is described in more detail below in conjunction with FIG. 2. In one embodiment, at least some of client computers 102-105 may operate over one or more wired or wireless networks, such as networks 108, or 110. Generally, client computers 102-105 may include virtually any computer capable of communicating over a network to send and receive information, perform various online activities, offline actions, or the like. In one embodiment, one or more of client computers 102-105 may be configured to operate within a business or other entity to perform a variety of services for the business or other entity. For example, client computers 102-105 may be configured to operate as a web server, firewall, client application, media player, mobile telephone, game console, desktop computer, or the like. However, client computers 102-105 are not constrained to these services and may also be employed, for example, as for end-user computing in other embodiments. It should be recognized that more or less client computers (as shown in FIG. 1) may be included within a system such as described herein, and embodiments are therefore not constrained by the number or type of client computers employed.

Computers that may operate as client computer 102 may include computers that typically connect using a wired or wireless communications medium such as personal computers, multiprocessor systems, microprocessor-based or programmable electronic devices, network PCs, or the like. In some embodiments, client computers 102-105 may include virtually any portable computer capable of connecting to another computer and receiving information such as, laptop computer 103, mobile computer 104, tablet computers 105, or the like. However, portable computers are not so limited and may also include other portable computers such as cellular telephones, display pagers, radio frequency (RF) devices, infrared (IR) devices, Personal Digital Assistants (PDAs), handheld computers, wearable computers, integrated devices combining one or more of the preceding computers, or the like. As such, client computers 102-105 typically range widely in terms of capabilities and features. Moreover, client computers 102-105 may access various computing applications, including a browser, or other web-based application.

A web-enabled client computer may include a browser application that is configured to send requests and receive responses over the web. The browser application may be configured to receive and display graphics, text, multimedia, and the like, employing virtually any web-based language. In one embodiment, the browser application is enabled to employ JavaScript, HyperText Markup Language (HTML), eXtensible Markup Language (XML), JavaScript Object Notation (JSON), Cascading Style Sheets (CSS), or the like, or combination thereof, to display and send a message. In one embodiment, a user of the client computer may employ the browser application to perform various activities over a network (online). However, another application may also be used to perform various online activities.

Client computers 102-105 also may include at least one other client application that is configured to receive or send content between another computer. The client application may include a capability to send or receive content, or the like. The client application may further provide information that identifies itself, including a type, capability, name, and the like. In one embodiment, client computers 102-105 may uniquely identify themselves through any of a variety of mechanisms, including an Internet Protocol (IP) address, a phone number, Mobile Identification Number (MIN), an electronic serial number (ESN), a client certificate, or other device identifier. Such information may be provided in one or more network packets, or the like, sent between other client computers, application server computer 116, file system management server computer 118, cloud computing environment 120, or other computers.

Client computers 102-105 may further be configured to include a client application that enables an end-user to log into an end-user account that may be managed by another computer, such as application server computer 116, file system management server computer 118, object store 120, or the like. Such an end-user account, in one non-limiting example, may be configured to enable the end-user to manage one or more online activities, including in one non-limiting example, project management, software development, system administration, configuration management, search activities, social networking activities, browse various websites, communicate with other users, or the like. Also, client computers may be arranged to enable users to display reports, interactive user-interfaces, or results provided by application server computer 116, file system management server computer 118, cloud computing environment 120, or the like.

Wireless network 108 is configured to couple client computers 103-105 and its components with network 110. Wireless network 108 may include any of a variety of wireless sub-networks that may further overlay stand-alone ad-hoc networks, and the like, to provide an infrastructure-oriented connection for client computers 103-105. Such sub-networks may include mesh networks, Wireless LAN (WLAN) networks, cellular networks, and the like. In one embodiment, the system may include more than one wireless network.

Wireless network 108 may further include an autonomous system of terminals, gateways, routers, and the like connected by wireless radio links, and the like. These connectors may be configured to move freely and randomly and organize themselves arbitrarily, such that the topology of wireless network 108 may change rapidly.

Wireless network 108 may further employ a plurality of access technologies including 2nd (2G), 3rd (3G), 4th (4G) 5th (5G) generation radio access for cellular systems, WLAN, Wireless Router (WR) mesh, and the like. Access technologies such as 2G, 3G, 4G, 5G, and future access networks may enable wide area coverage for mobile computers, such as client computers 103-105 with various degrees of mobility. In one non-limiting example, wireless network 108 may enable a radio connection through a radio network access such as Global System for Mobil communication (GSM), General Packet Radio Services (GPRS), Enhanced Data GSM Environment (EDGE), code division multiple access (CDMA), time division multiple access (TDMA), Wideband Code Division Multiple Access (WCDMA), High Speed Downlink Packet Access (HSDPA), Long Term Evolution (LTE), and the like. In essence, wireless network 108 may include virtually any wireless communication mechanism by which information may travel between client computers 103-105 and another computer, network, a cloud-based network, a cloud instance, or the like.

Network 110 is configured to couple network computers with other computers, including, application server computer 116, file system management server computer 118, cloud computing environment 120, client computers 102, and client computers 103-105 through wireless network 108, or the like. Network 110 is enabled to employ any form of computer readable media for communicating information from one electronic device to another. Also, network 110 can include the Internet in addition to local area networks (LANs), wide area networks (WANs), direct connections, such as through a universal serial bus (USB) port, Ethernet port, other forms of computer-readable media, or any combination thereof. On an interconnected set of LANs, including those based on differing architectures and protocols, a router acts as a link between LANs, enabling messages to be sent from one to another. In addition, communication links within LANs typically include twisted wire pair or coaxial cable, while communication links between networks may utilize analog telephone lines, full or fractional dedicated digital lines including T1, T2, T3, and T4, or other carrier mechanisms including, for example, E-carriers, Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines (DSLs), wireless links including satellite links, or other communications links known to those skilled in the art. Moreover, communication links may further employ any of a variety of digital signaling technologies, including without limit, for example, DS-0, DS-1, DS-2, DS-3, DS-4, OC-3, OC-12, OC-48, or the like. Furthermore, remote computers and other related electronic devices could be remotely connected to either LANs or WANs via a modem and temporary telephone link. In one embodiment, network 110 may be configured to transport information of an Internet Protocol (IP).

Additionally, communication media typically embodies computer readable instructions, data structures, program modules, or other transport mechanism and includes any information non-transitory delivery media or transitory delivery media. By way of example, communication media includes wired media such as twisted pair, coaxial cable, fiber optics, wave guides, and other wired media and wireless media such as acoustic, RF, infrared, and other wireless media.

In some embodiments, cloud computing environment 120 may be one or more public or private cloud computing environments. In some embodiments, cloud computing environments may be provided by various vendors or developed internally or privately. Cloud computing environments typically provide virtualized network computers, virtualized storage (e.g., storage volumes), virtualized network interfaces, or the like. Various cloud computing environments may be assumed to have one or more APIs or interfaces that enable users or services to provision resources, provision storage, configure networking, monitoring usage/status, or the like. One of ordinary skill in the art will be well acquainted with public or private cloud computing environments.

Also, one embodiment of file system management server computer 118 is described in more detail below in conjunction with FIG. 3. Although FIG. 1 illustrates file system management server computer 118, or the like, as a single computer, the innovations or embodiments described herein are not so limited. For example, one or more functions of file system management server computer 118, or the like, may be distributed across one or more distinct network computers. Moreover, in one or more embodiments, file system management server computer 118 may be implemented using a plurality of network computers. Further, in one or more of the various embodiments, file system management server computer 118, or the like, may be implemented using one or more cloud instances in one or more cloud networks, such as, cloud computing environment 120. Accordingly, these innovations and embodiments are not to be construed as being limited to a single environment, and other configurations, and other architectures are also envisaged.

Illustrative Client Computer

FIG. 2 shows one embodiment of client computer 200 that may include many more or less components than those shown. Client computer 200 may represent, for example, one or more embodiment of mobile computers or client computers shown in FIG. 1.

Client computer 200 may include processor 202 in communication with memory 204 via bus 228. Client computer 200 may also include power supply 230, network interface 232, audio interface 256, display 250, keypad 252, illuminator 254, video interface 242, input/output interface 238, haptic interface 264, global positioning systems (GPS) receiver 258, open air gesture interface 260, temperature interface 262, camera(s) 240, projector 246, pointing device interface 266, processor-readable stationary storage device 234, and processor-readable removable storage device 236. Client computer 200 may optionally communicate with a base station (not shown), or directly with another computer. And in one embodiment, although not shown, a gyroscope may be employed within client computer 200 to measuring or maintaining an orientation of client computer 200.

Power supply 230 may provide power to client computer 200. A rechargeable or non-rechargeable battery may be used to provide power. The power may also be provided by an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the battery.

Network interface 232 includes circuitry for coupling client computer 200 to one or more networks, and is constructed for use with one or more communication protocols and technologies including, but not limited to, protocols and technologies that implement any portion of the OSI model for mobile communication (GSM), CDMA, time division multiple access (TDMA), UDP, TCP/IP, SMS, MMS, GPRS, WAP, UWB, WiMax, SIP/RTP, GPRS, EDGE, WCDMA, LTE, UMTS, OFDM, CDMA2000, EV-DO, HSDPA, 5G, or any of a variety of other wireless communication protocols. Network interface 232 is sometimes known as a transceiver, transceiving device, or network interface card (MC).

Audio interface 256 may be arranged to produce and receive audio signals such as the sound of a human voice. For example, audio interface 256 may be coupled to a speaker and microphone (not shown) to enable telecommunication with others or generate an audio acknowledgment for some action. A microphone in audio interface 256 can also be used for input to or control of client computer 200, e.g., using voice recognition, detecting touch based on sound, and the like.

Display 250 may be a liquid crystal display (LCD), gas plasma, electronic ink, light emitting diode (LED), Organic LED (OLED) or any other type of light reflective or light transmissive display that can be used with a computer. Display 250 may also include a touch interface 244 arranged to receive input from an object such as a stylus or a digit from a human hand, and may use resistive, capacitive, surface acoustic wave (SAW), infrared, radar, or other technologies to sense touch or gestures.

Projector 246 may be a remote handheld projector or an integrated projector that is capable of projecting an image on a remote wall or any other reflective object such as a remote screen.

Video interface 242 may be arranged to capture video images, such as a still photo, a video segment, an infrared video, or the like. For example, video interface 242 may be coupled to a digital video camera, a web-camera, or the like. Video interface 242 may comprise a lens, an image sensor, and other electronics. Image sensors may include a complementary metal-oxide-semiconductor (CMOS) integrated circuit, charge-coupled device (CCD), or any other integrated circuit for sensing light.

Keypad 252 may comprise any input device arranged to receive input from a user. For example, keypad 252 may include a push button numeric dial, or a keyboard. Keypad 252 may also include command buttons that are associated with selecting and sending images.

Illuminator 254 may provide a status indication or provide light. Illuminator 254 may remain active for specific periods of time or in response to event messages. For example, when illuminator 254 is active, it may back-light the buttons on keypad 252 and stay on while the client computer is powered. Also, illuminator 254 may back-light these buttons in various patterns when particular actions are performed, such as dialing another client computer. Illuminator 254 may also cause light sources positioned within a transparent or translucent case of the client computer to illuminate in response to actions.

Further, client computer 200 may also comprise hardware security module (HSM) 268 for providing additional tamper resistant safeguards for generating, storing or using security/cryptographic information such as, keys, digital certificates, passwords, passphrases, two-factor authentication information, or the like. In some embodiments, hardware security module may be employed to support one or more standard public key infrastructures (PKI), and may be employed to generate, manage, or store keys pairs, or the like. In some embodiments, HSM 268 may be a stand-alone computer, in other cases, HSM 268 may be arranged as a hardware card that may be added to a client computer.

Client computer 200 may also comprise input/output interface 238 for communicating with external peripheral devices or other computers such as other client computers and network computers. The peripheral devices may include an audio headset, virtual reality headsets, display screen glasses, remote speaker system, remote speaker and microphone system, and the like. Input/output interface 238 can utilize one or more technologies, such as Universal Serial Bus (USB), Infrared, WiFi, WiMax, Bluetooth™, and the like.

Input/output interface 238 may also include one or more sensors for determining geolocation information (e.g., GPS), monitoring electrical power conditions (e.g., voltage sensors, current sensors, frequency sensors, and so on), monitoring weather (e.g., thermostats, barometers, anemometers, humidity detectors, precipitation scales, or the like), or the like. Sensors may be one or more hardware sensors that collect or measure data that is external to client computer 200.

Haptic interface 264 may be arranged to provide tactile feedback to a user of the client computer. For example, the haptic interface 264 may be employed to vibrate client computer 200 in a particular way when another user of a computer is calling. Temperature interface 262 may be used to provide a temperature measurement input or a temperature changing output to a user of client computer 200. Open air gesture interface 260 may sense physical gestures of a user of client computer 200, for example, by using single or stereo video cameras, radar, a gyroscopic sensor inside a computer held or worn by the user, or the like. Camera 240 may be used to track physical eye movements of a user of client computer 200.

GPS transceiver 258 can determine the physical coordinates of client computer 200 on the surface of the Earth, which typically outputs a location as latitude and longitude values. GPS transceiver 258 can also employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), Enhanced Observed Time Difference (E-OTD), Cell Identifier (CI), Service Area Identifier (SAI), Enhanced Timing Advance (ETA), Base Station Subsystem (BSS), or the like, to further determine the physical location of client computer 200 on the surface of the Earth. It is understood that under different conditions, GPS transceiver 258 can determine a physical location for client computer 200. In one or more embodiments, however, client computer 200 may, through other components, provide other information that may be employed to determine a physical location of the client computer, including for example, a Media Access Control (MAC) address, IP address, and the like.

In at least one of the various embodiments, applications, such as, operating system 206, other client apps 224, web browser 226, or the like, may be arranged to employ geo-location information to select one or more localization features, such as, time zones, languages, currencies, calendar formatting, or the like. Localization features may be used in display objects, data models, data objects, user-interfaces, reports, as well as internal processes or databases. In at least one of the various embodiments, geo-location information used for selecting localization information may be provided by GPS 258. Also, in some embodiments, geolocation information may include information provided using one or more geolocation protocols over the networks, such as, wireless network 108 or network 111.

Human interface components can be peripheral devices that are physically separate from client computer 200, allowing for remote input or output to client computer 200. For example, information routed as described here through human interface components such as display 250 or keyboard 252 can instead be routed through network interface 232 to appropriate human interface components located remotely. Examples of human interface peripheral components that may be remote include, but are not limited to, audio devices, pointing devices, keypads, displays, cameras, projectors, and the like. These peripheral components may communicate over a Pico Network such as Bluetooth™, Zigbee™ and the like. One non-limiting example of a client computer with such peripheral human interface components is a wearable computer, which might include a remote pico projector along with one or more cameras that remotely communicate with a separately located client computer to sense a user's gestures toward portions of an image projected by the pico projector onto a reflected surface such as a wall or the user's hand.

A client computer may include web browser application 226 that is configured to receive and to send web pages, web-based messages, graphics, text, multimedia, and the like. The client computer's browser application may employ virtually any programming language, including a wireless application protocol messages (WAP), and the like. In one or more embodiments, the browser application is enabled to employ Handheld Device Markup Language (HDML), Wireless Markup Language (WML), WMLScript, JavaScript, Standard Generalized Markup Language (SGML), HyperText Markup Language (HTML), eXtensible Markup Language (XML), HTML5, and the like.

Memory 204 may include RAM, ROM, or other types of memory. Memory 204 illustrates an example of computer-readable storage media (devices) for storage of information such as computer-readable instructions, data structures, program modules or other data. Memory 204 may store BIOS 208 for controlling low-level operation of client computer 200. The memory may also store operating system 206 for controlling the operation of client computer 200. It will be appreciated that this component may include a general-purpose operating system such as a version of UNIX, or Linux®, or a specialized client computer communication operating system such as Windows Phone™, or the Apple Corporation's iOS or macOS® operating systems. The operating system may include, or interface various runtime engines, including Java virtual machines, or the like, that may enable control of hardware components or operating system operations via application programs supported by the various runtime engines.

Memory 204 may further include one or more data storage 210, which can be utilized by client computer 200 to store, among other things, applications 220 or other data. For example, data storage 210 may also be employed to store information that describes various capabilities of client computer 200. The information may then be provided to another device or computer based on any of a variety of methods, including being sent as part of a header during a communication, sent upon request, or the like. Data storage 210 may also be employed to store social networking information including address books, buddy lists, aliases, user profile information, or the like. Data storage 210 may further include program code, data, algorithms, and the like, for use by a processor, such as processor 202 to execute and perform actions. In one embodiment, at least some of data storage 210 might also be stored on another component of client computer 200, including, but not limited to, non-transitory processor-readable removable storage device 236, processor-readable stationary storage device 234, or even external to the client computer.

Applications 220 may include computer executable instructions which, when executed by client computer 200, transmit, receive, or otherwise process instructions and data. Applications 220 may include, for example, other client applications 224, web browser 226, or the like. Client computers may be arranged to exchange communications one or more servers.

Other examples of application programs include calendars, search programs, email client applications, IM applications, SMS applications, Voice Over Internet Protocol (VOIP) applications, contact managers, task managers, transcoders, database programs, word processing programs, security applications, spreadsheet programs, games, search programs, visualization applications, and so forth.

Additionally, in one or more embodiments (not shown in the figures), client computer 200 may include an embedded logic hardware device instead of a CPU, such as, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), Programmable Array Logic (PAL), or the like, or combination thereof. The embedded logic hardware device may directly execute its embedded logic to perform actions. Also, in one or more embodiments (not shown in the figures), client computer 200 may include one or more hardware micro-controllers instead of CPUs. In one or more embodiments, the one or more micro-controllers may directly execute their own embedded logic to perform actions and access its own internal memory and its own external Input and Output Interfaces (e.g., hardware pins or wireless transceivers) to perform actions, such as System On a Chip (SOC), or the like.

Illustrative Network Computer

FIG. 3 shows one embodiment of network computer 300 that may be included in a system implementing one or more of the various embodiments. Network computer 300 may include many more or less components than those shown in FIG. 3. However, the components shown are sufficient to disclose an illustrative embodiment for practicing these innovations. Network computer 300 may represent, for example, one or more embodiments of a file system management server computer such as file system management server computer 118, or the like, of FIG. 1.

Network computers, such as, network computer 300 may include a processor 302 that may be in communication with a memory 304 via a bus 328. In some embodiments, processor 302 may be comprised of one or more hardware processors, or one or more processor cores. In some cases, one or more of the one or more processors may be specialized processors designed to perform one or more specialized actions, such as, those described herein. Network computer 300 also includes a power supply 330, network interface 332, audio interface 356, display 350, keyboard 352, input/output interface 338, processor-readable stationary storage device 334, and processor-readable removable storage device 336. Power supply 330 provides power to network computer 300.

Network interface 332 includes circuitry for coupling network computer 300 to one or more networks, and is constructed for use with one or more communication protocols and technologies including, but not limited to, protocols and technologies that implement any portion of the Open Systems Interconnection model (OSI model), global system for mobile communication (GSM), code division multiple access (CDMA), time division multiple access (TDMA), user datagram protocol (UDP), transmission control protocol/Internet protocol (TCP/IP), Short Message Service (SMS), Multimedia Messaging Service (MMS), general packet radio service (GPRS), WAP, ultra-wide band (UWB), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), Session Initiation Protocol/Real-time Transport Protocol (SIP/RTP), 5G, or any of a variety of other wired and wireless communication protocols. Network interface 332 is sometimes known as a transceiver, transceiving device, or network interface card (NIC). Network computer 300 may optionally communicate with a base station (not shown), or directly with another computer.

Audio interface 356 is arranged to produce and receive audio signals such as the sound of a human voice. For example, audio interface 356 may be coupled to a speaker and microphone (not shown) to enable telecommunication with others or generate an audio acknowledgment for some action. A microphone in audio interface 356 can also be used for input to or control of network computer 300, for example, using voice recognition.

Display 350 may be a liquid crystal display (LCD), gas plasma, electronic ink, light emitting diode (LED), Organic LED (OLED) or any other type of light reflective or light transmissive display that can be used with a computer. In some embodiments, display 350 may be a handheld projector or pico projector capable of projecting an image on a wall or other object.

Network computer 300 may also comprise input/output interface 338 for communicating with external devices or computers not shown in FIG. 3. Input/output interface 338 can utilize one or more wired or wireless communication technologies, such as USB™, Firewire™, WiFi, WiMax, Thunderbolt™, Infrared, Bluetooth™, Zigbee™, serial port, parallel port, and the like.

Also, input/output interface 338 may also include one or more sensors for determining geolocation information (e.g., GPS), monitoring electrical power conditions (e.g., voltage sensors, current sensors, frequency sensors, and so on), monitoring weather (e.g., thermostats, barometers, anemometers, humidity detectors, precipitation scales, or the like), or the like. Sensors may be one or more hardware sensors that collect or measure data that is external to network computer 300. Human interface components can be physically separate from network computer 300, allowing for remote input or output to network computer 300. For example, information routed as described here through human interface components such as display 350 or keyboard 352 can instead be routed through the network interface 332 to appropriate human interface components located elsewhere on the network. Human interface components include any component that allows the computer to take input from, or send output to, a human user of a computer. Accordingly, pointing devices such as mice, styluses, track balls, or the like, may communicate through pointing device interface 358 to receive user input.

GPS transceiver 340 can determine the physical coordinates of network computer 300 on the surface of the Earth, which typically outputs a location as latitude and longitude values. GPS transceiver 340 can also employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), Enhanced Observed Time Difference (E-OTD), Cell Identifier (CI), Service Area Identifier (SAI), Enhanced Timing Advance (ETA), Base Station Subsystem (BSS), or the like, to further determine the physical location of network computer 300 on the surface of the Earth. It is understood that under different conditions, GPS transceiver 340 can determine a physical location for network computer 300. In one or more embodiments, however, network computer 300 may, through other components, provide other information that may be employed to determine a physical location of the client computer, including for example, a Media Access Control (MAC) address, IP address, and the like.

In at least one of the various embodiments, applications, such as, operating system 306, file system engine 322, recovery engine 324, monitoring engine 326, web services 329, or the like, may be arranged to employ geo-location information to select one or more localization features, such as, time zones, languages, currencies, currency formatting, calendar formatting, or the like. Localization features may be used in user interfaces, dashboards, reports, as well as internal processes or databases. In at least one of the various embodiments, geo-location information used for selecting localization information may be provided by GPS 340. Also, in some embodiments, geolocation information may include information provided using one or more geolocation protocols over the networks, such as, wireless network 108 or network 111.

Memory 304 may include Random Access Memory (RAM), Read-Only Memory (ROM), or other types of memory. Memory 304 illustrates an example of computer-readable storage media (devices) for storage of information such as computer-readable instructions, data structures, program modules or other data. Memory 304 stores a basic input/output system (BIOS) 308 for controlling low-level operation of network computer 300. The memory also stores an operating system 306 for controlling the operation of network computer 300. It will be appreciated that this component may include a general-purpose operating system such as a version of UNIX, or Linux®, or a specialized operating system such as Microsoft Corporation's Windows® operating system, or the Apple Corporation's macOS® operating system. The operating system may include, or interface with one or more virtual machine modules, such as, a Java virtual machine module that enables control of hardware components or operating system operations via Java application programs. Likewise, other runtime environments may be included.

Memory 304 may further include one or more data storage 310, which can be utilized by network computer 300 to store, among other things, applications 320 or other data. For example, data storage 310 may also be employed to store information that describes various capabilities of network computer 300. The information may then be provided to another device or computer based on any of a variety of methods, including being sent as part of a header during a communication, sent upon request, or the like. Data storage 310 may also be employed to store social networking information including address books, friend lists, aliases, user profile information, or the like. Data storage 310 may further include program code, data, algorithms, and the like, for use by a processor, such as processor 302 to execute and perform actions such as those actions described below. In one embodiment, at least some of data storage 310 might also be stored on another component of network computer 300, including, but not limited to, non-transitory media inside processor-readable removable storage device 336, processor-readable stationary storage device 334, or any other computer-readable storage device within network computer 300, or even external to network computer 300. Data storage 310 may include, for example, file storage 314, file system data 316, or the like.

Applications 320 may include computer executable instructions which, when executed by network computer 300, transmit, receive, or otherwise process messages (e.g., SMS, Multimedia Messaging Service (MMS), Instant Message (IM), email, or other messages), audio, video, and enable telecommunication with another user of another mobile computer. Other examples of application programs include calendars, search programs, email client applications, IM applications, SMS applications, Voice Over Internet Protocol (VOIP) applications, contact managers, task managers, transcoders, database programs, word processing programs, security applications, spreadsheet programs, games, search programs, and so forth. Applications 320 may include file system engine 322, recovery engine 324, monitoring engine 326, web services 329, or the like, that may be arranged to perform actions for embodiments described below. In one or more of the various embodiments, one or more of the applications may be implemented as modules or components of another application. Further, in one or more of the various embodiments, applications may be implemented as operating system extensions, modules, plugins, or the like.

Furthermore, in one or more of the various embodiments, file system engine 322, recovery engine 324, monitoring engine 326, web services 329, or the like, may be operative in a cloud-based computing environment. In one or more of the various embodiments, these applications, and others, that comprise the management platform may be executing within virtual machines or virtual servers that may be managed in a cloud-based based computing environment. In one or more of the various embodiments, in this context the applications may flow from one physical network computer within the cloud-based environment to another depending on performance and scaling considerations automatically managed by the cloud computing environment. Likewise, in one or more of the various embodiments, virtual machines or virtual servers dedicated to file system engine 322, recovery engine 324, monitoring engine 326, web services 329, or the like, may be provisioned and de-commissioned automatically.

Also, in one or more of the various embodiments, file system engine 322, recovery engine 324, monitoring engine 326, web services 329, or the like, may be located in virtual servers running in a cloud-based computing environment rather than being tied to one or more specific physical network computers.

Further, network computer 300 may also comprise hardware security module (HSM) 360 for providing additional tamper resistant safeguards for generating, storing or using security/cryptographic information such as, keys, digital certificates, passwords, passphrases, two-factor authentication information, or the like. In some embodiments, hardware security module may be employ to support one or more standard public key infrastructures (PKI), and may be employed to generate, manage, or store keys pairs, or the like. In some embodiments, HSM 360 may be a stand-alone network computer, in other cases, HSM 360 may be arranged as a hardware card that may be installed in a network computer.

Additionally, in one or more embodiments (not shown in the figures), network computer 300 may include an embedded logic hardware device instead of a CPU, such as, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), Programmable Array Logic (PAL), or the like, or combination thereof. The embedded logic hardware device may directly execute its embedded logic to perform actions. Also, in one or more embodiments (not shown in the figures), the network computer may include one or more hardware microcontrollers instead of a CPU. In one or more embodiments, the one or more microcontrollers may directly execute their own embedded logic to perform actions and access their own internal memory and their own external Input and Output Interfaces (e.g., hardware pins or wireless transceivers) to perform actions, such as System On a Chip (SOC), or the like.

Illustrative Logical System Architecture

FIG. 4 illustrates a logical architecture of system 400 for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments. In one or more of the various embodiments, one or more file systems, such as, file system 402 may be arranged to be communicatively coupled to one or more networks, such as, networks 408. Accordingly, in one or more of the various embodiments, one or more clients, such as, client computer 410 or client computer 412 may be arranged to access file system 402 over networks 408. In some embodiments, clients of file system 402 may include users, services, programs, computers, devices, or the like, that may be enabled to perform one or more data related operations, such as, creating, reading, updating, or deleting data (e.g., file system objects, documents, or the like) that may be stored in file system 402.

In some embodiments, file system 402 may comprise one or more file system management computers, such as file system management computer 404. Also, in one or more of the various embodiments, file systems, such as file system 402 may include one or more file system objects, such as file system object 406. In one or more of the various embodiments, file system object 406 may be considered to represent the various file system objects, documents objects, or the like, that may be stored in file system 402. In some embodiments, file system objects may include, files, documents, directories, folders, backups, snapshots, replication snapshots, replication information, or the like.

In one or more of the various embodiments, the implementation details that enable file system 402 to provide file system services may be hidden from clients, such that they may be arranged to use file system 402 the same way they use other conventional local or remote file systems. Accordingly, in one or more of the various embodiments, clients may be unaware that they are using a distributed file system that supports replicating files in distributed file systems using object-based data storage because file system engines or replication engines may be arranged to mimic the interface or behavior of one or more conventional file systems.

Also, while file system 402 is illustrated as using one file system management computer with one set of file system objects, these innovations are not so limited. Innovations herein contemplate file systems that include one or more file system management computers or one or more file system object data stores. In some embodiments, file system objects may be located remotely from one or more file system management computers. Also, a logical file system object store or file system may be spread across two or more cloud computing environments, storage clusters, or the like.

FIG. 5 illustrates a logical schematic of cloud computing environment 500 for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments. As introduced above, file systems may be hosted or implemented in a cloud computing environment, such as, cloud computing environment 500.

In one or more of the various embodiments, cluster 502 may be virtualized file system cluster hosted in cloud computing environment 500. In this example, the boundary of cluster 502 is illustrated using a dashed line to represent the dynamic or elastic nature of a cloud-hosted file system cluster. Accordingly, in some embodiments, the innovations disclosed herein anticipate various conventional cloud computing features, such as, dynamically provisioning components, such as, compute nodes, storage volumes, or the like. Also, in some embodiments, innovations may rely on other common features of cloud computing environments, such as, dynamic network configuration, grouping or association of various cloud environment components with other components, component/object tagging systems, component/object labeling, or the like. However, in some embodiments, for some cloud environments, one or more features may be missing or distinct/different from what may be conventionally expected. Accordingly, in some embodiments, file system engines, recovery engines, monitoring engines, or the like, may be arranged to include custom instructions or libraries, to provide one or more features that may be omitted from a given cloud computing environment. For example, in some embodiments, a cloud computing environment may omit a suitable tagging or labeling system. Thus, for this example, in some embodiments, file system engines, recovery engines, or monitoring engines, may be arranged to provide or implement alternative systems such as a custom tagging system that associated key value pairs with various components of the file system or cloud computing environment.

In one or more of the various embodiments, file systems host or implemented in cloud computing environments may be assumed to provide services similar as described above for FIG. 4. Thus, for brevity or clarity those descriptions are not repeated here.

In some embodiments, cluster 502 may include one or more cluster controllers, such as, cluster controller 504 and one or more storage nodes, such as, storage node 506, or the like. In one or more of the various embodiments, cluster controller may be the same or similar as file system management computer 404, or the like. Also, in some embodiments, cluster controller 504 may be considered to be a cluster node that is designated to provide some or all of the same services a file system management computer may provide.

In some embodiments, storage nodes, such as, storage node 506 may be considered to cluster nodes that may be arranged to rely on or coordinate with cluster controls, such as, cluster controller 404.

In one or more of the various embodiments, storage nodes may be associated with one or more storage volumes the may be provisioned from the cloud computing environment. In this example, the storage volumes are not shown but they may be considered to be logically associated with the storage nodes.

Note, in some embodiments, cluster controllers may be storage nodes that have been selected (or elected) to provide controller services. Thus, in some embodiments, cluster controller nodes may be associated with one or more storage volumes the same as storage nodes.

Further, in some embodiments, the health of the storage volumes associated cluster nodes may be monitored by one or more services, such as, monitoring/recovery service 508. In some embodiments, monitoring/recovery services may be hosted in separate nodes, compute instances, or serverless computer services, or the like, depending on the features of the cloud computing environment.

In one or more of the various embodiments, monitoring services may be configured to periodically examine file systems to determine if there may be unhealthy storage volumes associated with one or more nodes of file system cluster.

In one or more of the various embodiments, monitoring engines may be arranged to keep account of various metrics that may be associated with one or more nodes or storage volumes in file system clusters. In some embodiments, the particular metrics may vary depending on the cloud computing environment. Accordingly, in some embodiments, monitoring engines may be arranged to employ rules, instructions, or the like, provided from configuration information to determine which metrics to monitor as well as threshold values, conditions, or the like, that may indicate if storage volumes may be unhealthy.

FIG. 6 illustrates a logical schematic of cloud computing environment 600 for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments.

In one or more of the various embodiments, as described above, cloud computing environments may enable one or more computing instances that may be considered similar to storage nodes of a distributed file system.

In one or more of the various embodiments, nodes in cloud computing environments may be associated with one or more storage volumes similar or analogous to how storage volume devices may be physically coupled with physical storage nodes. However, rather than being physical storage devices (hard drives, solid state drives, or the like), storage volumes for cloud storage nodes may be virtualized storage volumes that may be communicatively coupled to compute instances in the cloud computing environment.

In one or more of the various embodiments, cloud computing environments may provide configuration tools, APIs, user interfaces, or the like, that enable users to configure or select storage volumes that may have different attributes (e.g., capacity, response time, I/O performance, encryption, or the like) based on the needs of an application of user. Accordingly, storage volumes may be logically associated with compute instances in cloud computing environment to provide private or logically local storage. Thus, in some embodiments, storage volumes that are associated with a compute instance may be considered virtual storage devices.

In one or more of the various embodiments, storage nodes, such as, storage node 602 may comprised compute instance 604 and one or more storage slots, such as, storage slot 602 and storage slot 610. In some embodiments, each storage slot may represent a specified amount of data storage capabilities that correspond to the storage capacity a storage node may contribute to the file system.

In one or more of the various embodiments, storage nodes may be configured to have one or more storage slots each with known attributes. In some embodiments, storage slots may be considered analogous to physical storage device slots of a physical server. For example, a physical storage node may include one or more physical hard drives that each may be installed in a physical slot of the physical storage node. In cloud computing environments, in some embodiments, virtualized compute instances may be configured to have one or more storage slots that each represent or include an allocation of storage capacity in the cloud computing environment.

Accordingly, in some embodiments, file system operations may consider storage slots in cloud computing environments similar to physical storage slots. Thus, in some embodiments, conventional distributed file system operations, such as, erasure encoding, striping, recovery, replication, mirroring, or the like, the leverage storage slots for organization may be performed in cloud based distributed file systems similar to as they may be in distributed file systems that are based on physical hardware.

In one or more of the various embodiments, virtualized storage slots, such as storage slots 602 and storage slot 606 may be associated with storage volumes, such as storage volume 610. In some embodiments, storage volumes may be storage capacity provided in cloud computing environments that may be analogous to storage devices. In some embodiments, various attributes of storage volumes may be defined, configured, or selected using one or more APIs, user interfaces, or the like, that may be provided by cloud providers that provide a given cloud computing environment. Accordingly, in some embodiments, file system engines, or the like, may be arranged to logically consider storage volumes similar to physical storage devices. For example, a physical storage node with four physical storage slots (each with one physical storage device) may be considered similarly to a virtualized storage node in a cloud computing environment that may be coupled with four virtualized storage slots that each associated with virtualized storage volume.

In one or more of the various embodiments, compute instances that may be coupled with storage volumes may be arranged exchange messages or data with its storage volumes via one or more data paths provided by the cloud computing environment. The particular underlying implementation of data paths may vary depending on the cloud provider, however they may be generally considered logical data busses that enable compute instances to interact with storage volumes similar to interactions with physical storage devices. In this example, data path 608 represent the one or more cloud computing environment features that enable compute instances to interact or access storage volumes in cloud computing environments.

In one or more of the various embodiments, cloud computing environments may enable the allocation or instantiation of storage volumes that may be unassociated with a particular compute instances. In some embodiments, this feature may enable storage volumes to be created in advance or otherwise reserved. Likewise, in some embodiments, cloud computing environments may enable storage volumes to be decoupled or disassociated from compute instances. In some cases, this may include discarding/reallocating unused storage volumes. Also, in some cases, decoupled storage volumes may be stored as part of an archival strategy, or the like. In this example, storage volume 612 and storage volume 614 represent allocated or instantiated storage volumes in a cloud computing environment that are not coupled with a compute instance. In terms of a distributed file system, uncoupled storage volumes may be considered unassociated with storage slots. Thus, in some embodiments, storage capacity that corresponds to uncoupled storage volumes may be unavailable to file systems.

Accordingly, in one or more of the various embodiments, associating a storage volume with a storage slot of a storage node in a file system cluster makes the storage capacity of the storage volume available to file system. Thus, in some embodiments, assigning a storage volume to a storage slot of storage node may be considered similar to installing a hardware storage device in a hardware server of a physical file system. For example, if the file system is arranged to automatically begin allocating data to newly installed hardware storage devices, similar actions may be performed if new storage volumes are assigned to storage slots. Note, the particular actions or behavior of file system engines, or the like, performed upon the discovery of new storage devices or new storage volumes may vary depending on the particular implementation of the file system, file system engines, or the like.

In some embodiments, in cloud computing environments various virtualized components, such as, compute instances, storage volumes, load balancers, firewalls, networks, or the like, may be dynamically provisioned or decommissioned enabling various advantageous features that cloud computing environments may be well known to provide. However, in some embodiments, components in cloud computing environments may experience errors related to failures of underlying hardware components, system degradation, software defects, or the like.

Accordingly, in some embodiments, distributed file systems in cloud computing environments may require monitoring or other management operations specifically directed to cloud computing environments to enable high availability, data security, data integrity, or the like, similar as on-premises (e.g., physical) distributed file systems.

For example, file systems may include monitoring engines that monitor the health of physical storage devices in storage node storage slots so they may be replaced as they degrade or are otherwise disabled. Similarly, in cloud computing environments, distributed file systems may include monitoring engines that monitor the health of virtualized storage volumes associated with storage slots of virtualized storage nodes. In practice, the health of a physical storage device may be evaluated based on one or more metrics associated with the performance of the physical devices. Likewise, in some embodiments, the health of virtualized storage volumes (hereinafter referred to as storage volumes) may be evaluated based on one or more metrics associated with cloud computing environments or the performance of the storage volumes. For example, in some embodiments, metrics such as reported I/O errors, capacity limits/quotas, latency/response times, or the like, may monitored by monitoring engines or file system engines to evaluate the health of storage volumes similar to how the health physical storage devices may be evaluated.

FIG. 7 illustrates a logical schematic of cloud computing storage volume 700 for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments. Individual cloud computing environments may have distinct or different underlying implementation of storage volumes. However, one of ordinary skill in the art will appreciate that they may assumed to have facilities that enable various automatic/programmatic operations including, instantiation, provisioning, decommissioning, coupling with compute instances, decoupling from compute instances, or the like. Likewise, cloud computing environments may provide one or more different types of storage volumes with various performance/capacity features not unlike how different types or models of storage devices may have different features. Accordingly, in some embodiments, file system engines may be arranged to automatically provision storage volumes having capacity or features based on the requirements of a given file system. For example, in some embodiments, the configuration information associated with a file system may include parameters, rules, instructions, or the like, that may determine the attributes of storage volumes that may be associated with the storage slots of the storage nodes in the file system.

Also, in some embodiments, storage volumes may be associated with meta-data that file systems may employ to manage storage volumes in cloud computing environments. In some embodiments, cloud computing environments may provide features that enable meta-data to be associated with various cloud computing components, including storage volumes. For example, a cloud computing environment may include one or more APIs for associating key-value pairs with various cloud computing components.

Likewise, in some embodiments, cloud computing environments may enable various queries related to meta-data and the associated components. For example, for some embodiments, a cloud computing environment may enable queries that determine one or more components (e.g., storage volumes) that may be associated particular meta-data values.

Thus, if such built-in facilities may be available, file systems may be arranged to employ these facilities to associate meta-data with storage volumes, compute instances, or the like. However, in some embodiments, file systems may be arranged to provide custom meta-data databases if the necessary facilities are absent or otherwise inconvenient. For example, if the query facilities of a meta-data system of a cloud computing environment is inadequate, file systems may be arranged to employ custom meta-data management facilities.

In this example, storage volume 702 may be represented as including data storage 704 and meta-data 706. In some embodiments, data storage 704 may represent the storage space or capacity associated with a particular storage volume. And, in some embodiments, meta-data 706 may represent one or more meta-data entries associated with the particular storage volume.

Generalized Operations

FIGS. 8-10 represent generalized operations for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments. In one or more of the various embodiments, processes 800, 900, and 1000 described in conjunction with FIGS. 8-10 may be implemented by or executed by one or more processors on a single network computer, such as network computer 300 of FIG. 3. In other embodiments, these processes, or portions thereof, may be implemented by or executed on a plurality of network computers, such as network computer 300 of FIG. 3. In yet other embodiments, these processes, or portions thereof, may be implemented by or executed on one or more virtualized computers, such as, those in a cloud-based environment. However, embodiments are not so limited and various combinations of network computers, client computers, or the like may be utilized. Further, in one or more of the various embodiments, the processes described in conjunction with FIGS. 8-10 may perform actions for managing cloud storage for distributed file systems in accordance with at least one of the various embodiments or architectures such as those described in conjunction with FIGS. 4-7. Further, in one or more of the various embodiments, some or all of the actions performed by processes 800, 900, and 1000 may be executed in part by file system engine 322, recovery engine 324, or monitoring engine 326.

FIG. 8 illustrates an overview flowchart for process 800 for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments. After a start block, at block 802, in one or more of the various embodiments, a cloud based distributed file system may be provided.

In one or more of the various embodiments, organizations may employ one or more install scripts, setup programs, configuration tools, or the like, to provide distributed file system in cloud computing environments. In some embodiments, the particular arrangement of storage nodes, clusters, storage slots, storage volumes, or the like, may vary depending on the needs of the organization.

At block 804, in one or more of the various embodiments, monitoring engines may be arranged to monitor the health on one or more storage volumes. In one or more of the various embodiments, file systems may be arranged to include one or more monitoring engines that evaluate one or more storage volumes to determine if there may storage volumes that may be eligible for replacement.

In one or more of the various embodiments, monitoring engines may be implemented as serverless-services, long running services, cron jobs, or the like. In some embodiments, monitoring engine may be incorporated in one or more other services or engines associated with the file system.

In one non-limiting example, a monitoring engine may be a serverless-service that wakes up periodically (as configured) to check on the health of storage volumes in the file system.

At decision block 806, in one or more of the various embodiments, if the health of the one or more storage volumes remains okay, control may loop back to block 804 for continued monitoring.

At block 808, in one or more of the various embodiments, recovery engines may be arranged to determine one or more dead/disabled storage volumes. In one or more of the various embodiments, if the monitoring engine determines one or more storage volumes that are eligible for replacement, recovery engines may be arranged to perform one or more actions that may identify one or more storage nodes, one or more storage slots, or one or more storage volumes that may be associated with one or more monitored metrics that may indicate that there may be a problem with one or more storage volumes.

At block 810, in one or more of the various embodiments, recovery engines may be arranged to one or more replacement storage volumes. In one or more of the various embodiments, if the recovery engine or monitoring engine determines storage volumes that requirement replacement, the recovery engine may execute one or more recovery jobs to make the necessary replacements.

At block 812, in one or more of the various embodiments, recovery engines may be arranged to attach the one or more replacement storage volumes to one or more storage nodes. In one or more of the various embodiments, recovery jobs may determine one or more replacement storage volumes. In some embodiments, some or all of the replacement storage volumes may be previously provisioned storage volumes or some or all of the replacement storage volumes may be provisioned and instantiated on-demand.

At block 814, in one or more of the various embodiments, recovery engines may be arranged to perform one or more recovery/balancing operations. In one or more of the various embodiments, if new storage volumes may be assigned to the storage slots of one or more storage nodes, the file system may detect the newly assigned replacement storage volumes. Accordingly, in some embodiments, the file system may be arranged to perform additional related to using the capacity of the replacement storage volumes. In some embodiments, these actions may be considered similar to the actions a physical file system may execute if a new/empty storage device is detected on a storage node.

Next, in one or more of the various embodiments, control may be returned to a calling process.

FIG. 9 illustrates a flowchart for process 900 for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments. After a start block, at decision block 902, in one or more of the various embodiments, if the health of storage volumes in the file system should be evaluated, control may flow to block 904; otherwise, control may loop back to decision block 902.

In one or more of the various embodiments, as described above, file systems may include a monitoring engine that regularly “wakes up” to evaluate if there may be one or more disabled storage volumes that may need replacing. In some embodiments, monitoring engines may be arranged to employ dynamic wake-up rules that may consider various file system metrics, such as, size, number of nodes, number of storage volumes, size or type or storage volumes, contractual service/quality agreements, time-of-day, activity levels, or the like. Accordingly, in some embodiments, monitoring engines or file system management server computers may be arranged to enforce monitoring policies based on configuration information to account for local requirements or local circumstances.

At block 904, in one or more of the various embodiments, monitoring engines may be arranged to query the file system cluster to obtain status information associated with one or more storage volumes in the file system cluster.

Alternatively, in one or more of the various embodiments, monitoring engines may be arranged to directly query one or more storage nodes to determine status information associated with its storage volumes.

In one or more of the various embodiments, status information may be based on discrete health status indicators, such as, a list of disabled storage volumes as determined by the storage nodes or file system. Alternatively, in some embodiments, the status information may include one or more metrics that may be collected by the storage nodes for its storage volumes. For example, in some embodiments, the status information may include metrics, such as, number of errors, errors broken down by type, error-rate, lifetime/age of storage volumes, access counts, activity measurements, diagnostic test results, or the like.

At block 906, in one or more of the various embodiments, monitoring engines may be arranged to evaluate the health of the one or more storage volumes based on the status information.

In one or more of the various embodiments, monitoring engines may be arranged to employ the status information to determine if one or more storage volumes may be considered disabled or otherwise eligible for being replaced. Similar, to determining how often to evaluate the health of storage volumes, monitoring engines may be arranged to enforce different evaluation policies for different file systems. In some embodiments, some file systems may have different standards for determining if storage volumes may be eligible for replacement. For example, one or more file systems may have risk management policies that require storage volumes to be replaced more often (or under different conditions) than one or more other file systems. Likewise, in some embodiments, different cloud computing environments may have different performance or reliability guarantees that require monitoring engines to employ different evaluation policies for different cloud computing environments. Accordingly, in some embodiments, monitoring engines, or the like, may employ rules, instructions, or the like, provided via configuration information to account for local requirements or local circumstances.

At decision block 908, in one or more of the various embodiments, if there may be one or more disabled storage volumes, control may flow to block 910; otherwise, control may loop back to decision block 902.

At block 910, in one or more of the various embodiments, recovery engines may be arranged to replace the one or more disabled storage volumes. In one or more of the various embodiments, monitoring engines may be arranged to trigger or otherwise initiate recovery jobs to replace the disabled storage volumes. In some embodiments, monitoring engines may be arranged to update one or more metrics, flags, or the like, that may be monitored by a recovery engine or file system management server computer. Thus, in some embodiments, if the updated values meet one or more conditions, the recovery operation may be initiated.

Next, in one or more of the various embodiments, control may be returned to a calling process.

FIG. 10 illustrates a flowchart for process 1000 for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments. After a start block, at block 1002, in one or more of the various embodiments, recovery engines or monitoring engines may be arranged to query the file system cluster to determine one or more disabled storage volumes.

In one or more of the various embodiments, recovery engines, or the like, may be arranged to query a file system management server computer that may be responsible for managing or controlling a file system cluster. In response to the query, in some embodiments, recovery engines may be provided a list of storage volumes that the file system may consider to be disabled. In some embodiments, the list may include identifiers of the storage volumes, storage nodes, storage slots, or the like, that may be associated with the disabled storage volumes.

In one or more of the various embodiments, the query may include one or more query expressions that enable a determination of storage slots that may be missing storage volumes. Thus, in some embodiments, the response to the query may include disabled storage volumes that remain associated with storage slots as well as a list of storage slots that are unassociated with healthy or disabled storage volumes. For example, if a new storage node is added to a file system cluster before its storage slots have been assigned storage volumes, the query response may identify these empty storage slots.

Alternatively, in some embodiments, recovery engines may be arranged to query one or more storage nodes directly to determine if individual storage nodes may report one or more disabled storage volumes. Likewise, in some embodiments, monitoring engines may maintain a running record of unhealthy or otherwise disabled storage volumes that may be queried by a recovery engine for determining the one or more disabled storage volumes.

In one or more of the various embodiments, recovery engines may be arranged to employ rules, instructions, or the like, provided via configuration information to determine how to form or structure the queries. For example, different cloud computing environments may require different formatting, parameters, or the like, to perform the queries to determine disabled storage volumes or missing storage volumes.

At block 1004, in one or more of the various embodiments, recovery engines may be arranged to tag the one or more disabled storage volumes as being disabled. In one or more of the various embodiments, before taking additional actions, recovery engines may be arranged to associate meta-data that indicates that the disabled storage volumes may be disabled. In some embodiments, this may include associating one or more key-pair values, such as, ‘HealthStatus=Disabled’ with the disabled storage volumes.

In one or more of the various embodiments, recovery engines may be arranged to tag the disabled storage volumes early in the recovery process to ensure that the disabled storage volumes may be identified if the recovery process unexpectedly crashes or unexpectedly terminates. Otherwise, in some circumstances, unhealthy storage volumes may be reused or otherwise not properly accounted if the recovery process terminates early.

At block 1006, in one or more of the various embodiments, recovery engines may be arranged to detach the one or more disabled storage volumes from one or more storage nodes. In one or more of the various embodiments, recovery engines may be arranged to execute one or more instructions in the cloud computing environment that decouple the disabled storage volumes from storage nodes. In one or more of the various embodiments, the particular instructions may be determined via configuration information that includes instructions for particular cloud computing environments.

In one or more of the various embodiments, decoupling disabled storage volumes from storage nodes includes removing or disassociating the one or more disabled storage volumes from one or more corresponding storage slots. This may be considered analogous to physically removing disabled storage devices from a physical storage node.

At block 1008, in one or more of the various embodiments, recovery engines may be arranged to determine one or more parameters of the one or more storage slots that may be associated with the disabled storage volumes.

In one or more of the various embodiments, storage slots for one or more storage nodes may have different requirements. For example, in some file systems, each storage slot of a storage node may require storage volumes that have the same capacity, performance, price, or the like. Note, in some file systems, or some embodiments, one or more storage nodes may include storage slots with non-uniform parameters. Likewise, in some embodiments, one or more file systems may be configured to support non-uniform storage nodes in a cluster rather than requiring them to be configured/provisioned the same.

Accordingly, in some embodiments, recovery engines may be arranged to query the file system, storage nodes, or the like, to determine the storage slot parameters associated with the one or more disabled or missing storage volumes. Alternatively, in some embodiments, storage slot parameters may be provided in responses to the one or more queries that may have been determined the unhealthy or missing storage volumes.

At block 1010, in one or more of the various embodiments, recovery engines may be arranged to query the cloud computing environment for one or more replacement storage volumes that may match the one or more storage slots.

In one or more of the various embodiments, cloud computing environments may provide various APIs that enable resources associated with users, accounts, or the like, to be queried based on their meta-data. Accordingly, in some embodiments, recovery engines may be arranged to query the cloud computing environment for storage volumes that have meta-data that indicates that they may be healthy and unassigned to a storage slot.

Alternatively, in one or more of the various embodiments, if a cloud computing environment does not provide query/meta-data facilities that may support such a query, recovery engines may be arranged to provide custom (native) query-able data stores that associate storage volumes with meta-data.

In one or more of the various embodiments, recovery engines may be arranged to employ the response to the query to determine if there may be one or more healthy storage volumes that may not be assigned to storage nodes. Accordingly, in some embodiments, recovery engines may be arranged to discover if there may be healthy storage volumes that may be ‘orphaned’ or otherwise unassigned. For example, for some embodiments, if a recovery process was interrupted, there may be one or more healthy storage volumes that may be provisioned but not assigned to a storage node or storage slot. Accordingly, in some embodiments, this step may discover one or more orphaned or otherwise lost health storage volumes that may be available.

At decision block 1012, in one or more of the various embodiments, if there may be healthy replacement storage volumes available, control may flow to block 1018; otherwise, control may flow block 1014.

In some cases, for some embodiments, there may be enough healthy storage volumes that have not been assigned to storage slot or storage nodes. Also, in some embodiments, there may some healthy storage volumes but not enough to fulfill the need. If so, recovery engines may be arranged to use the available healthy storage volumes and generate one or more new storage volumes to make up the difference between the number of available healthy storage volumes and the number of storage slots that may require healthy storage volumes.

At block 1014, in one or more of the various embodiments, recovery engines may be arranged to provision one or more replacement storage volumes that match the one or more storage slots.

Accordingly, in some embodiments, recovery engines may be arranged to send one or more instructions or messages to the cloud computing environment to enable the cloud computing environment to instantiate one or more storage volumes that may conform to the requirements of the storage slots that need storage volumes. For example, if two 8 TB storage volumes are required for two different storage slots, in some embodiments, a recovery engine may send the cloud computing environment one or more messages that include the credentials and parameters for provisioning the two 8 TB storage volumes.

At block 1016, in one or more of the various embodiments, recovery engines may be arranged to tag the one or more replacement volumes as being healthy storage volumes. In one or more of the various embodiments, recovery engines may be arranged to update the meta-data corresponding to the newly instantiated storage volumes to indicate that the storage volumes are healthy to guard against disruptions in the replacement process that may interrupt the process before the new storage volumes are associated with storage slots.

In one or more of the various embodiments, the actions for block 1014 and block 1016 may be combined into a single action depending on the APIs of the cloud computing environment. For example, in some embodiments, if the cloud computing environment APIs enables meta-data to be provided with the command to instantiate storage volumes, the new storage volumes may be automatically tagged as healthy as part of the instantiation process.

At block 1018, in one or more of the various embodiments, recovery engines may be arranged to assign the one or more healthy storage volumes to the one or more storage slots.

Here, in one or more of the various embodiments, the recovery engine may determine that there may be a sufficient number of healthy storage volumes (a combination of existing storage volumes or newly provisioned storage volumes) to assign to the one or more storage slots that may need new storage volumes. Accordingly, in some embodiments, the recovery engine may be arranged to associate one or more storage slots with compatible healthy storage volumes.

At this point, for some embodiments, the file system (e.g., recovery engines or file system engines) may automatically detect that new (empty) storage volumes have been added to one or more storage nodes. Accordingly, in some embodiments, the file system may initiate one or more actions to incorporate the new storage volumes into the file system. For example, this may include activating one or more rebalancing policies to restore the file system to normal/optimal operation.

Next, in one or more of the various embodiments, control may be returned to a calling process.

FIG. 11 illustrates a flowchart for process 1100 for managing cloud storage for distributed file systems in accordance with one or more of the various embodiments. After a start block, at decision block 1102, in one or more of the various embodiments, if recovery engines or monitoring engines determine that there may be one or more missing storage volumes, control may flow to block 1104; otherwise, control may be returned to a calling process.

At block 1104, in one or more of the various embodiments, recovery engines or monitoring engines may be arranged to query the file system cluster to determine one or more missing storage volumes.

In one or more of the various embodiments, recovery engines, or the like, may be arranged to query a file system management server computer that may be responsible for managing or controlling a file system cluster. In response to the query, in some embodiments, recovery engines may be provided a list of storage volumes that the file system or cloud computing environment may consider to be missing. In some embodiments, the list may include identifiers of the storage volumes, storage nodes, storage slots, or the like, that may be associated with the missing storage volumes.

Alternatively, in some embodiments, recovery engines may be arranged to query one or more storage nodes directly to determine if individual storage nodes may report one or more missing storage volumes.

In one or more of the various embodiments, missing storage volumes may be missing or otherwise absent from the cloud computing environment. Accordingly, in some embodiments, recovery engines may be arranged to direct queries to the cloud computing environment to determine the one or more missing storage volumes that may be unknown, missing, or the like.

At block 1106, in one or more of the various embodiments, recovery engines may be arranged to generate metadata for replacing the one or more missing storage volumes. In some embodiments, recovery engines may be arranged to generate replacement metadata based on storage volume information collected from the storage nodes associated with the missing storage volumes. In some embodiments, the metadata that describes or defines the storage characteristics (e.g., data volume information) may be determined based on one or more of storage volume information provided by the file system management server or storage information provided by the storage nodes associated with the missing storage volumes. For example, in some embodiments, storage information may include information regarding other storage volumes on the storage nodes associated with the missing storage volumes. Likewise, in some embodiments, storage information provided by the file system management server may include information describing the storage volumes that were originally provisioned for the storage nodes associated with the missing storage volumes.

At block 1108, in one or more of the various embodiments, recovery engines may be arranged to provision one or more storage volumes to replace the missing storage volumes. In some embodiments, recovery engines may be arranged to employ one or more of the replacement metadata or storage volume information to determine provisioning parameters that may be provided to the cloud computing environment.

At block 1110, in one or more of the various embodiments, recovery engines may be arranged to associate the replacement metadata with the one or more replacement storage volumes. In some embodiments, this may include associating the one or more replacement storage volumes with the cluster, the storage node, tagging the replacement volume as a healthy volume, or the like, similar to other provisioned storage volumes in the cluster.

At block 1112, in one or more of the various embodiments, recovery engines may be arranged to couple the replacement storage volumes with the storage nodes that may be missing storage volumes.

Next, in some embodiments, control may be returned to a calling process.

It will be understood that each block in each flowchart illustration, and combinations of blocks in each flowchart illustration, can be implemented by computer program instructions. These program instructions may be provided to a processor to produce a machine, such that the instructions, which execute on the processor, create means for implementing the actions specified in each flowchart block or blocks. The computer program instructions may be executed by a processor to cause a series of operational steps to be performed by the processor to produce a computer-implemented process such that the instructions, which execute on the processor, provide steps for implementing the actions specified in each flowchart block or blocks. The computer program instructions may also cause at least some of the operational steps shown in the blocks of each flowchart to be performed in parallel. Moreover, some of the steps may also be performed across more than one processor, such as might arise in a multi-processor computer system. In addition, one or more blocks or combinations of blocks in each flowchart illustration may also be performed concurrently with other blocks or combinations of blocks, or even in a different sequence than illustrated without departing from the scope or spirit of the invention.

Accordingly, each block in each flowchart illustration supports combinations of means for performing the specified actions, combinations of steps for performing the specified actions and program instruction means for performing the specified actions. It will also be understood that each block in each flowchart illustration, and combinations of blocks in each flowchart illustration, can be implemented by special purpose hardware based systems, which perform the specified actions or steps, or combinations of special purpose hardware and computer instructions. The foregoing example should not be construed as limiting or exhaustive, but rather, an illustrative use case to show an implementation of at least one of the various embodiments of the invention.

Further, in one or more embodiments (not shown in the figures), the logic in the illustrative flowcharts may be executed using an embedded logic hardware device instead of a CPU, such as, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), Programmable Array Logic (PAL), or the like, or combination thereof. The embedded logic hardware device may directly execute its embedded logic to perform actions. In one or more embodiments, a microcontroller may be arranged to directly execute its own embedded logic to perform actions and access its own internal memory and its own external Input and Output Interfaces (e.g., hardware pins or wireless transceivers) to perform actions, such as System On a Chip (SOC), or the like.

Claims

1. A method for managing data in a file system over a network using one or more processors that execute instructions to perform actions, comprising: providing the file system that includes a plurality of storage nodes and a plurality of storage volumes, wherein each storage node is coupled to a portion of the plurality of storage volumes, and wherein each storage node is a compute instance in a cloud computing environment and each storage volume is a data store in the cloud computing environment;monitoring one or more metrics associated with each storage volume; andin response to the one or more metrics exceeding one or more threshold values, performing further actions, including: determining one or more storage volumes in the plurality of storage volumes that are disabled or missing based on the one or more metrics that exceed the one or more threshold values and one or more parameters for one or more storage slots associated with each of the disabled or missing one or more storage volumes;updating metadata associated with the disabled one or more storage volumes to indicate that the disabled one or more storage volumes are also unhealthy, wherein the one or more disabled storage volumes are tagged as disabled;decoupling the one or more unhealthy storage volumes from one or more storage nodes coupled to the one or more unhealthy storage volumes;determining one or more replacement storage volumes based on the metadata associated with the one or more unhealthy storage volumes, one or more native queries that associate the metadata with the one or more unhealthy storage volumes, one or more queries for orphaned healthy storage volumes, and the one or more parameters for the one or more storage slots associated with each of the disabled one or more storage volumes, wherein each replacement storage volume matches the one or more parameters that correspond to at least one of the storage slots;updating other metadata associated with the one or more replacement storage volumes to indicate that the one or more replacement storage volumes are healthy storage volumes;coupling the one or more healthy storage volumes with the one or more storage nodes that were coupled to the one or more unhealthy storage volumes;generating replacement metadata for the missing one or more storage volumes, wherein the replacement metadata is employed to generate and provision one or more replacement storage volumes; andassociating the one or more replacement storage volumes with the plurality of storage nodes, wherein the one or more replacement storage volumes are tagged as healthy and coupled to the one or more storage nodes, and wherein one or more portions of the healthy replacement storage volumes are assigned to each storage slot that lacks one or more healthy storage volumes.
2. The method of claim 1, wherein determining the one or more replacement storage volumes, further comprises: generating a query based on the metadata associated with the one or more unhealthy storage volumes;employing the query to determine one or more uncoupled healthy storage volumes in the cloud computing environment, wherein the metadata associated with the one or more unhealthy storage volumes matches the other metadata associated with the one or more uncoupled preexisting healthy storage volumes; andproviding the one or more healthy storage volumes as at least a portion of the one or more replacement storage volumes.
3. The method of claim 1, wherein determining the one or more replacement storage volumes, further comprises: in response to a quantity of the one or more unhealthy storage volumes exceeding a quantity of one or more preexisting uncoupled healthy storage volumes, performing further actions, including: provisioning one or more additional uncoupled storage volumes from the cloud computing environment that match the one or more unhealthy storage volumes;updating metadata associated with the one or more uncoupled storage volumes to indicate that the one or more additional uncoupled storage volumes are uncoupled healthy storage volumes; andproviding the one or more uncoupled healthy storage volumes as the one or more replacement storage volumes.
4. The method of claim 1, wherein coupling the one or more healthy storage volumes with the one or more storage nodes, further comprises: determining the one or more storage slots associated with the one or more storage nodes based on the file system, wherein each storage slot corresponds to a fraction of a storage capacity of the file system; andassociating the one or more healthy storage volumes with the one or more storage slots, wherein each healthy storage volume is employed to provide the fraction of the storage capacity that corresponds to its associated storage slot.
5. The method of claim 1, wherein monitoring the one or more metrics associated with each storage volume, further comprises, querying each storage node of the plurality of storage nodes for one or more values of the one or more metrics that are associated a portion of the plurality of storage volumes that are coupled to the queried storage node, wherein the one or more values of the one or more metrics are based on error information provided to each storage node by the cloud computing environment.
6. The method of claim 1, wherein the metadata associated with the one or more storage volumes, further comprises, one or more of a storage cluster identifier, a storage slot identifier, and a field for storing a value that indicates that a storage volume is healthy or unhealthy.
7. The method of claim 1, wherein determining the one or more replacement storage volumes, further comprises: determining one or more storage volumes that are missing from the plurality of storage volumes based on the one or more metrics;providing storage volume information associated with the one or more missing storage volumes based on querying the one or more storage nodes;generating replacement metadata based on the storage volume information;provisioning one or more additional uncoupled storage volumes from the cloud computing environment based on the replacement metadata;updating metadata associated with the one or more additional uncoupled storage volumes to indicate that the one or more additional uncoupled storage volumes are uncoupled healthy storage volumes; andproviding the one or more uncoupled healthy storage volumes as the one or more replacement storage volumes.
8. A system for managing data in a file system comprising: a network computer, comprising: a memory that stores at least instructions; andone or more processors that execute instructions that perform actions, including: providing the file system that includes a plurality of storage nodes and a plurality of storage volumes, wherein each storage node is coupled to a portion of the plurality of storage volumes, and wherein each storage node is a compute instance in a cloud computing environment and each storage volume is a data store in the cloud computing environment;monitoring one or more metrics associated with each storage volume; andin response to the one or more metrics exceeding one or more threshold values, performing further actions, including: determining one or more storage volumes in the plurality of storage volumes that are disabled or missing based on the one or more metrics that exceed the one or more threshold values and one or more parameters for one or more storage slots associated with each of the disabled or missing one or more storage volumes;updating metadata associated with the disabled one or more storage volumes to indicate that the disabled one or more storage volumes are also unhealthy;decoupling the one or more unhealthy storage volumes from one or more storage nodes coupled to the one or more unhealthy storage volumes;determining one or more replacement storage volumes based on the metadata associated with the one or more unhealthy storage volumes, one or more native queries that associate the metadata with the one or more unhealthy storage volumes, one or more queries for orphaned healthy storage volumes, and the one or more parameters for the one or more storage slots associated with each of the disabled one or more storage volumes, wherein each replacement storage volume matches the one or more parameters that correspond to at least one of the storage slots;updating other metadata associated with the one or more replacement storage volumes to indicate that the one or more replacement storage volumes are healthy storage volumes;coupling the one or more healthy storage volumes with the one or more storage nodes that were coupled to the one or more unhealthy storage volumes;generating replacement metadata for the missing one or more storage volumes, wherein the replacement metadata is employed to generate and provision one or more replacement storage volumes; andassociating the one or more replacement storage volumes with the plurality of storage nodes, wherein the one or more replacement storage volumes are tagged as healthy and coupled to the one or more storage nodes, and wherein one or more portions of the healthy replacement storage volumes are assigned to each storage slot that lacks one or more healthy storage volumes; anda client computer, comprising: a memory that stores at least instructions; andone or more processors that execute instructions that enable performance of actions, including: providing one or more of the one or more threshold values.
9. The system of claim 8, wherein determining the one or more replacement storage volumes, further comprises: generating a query based on the metadata associated with the one or more unhealthy storage volumes;employing the query to determine one or more uncoupled healthy storage volumes in the cloud computing environment, wherein the metadata associated with the one or more unhealthy storage volumes matches the other metadata associated with the one or more uncoupled preexisting healthy storage volumes; andproviding the one or more healthy storage volumes as at least a portion of the one or more replacement storage volumes.
10. The system of claim 8, wherein determining the one or more replacement storage volumes, further comprises: in response to a quantity of the one or more unhealthy storage volumes exceeding a quantity of one or more preexisting uncoupled healthy storage volumes, performing further actions, including: provisioning one or more additional uncoupled storage volumes from the cloud computing environment that match the one or more unhealthy storage volumes;updating metadata associated with the one or more uncoupled storage volumes to indicate that the one or more additional uncoupled storage volumes are uncoupled healthy storage volumes; andproviding the one or more uncoupled healthy storage volumes as the one or more replacement storage volumes.
11. The system of claim 8, wherein coupling the one or more healthy storage volumes with the one or more storage nodes, further comprises: determining the one or more storage slots associated with the one or more storage nodes based on the file system, wherein each storage slot corresponds to a fraction of a storage capacity of the file system; andassociating the one or more healthy storage volumes with the one or more storage slots, wherein each healthy storage volume is employed to provide the fraction of the storage capacity that corresponds to its associated storage slot.
12. The system of claim 8, wherein monitoring the one or more metrics associated with each storage volume, further comprises, querying each storage node of the plurality of storage nodes for one or more values of the one or more metrics that are associated a portion of the plurality of storage volumes that are coupled to the queried storage node, wherein the one or more values of the one or more metrics are based on error information provided to each storage node by the cloud computing environment.
13. The system of claim 8, wherein the metadata associated with the one or more storage volumes, further comprises, one or more of a storage cluster identifier, a storage slot identifier, and a field for storing a value that indicates that a storage volume is healthy or unhealthy.
14. The system of claim 8, wherein determining the one or more replacement storage volumes, further comprises: determining one or more storage volumes that are missing from the plurality of storage volumes based on the one or more metrics;providing storage volume information associated with the one or more missing storage volumes based on querying the one or more storage nodes;generating replacement metadata based on the storage volume information;provisioning one or more additional uncoupled storage volumes from the cloud computing environment based on the replacement metadata;updating metadata associated with the one or more additional uncoupled storage volumes to indicate that the one or more additional uncoupled storage volumes are uncoupled healthy storage volumes; andproviding the one or more uncoupled healthy storage volumes as the one or more replacement storage volumes.
15. A processor readable non-transitory storage media that includes instructions for managing data in a file system over a network, wherein execution of the instructions by one or more processors on one or more network computers performs actions, comprising: providing the file system that includes a plurality of storage nodes and a plurality of storage volumes, wherein each storage node is coupled to a portion of the plurality of storage volumes, and wherein each storage node is a compute instance in a cloud computing environment and each storage volume is a data store in the cloud computing environment;monitoring one or more metrics associated with each storage volume; andin response to the one or more metrics exceeding one or more threshold values, performing further actions, including: determining one or more storage volumes in the plurality of storage volumes that are disabled or missing based on the one or more metrics that exceed the one or more threshold values and one or more parameters for one or more storage slots associated with each of the disabled or missing one or more storage volumes;updating metadata associated with the disabled one or more storage volumes to indicate that the disabled one or more storage volumes are also unhealthy;decoupling the one or more unhealthy storage volumes from one or more storage nodes coupled to the one or more unhealthy storage volumes;determining one or more replacement storage volumes based on the metadata associated with the one or more unhealthy storage volumes, one or more native queries that associate the metadata with the one or more unhealthy storage volumes, one or more queries for orphaned healthy storage volumes, and the one or more parameters for the one or more storage slots associated with each of the disabled one or more storage volumes, wherein each replacement storage volume matches the one or more parameters that correspond to at least one of the storage slots;updating other metadata associated with the one or more replacement storage volumes to indicate that the one or more replacement storage volumes are healthy storage volumes;coupling the one or more healthy storage volumes with the one or more storage nodes that were coupled to the one or more unhealthy storage volumes;generating replacement metadata for the missing one or more storage volumes, wherein the replacement metadata is employed to generate and provision one or more replacement storage volumes; andassociating the one or more replacement storage volumes with the plurality of storage nodes, wherein the one or more replacement storage volumes are tagged as healthy and coupled to the one or more storage nodes, and wherein one or more portions of the healthy replacement storage volumes are assigned to each storage slot that lacks one or more healthy storage volumes.
16. The media of claim 15, wherein determining the one or more replacement storage volumes, further comprises: generating a query based on the metadata associated with the one or more unhealthy storage volumes;employing the query to determine one or more uncoupled healthy storage volumes in the cloud computing environment, wherein the metadata associated with the one or more unhealthy storage volumes matches the other metadata associated with the one or more uncoupled preexisting healthy storage volumes; andproviding the one or more healthy storage volumes as at least a portion of the one or more replacement storage volumes.
17. The media of claim 15, wherein determining the one or more replacement storage volumes, further comprises: in response to a quantity of the one or more unhealthy storage volumes exceeding a quantity of one or more preexisting uncoupled healthy storage volumes, performing further actions, including: provisioning one or more additional uncoupled storage volumes from the cloud computing environment that match the one or more unhealthy storage volumes;updating metadata associated with the one or more uncoupled storage volumes to indicate that the one or more additional uncoupled storage volumes are uncoupled healthy storage volumes; andproviding the one or more uncoupled healthy storage volumes as the one or more replacement storage volumes.
18. The media of claim 15, wherein coupling the one or more healthy storage volumes with the one or more storage nodes, further comprises: determining the one or more storage slots associated with the one or more storage nodes based on the file system, wherein each storage slot corresponds to a fraction of a storage capacity of the file system; andassociating the one or more healthy storage volumes with the one or more storage slots, wherein each healthy storage volume is employed to provide the fraction of the storage capacity that corresponds to its associated storage slot.
19. The media of claim 15, wherein monitoring the one or more metrics associated with each storage volume, further comprises, querying each storage node of the plurality of storage nodes for one or more values of the one or more metrics that are associated a portion of the plurality of storage volumes that are coupled to the queried storage node, wherein the one or more values of the one or more metrics are based on error information provided to each storage node by the cloud computing environment.
20. The media of claim 15, wherein the metadata associated with the one or more storage volumes, further comprises, one or more of a storage cluster identifier, a storage slot identifier, and a field for storing a value that indicates that a storage volume is healthy or unhealthy.
21. The media of claim 15, wherein determining the one or more replacement storage volumes, further comprises: determining one or more storage volumes that are missing from the plurality of storage volumes based on the one or more metrics;providing storage volume information associated with the one or more missing storage volumes based on querying the one or more storage nodes;generating replacement metadata based on the storage volume information;provisioning one or more additional uncoupled storage volumes from the cloud computing environment based on the replacement metadata;updating metadata associated with the one or more additional uncoupled storage volumes to indicate that the one or more additional uncoupled storage volumes are uncoupled healthy storage volumes; andproviding the one or more uncoupled healthy storage volumes as the one or more replacement storage volumes.
22. A network computer for managing data in a file system, comprising: a memory that stores at least instructions; andone or more processors that execute instructions that perform actions, including: providing the file system that includes a plurality of storage nodes and a plurality of storage volumes, wherein each storage node is coupled to a portion of the plurality of storage volumes, and wherein each storage node is a compute instance in a cloud computing environment and each storage volume is a data store in the cloud computing environment;monitoring one or more metrics associated with each storage volume; andin response to the one or more metrics exceeding one or more threshold values, performing further actions, including: determining one or more storage volumes in the plurality of storage volumes that are disabled or missing based on the one or more metrics that exceed the one or more threshold values and one or more parameters for one or more storage slots associated with each of the disabled or missing one or more storage volumes;updating metadata associated with the disabled one or more storage volumes to indicate that the disabled one or more storage volumes are also unhealthy;decoupling the one or more unhealthy storage volumes from one or more storage nodes coupled to the one or more unhealthy storage volumes;determining one or more replacement storage volumes based on the metadata associated with the one or more unhealthy storage volumes, one or more native queries that associate the metadata with the one or more unhealthy storage volumes, one or more queries for orphaned healthy storage volumes, and the one or more parameters for the one or more storage slots associated with each of the disabled one or more storage volumes, wherein each replacement storage volume matches the one or more parameters that correspond to at least one of the storage slots;updating other metadata associated with the one or more replacement storage volumes to indicate that the one or more replacement storage volumes are healthy storage volumes;coupling the one or more healthy storage volumes with the one or more storage nodes that were coupled to the one or more unhealthy storage volumes;generating replacement metadata for the missing one or more storage volumes, wherein the replacement metadata is employed to generate and provision one or more replacement storage volumes; andassociating the one or more replacement storage volumes with the plurality of storage nodes, wherein the one or more replacement storage volumes are tagged as healthy and coupled to the one or more storage nodes, and wherein one or more portions of the healthy replacement storage volumes are assigned to each storage slot that lacks one or more healthy storage volumes.
23. The network computer of claim 22, wherein determining the one or more replacement storage volumes, further comprises: generating a query based on the metadata associated with the one or more unhealthy storage volumes;employing the query to determine one or more uncoupled healthy storage volumes in the cloud computing environment, wherein the metadata associated with the one or more unhealthy storage volumes matches the other metadata associated with the one or more uncoupled preexisting healthy storage volumes; andproviding the one or more healthy storage volumes as at least a portion of the one or more replacement storage volumes.
24. The network computer of claim 22, wherein determining the one or more replacement storage volumes, further comprises: in response to a quantity of the one or more unhealthy storage volumes exceeding a quantity of one or more preexisting uncoupled healthy storage volumes, performing further actions, including: provisioning one or more additional uncoupled storage volumes from the cloud computing environment that match the one or more unhealthy storage volumes;updating metadata associated with the one or more uncoupled storage volumes to indicate that the one or more additional uncoupled storage volumes are uncoupled healthy storage volumes; andproviding the one or more uncoupled healthy storage volumes as the one or more replacement storage volumes.
25. The network computer of claim 22, wherein coupling the one or more healthy storage volumes with the one or more storage nodes, further comprises: determining the one or more storage slots associated with the one or more storage nodes based on the file system, wherein each storage slot corresponds to a fraction of a storage capacity of the file system; andassociating the one or more healthy storage volumes with the one or more storage slots, wherein each healthy storage volume is employed to provide the fraction of the storage capacity that corresponds to its associated storage slot.
26. The network computer of claim 22, wherein monitoring the one or more metrics associated with each storage volume, further comprises, querying each storage node of the plurality of storage nodes for one or more values of the one or more metrics that are associated a portion of the plurality of storage volumes that are coupled to the queried storage node, wherein the one or more values of the one or more metrics are based on error information provided to each storage node by the cloud computing environment.
27. The network computer of claim 22, wherein the metadata associated with the one or more storage volumes, further comprises, one or more of a storage cluster identifier, a storage slot identifier, and a field for storing a value that indicates that a storage volume is healthy or unhealthy.
28. The network computer of claim 22, wherein determining the one or more replacement storage volumes, further comprises: determining one or more storage volumes that are missing from the plurality of storage volumes based on the one or more metrics;providing storage volume information associated with the one or more missing storage volumes based on querying the one or more storage nodes;generating replacement metadata based on the storage volume information;provisioning one or more additional uncoupled storage volumes from the cloud computing environment based on the replacement metadata;updating metadata associated with the one or more additional uncoupled storage volumes to indicate that the one or more additional uncoupled storage volumes are uncoupled healthy storage volumes; andproviding the one or more uncoupled healthy storage volumes as the one or more replacement storage volumes.

US Referenced Citations (339)

Number	Name	Date	Kind
5165031	Pruul et al.	Nov 1992	A
5283875	Gibson et al.	Feb 1994	A
5319773	Britton et al.	Jun 1994	A
5410684	Ainsworth et al.	Apr 1995	A
5410719	Shackleford	Apr 1995	A
5442561	Yoshizawa et al.	Aug 1995	A
5953719	Kleewein et al.	Sep 1999	A
6236996	Bapat et al.	May 2001	B1
6385641	Jiang et al.	May 2002	B1
6415283	Conklin	Jul 2002	B1
6496944	Hsiao et al.	Dec 2002	B1
6529998	Yochai et al.	Mar 2003	B1
6560615	Zayas et al.	May 2003	B1
6772435	Thexton et al.	Aug 2004	B1
6874130	Baweja et al.	Mar 2005	B1
6892211	Hitz et al.	May 2005	B2
6965903	Agarwal et al.	Nov 2005	B1
6965936	Wipfel et al.	Nov 2005	B1
7165158	Yagawa	Jan 2007	B1
7213040	Stokes et	May 2007	B1
7330948	Deguchi et al.	Feb 2008	B2
7467333	Keeton et al.	Dec 2008	B2
7594138	Abdulvahid	Sep 2009	B2
7636743	Erofeev	Dec 2009	B2
7693876	Hackworth et al.	Apr 2010	B2
7757056	Fair	Jul 2010	B1
7761456	Cram et al.	Jul 2010	B1
7844580	Srivastava et al.	Nov 2010	B2
7933870	Webster	Apr 2011	B1
7937421	Mikesell et al.	May 2011	B2
7962709	Agrawal	Jun 2011	B2
7966293	Owara et al.	Jun 2011	B1
8027827	Bitar et al.	Sep 2011	B2
8046378	Zhuge et al.	Oct 2011	B1
8108429	Sim-Tang et al.	Jan 2012	B2
8296312	Leung et al.	Oct 2012	B1
8341540	Haynes et al.	Dec 2012	B1
8355407	Wookey et al.	Jan 2013	B2
8364648	Sim-Tang	Jan 2013	B1
8423733	Ozdemir	Apr 2013	B1
8423821	Keith, Jr.	Apr 2013	B1
8448170	Wipfel et al.	May 2013	B2
8463825	Harty et al.	Jun 2013	B1
8489656	Erofeev	Jul 2013	B2
8504733	Iyer et al.	Aug 2013	B1
8515911	Zhou et al.	Aug 2013	B1
8612404	Bone et al.	Dec 2013	B2
8612488	Subramanya et al.	Dec 2013	B1
8645323	Jackiewicz et al.	Feb 2014	B2
8661447	Olliff et al.	Feb 2014	B1
8725691	Natanzon	May 2014	B1
8776050	Plouffe et al.	Jul 2014	B2
8782655	Blanding et al.	Jul 2014	B2
8806154	Gupta et al.	Aug 2014	B1
8838887	Burke et al.	Sep 2014	B1
8838931	Marshak et al.	Sep 2014	B1
8849764	Long et al.	Sep 2014	B1
8849809	Seshadri	Sep 2014	B1
8868797	Kirac et al.	Oct 2014	B1
8924364	Zhong et al.	Dec 2014	B1
8972694	Dolan et al.	Mar 2015	B1
9015214	Nishida et al.	Apr 2015	B2
9026765	Marshak et al.	May 2015	B1
9031994	Cao et al.	May 2015	B1
9032170	Vaghani	May 2015	B2
9047017	Dolan et al.	Jun 2015	B1
9141633	Li et al.	Sep 2015	B1
9143379	Berger et al.	Sep 2015	B1
9158653	Gold	Oct 2015	B2
9171145	Dash et al.	Oct 2015	B2
9244975	Das et al.	Jan 2016	B2
9244976	Zhang et al.	Jan 2016	B1
9361187	Jarvis	Jun 2016	B2
9384252	Akirav et al.	Jul 2016	B2
9459804	Natanzon et al.	Oct 2016	B1
9501487	Yuan et al.	Nov 2016	B1
9547560	Lee	Jan 2017	B1
9600193	Ahrens et al.	Mar 2017	B2
9727432	Cutforth et al.	Aug 2017	B1
9747171	Beeken et al.	Aug 2017	B2
9753782	Fang et al.	Sep 2017	B2
9753932	Brow et al.	Sep 2017	B1
9753987	Dolan et al.	Sep 2017	B1
9785377	Shin et al.	Oct 2017	B2
9846698	Panidis et al.	Dec 2017	B1
10140185	Lopez et al.	Nov 2018	B1
10261868	Brown et al.	Apr 2019	B2
10275493	Mostak	Apr 2019	B1
10303561	Beeken et al.	May 2019	B2
10318401	Rothschilds et al.	Jun 2019	B2
10339101	Gupta	Jul 2019	B1
10423609	Strauss	Sep 2019	B1
10437509	Alexeev et al.	Oct 2019	B1
10447779	Dieterich	Oct 2019	B2
10474635	Unger et al.	Nov 2019	B1
10534758	Carpenter et al.	Jan 2020	B1
10540662	Barlett et al.	Jan 2020	B2
10545986	Tappan et al.	Jan 2020	B2
10621147	Liang et al.	Apr 2020	B1
10664408	Chatterjee et al.	May 2020	B1
10678663	Sharma et al.	Jun 2020	B1
10725977	Chmiel et al.	Jul 2020	B1
10795796	Bai et al.	Oct 2020	B1
10860546	Ye et al.	Dec 2020	B2
11023535	Greenwood et al.	Jun 2021	B1
11157458	Carter et al.	Oct 2021	B1
20010039622	Hitz et al.	Nov 2001	A1
20020059439	Arroyo et al.	May 2002	A1
20020065835	Fujisaki	May 2002	A1
20020083073	Vaidya et al.	Jun 2002	A1
20020099691	Lore et al.	Jul 2002	A1
20020178271	Graham et al.	Nov 2002	A1
20030033308	Patel et al.	Feb 2003	A1
20030145009	Forman et al.	Jul 2003	A1
20030177379	Hori et al.	Sep 2003	A1
20030182313	Federwisch et al.	Sep 2003	A1
20040030727	Armangau et al.	Feb 2004	A1
20040093474	Lin et al.	May 2004	A1
20040098425	Wiss et al.	May 2004	A1
20040153479	Mikesell et al.	Aug 2004	A1
20040255048	Lev Ran et al.	Dec 2004	A1
20050015674	Haugh	Jan 2005	A1
20050027748	Kisley	Feb 2005	A1
20050065986	Bixby et al.	Mar 2005	A1
20050091663	Bagsby	Apr 2005	A1
20050114593	Cassell	May 2005	A1
20050114726	Ouchi	May 2005	A1
20050119996	Ohata et al.	Jun 2005	A1
20050154866	Steely, Jr. et al.	Jul 2005	A1
20050195660	Kavuri et al.	Sep 2005	A1
20050223019	Das et al.	Oct 2005	A1
20060004890	Semple et al.	Jan 2006	A1
20060053139	Marzinski et al.	Mar 2006	A1
20060089982	Abbott et al.	Apr 2006	A1
20060090036	Zohar et al.	Apr 2006	A1
20060123005	Burnett et al.	Jun 2006	A1
20060173842	Horvitz et al.	Aug 2006	A1
20060271604	Shoens	Nov 2006	A1
20070011302	Groner et al.	Jan 2007	A1
20070027985	Ramany et al.	Feb 2007	A1
20070100855	Kohl	May 2007	A1
20070106706	Ahrens et al.	May 2007	A1
20070118561	Idicula et al.	May 2007	A1
20070143371	Kottomtharayil	Jun 2007	A1
20080028006	Liu et al.	Jan 2008	A1
20080059399	DeLorme et al.	Mar 2008	A1
20080059541	Fachan et al.	Mar 2008	A1
20080082593	Komarov et al.	Apr 2008	A1
20080162608	Torii et al.	Jul 2008	A1
20080172366	Hannel et al.	Jul 2008	A1
20080228772	Plamondon	Sep 2008	A1
20080250357	Lee et al.	Oct 2008	A1
20080256474	Chakra et al.	Oct 2008	A1
20080270469	Myerson et al.	Oct 2008	A1
20080270928	Chakra et al.	Oct 2008	A1
20080282244	Wu et al.	Nov 2008	A1
20080288306	MacIntyre et al.	Nov 2008	A1
20080301256	McWilliams et al.	Dec 2008	A1
20080313217	Dunsmore et al.	Dec 2008	A1
20090077087	Urano et al.	Mar 2009	A1
20090138500	Yuan et al.	May 2009	A1
20090199190	Chen et al.	Aug 2009	A1
20090222509	King et al.	Sep 2009	A1
20090240539	Slawson et al.	Sep 2009	A1
20090274047	Kruys et al.	Nov 2009	A1
20090319566	Wald et al.	Dec 2009	A1
20090327642	Ogihara et al.	Dec 2009	A1
20100030825	Matsuzawa et al.	Feb 2010	A1
20100036895	Boyd et al.	Feb 2010	A1
20100088317	Bone et al.	Apr 2010	A1
20100161557	Anderson et al.	Jun 2010	A1
20100179959	Shoens	Jul 2010	A1
20100217948	Mason et al.	Aug 2010	A1
20100241668	Susanto et al.	Sep 2010	A1
20100281214	Jernigan, IV	Nov 2010	A1
20100287512	Gan et al.	Nov 2010	A1
20110039622	Levenson	Feb 2011	A1
20110066668	Guarraci	Mar 2011	A1
20110082836	Wang et al.	Apr 2011	A1
20110125799	Kandasamy et al.	May 2011	A1
20110125973	Lev et al.	May 2011	A1
20110161381	Wang et al.	Jun 2011	A1
20110161964	Piazza et al.	Jun 2011	A1
20110196833	Drobychev et al.	Aug 2011	A1
20110196899	Hughes et al.	Aug 2011	A1
20110202925	Banerjee et al.	Aug 2011	A1
20110246724	Marathe et al.	Oct 2011	A1
20120036463	Krakovsky et al.	Feb 2012	A1
20120066179	Saika	Mar 2012	A1
20120096059	Shimizu et al.	Apr 2012	A1
20120136843	Bone et al.	May 2012	A1
20120151438	Bach et al.	Jun 2012	A1
20120166478	Das et al.	Jun 2012	A1
20120179886	Prahlad et al.	Jul 2012	A1
20120204060	Swift et al.	Aug 2012	A1
20120216005	Naito	Aug 2012	A1
20120317079	Shoens et al.	Dec 2012	A1
20130019072	Strasser et al.	Jan 2013	A1
20130024609	Gorobets et al.	Jan 2013	A1
20130073819	Havewala et al.	Mar 2013	A1
20130086121	Preslan	Apr 2013	A1
20130091168	Bhave et al.	Apr 2013	A1
20130110787	Garimella et al.	May 2013	A1
20130191355	Bone et al.	Jul 2013	A1
20130212579	Ben-Shaul et al.	Aug 2013	A1
20130227236	Flynn et al.	Aug 2013	A1
20130254163	Savage et al.	Sep 2013	A1
20130268650	Faitelson et al.	Oct 2013	A1
20130275391	Batwara et al.	Oct 2013	A1
20130304903	Mick et al.	Nov 2013	A1
20130311454	Ezzat	Nov 2013	A1
20130318194	Timbs	Nov 2013	A1
20130325806	Bachar et al.	Dec 2013	A1
20130325808	Bachar et al.	Dec 2013	A1
20130339406	Kanfi	Dec 2013	A1
20140006354	Parkison et al.	Jan 2014	A1
20140040199	Golab et al.	Feb 2014	A1
20140040693	Kim et al.	Feb 2014	A1
20140059158	Chen et al.	Feb 2014	A1
20140089278	Lovinger et al.	Mar 2014	A1
20140089649	Chaganti	Mar 2014	A1
20140095249	Tarakad et al.	Apr 2014	A1
20140095505	Blanchflower et al.	Apr 2014	A1
20140095560	Ikai et al.	Apr 2014	A1
20140095582	Eshel et al.	Apr 2014	A1
20140101389	Nellans et al.	Apr 2014	A1
20140156956	Ezra	Jun 2014	A1
20140181441	Kottomtharayil et al.	Jun 2014	A1
20140189267	Qi et al.	Jul 2014	A1
20140237193	Shivashankaraiah	Aug 2014	A1
20140258609	Cui et al.	Sep 2014	A1
20140280485	A Hummaida et al.	Sep 2014	A1
20140281307	Peterson et al.	Sep 2014	A1
20140281411	Abdallah	Sep 2014	A1
20140344222	Morris et al.	Nov 2014	A1
20140372384	Long et al.	Dec 2014	A1
20140372607	Gladwin et al.	Dec 2014	A1
20140373032	Merry et al.	Dec 2014	A1
20150006226	Smith et al.	Jan 2015	A1
20150012666	Pannese et al.	Jan 2015	A1
20150067086	Adriaens et al.	Mar 2015	A1
20150067142	Renkema	Mar 2015	A1
20150106145	Hamilton et al.	Apr 2015	A1
20150135331	Das	May 2015	A1
20150143026	Reddy et al.	May 2015	A1
20150149736	Kwon et al.	May 2015	A1
20150186217	Eslami Sarab	Jul 2015	A1
20150186410	Petculescu et al.	Jul 2015	A1
20150186483	Tappan et al.	Jul 2015	A1
20150186527	Rao et al.	Jul 2015	A1
20150186529	Rope et al.	Jul 2015	A1
20150193347	Kluesing et al.	Jul 2015	A1
20150215405	Baek et al.	Jul 2015	A1
20150234716	Brooker	Aug 2015	A1
20150234879	Baldwin et al.	Aug 2015	A1
20150242263	Klose	Aug 2015	A1
20150248253	Kim et al.	Sep 2015	A1
20150278282	Sardina et al.	Oct 2015	A1
20150310035	Godman et al.	Oct 2015	A1
20150347126	Tibble et al.	Dec 2015	A1
20160034356	Aron et al.	Feb 2016	A1
20160110105	Karamcheti et al.	Apr 2016	A1
20160139836	Nallathambi et al.	May 2016	A1
20160147654	Zhao et al.	May 2016	A1
20160224430	Long et al.	Aug 2016	A1
20160239185	Balimidi et al.	Aug 2016	A1
20160246816	Abiri et al.	Aug 2016	A1
20160269501	Usgaonkar et al.	Sep 2016	A1
20160292013	Li et al.	Oct 2016	A1
20160292429	Manville et al.	Oct 2016	A1
20160306810	Ni et al.	Oct 2016	A1
20160314046	Kumarasamy	Oct 2016	A1
20160335278	Tabaaloute et al.	Nov 2016	A1
20160357677	Hooker et al.	Dec 2016	A1
20160359859	Capone	Dec 2016	A1
20160371297	Okun et al.	Dec 2016	A1
20160380878	Bugenhagen et al.	Dec 2016	A1
20170024152	Bhagi et al.	Jan 2017	A1
20170032006	Anglin et al.	Feb 2017	A1
20170046143	Kochhar et al.	Feb 2017	A1
20170052898	Ash et al.	Feb 2017	A1
20170078164	Hildebrand et al.	Mar 2017	A1
20170091046	Bangalore et al.	Mar 2017	A1
20170118287	Beck	Apr 2017	A1
20170123883	Hall	May 2017	A1
20170123935	Pandit et al.	May 2017	A1
20170163728	Chawla et al.	Jun 2017	A1
20170201582	Zhang et al.	Jul 2017	A1
20170206231	Binder et al.	Jul 2017	A1
20170270180	State	Sep 2017	A1
20170286455	Li et al.	Oct 2017	A1
20170316321	Whitney et al.	Nov 2017	A1
20170336983	Roh et al.	Nov 2017	A1
20170344598	Constantinescu et al.	Nov 2017	A1
20170344905	Hack et al.	Nov 2017	A1
20170366609	Dieterich et al.	Dec 2017	A1
20180040029	Zeng et al.	Feb 2018	A1
20180059946	Kunii	Mar 2018	A1
20180089031	Mitkar et al.	Mar 2018	A1
20180101546	Krasnow et al.	Apr 2018	A1
20180129443	Karve et al.	May 2018	A1
20180203798	Hughes et al.	Jul 2018	A1
20180276078	Blea et al.	Sep 2018	A1
20180288057	Varadamma et al.	Oct 2018	A1
20180314423	Gong et al.	Nov 2018	A1
20180365115	Fang	Dec 2018	A1
20190087770	Walsh et al.	Mar 2019	A1
20190095112	Lingarajappa	Mar 2019	A1
20190102700	Babu et al.	Apr 2019	A1
20190163589	McBride et al.	May 2019	A1
20190163591	Ouyang et al.	May 2019	A1
20190196879	Dutta	Jun 2019	A1
20190212921	Liang et al.	Jul 2019	A1
20190220189	Yang et al.	Jul 2019	A1
20190286521	Okpotse et al.	Sep 2019	A1
20190286528	Wu et al.	Sep 2019	A1
20190384640	Swamy et al.	Dec 2019	A1
20200004977	Araujo et al.	Jan 2020	A1
20200026438	Peleg et al.	Jan 2020	A1
20200034077	Haravu et al.	Jan 2020	A1
20200142878	Varadarajan et al.	May 2020	A1
20200174692	Dave et al.	Jun 2020	A1
20200242075	Davis et al.	Jul 2020	A1
20200286270	Lymperopoulos et al.	Sep 2020	A1
20200409583	Kusters	Dec 2020	A1
20210004355	Iwase	Jan 2021	A1
20210042263	Zdornov et al.	Feb 2021	A1
20210042282	Cseri et al.	Feb 2021	A1
20210056074	Zhu	Feb 2021	A1
20210110150	Kakrana et al.	Apr 2021	A1
20210191650	Vansteenkiste et al.	Jun 2021	A1
20210240393	Jo et al.	Aug 2021	A1
20210240678	Patel et al.	Aug 2021	A1
20210279187	Puder et al.	Sep 2021	A1
20210311841	McNutt	Oct 2021	A1
20210374105	Kodama et al.	Dec 2021	A1
20220019361	Kurata et al.	Jan 2022	A1
20220066882	Wang et al.	Mar 2022	A1
20220091739	Kumar et al.	Mar 2022	A1

Foreign Referenced Citations (6)

Number	Date	Country
1217551	Jun 2002	EP
1498829	Jan 2005	EP
1999044145	Sep 1999	WO
0072201	Nov 2000	WO
2009007250	Jan 2009	WO
2012029259	Mar 2012	WO

Non-Patent Literature Citations (210)

Entry
Office Communication for U.S. Appl. No. 16/226,587 dated Aug. 5, 2019, pp. 1-46.
Office Communication for U.S. Appl. No. 16/228,716 dated Jun. 24, 2019, pp. 1-10.
Office Communication for U.S. Appl. No. 16/262,756 dated Jul. 10, 2019, pp. 1-8.
Office Communication for U.S. Appl. No. 16/262,756 dated Aug. 5, 2019, pp. 1-35.
Office Communication for U.S. Appl. No. 15/967,499 dated Jun. 27, 2018, pp. 1-16.
Office Communication for U.S. Appl. No. 16/226,587 dated Feb. 25, 2019, pp. 1-43.
Office Communication for U.S. Appl. No. 16/231,354 dated Feb. 28, 2019, pp. 1-15.
Office Communication for U.S. Appl. No. 16/231,354 dated Mar. 25, 2019, pp. 1-10.
Office Communication for U.S. Appl. No. 16/262,756 dated Apr. 2, 2019, pp. 1-29.
Office Communication for U.S. Appl. No. 16/262,790 dated Aug. 23, 2019, pp. 1-16.
Office Communication for U.S. Appl. No. 16/262,756 dated Apr. 18, 2019, pp. 1-14.
Office Communication for U.S. Appl. No. 16/262,756 dated Oct. 25, 2019, pp. 1-4.
Office Communication for U.S. Appl. No. 16/659,488 dated Dec. 30, 2019, pp. 1-6.
Office Communication for U.S. Appl. No. 16/004,208 dated Dec. 31, 2019, pp. 1-16.
Office Communication for U.S. Appl. No. 16/004,208 dated Aug. 27, 2018, pp. 1-11.
Office Communication for U.S. Appl. No. 16/234,395 dated Aug. 8, 2019, pp. 1-10.
Office Communication for U.S. Appl. No. 16/234,334 dated Apr. 5, 2019, pp. 1-15.
Office Communication for U.S. Appl. No. 16/234,395 dated Mar. 28, 2019, pp. 1-10.
Kappes, Giorgos et al., “Dike: Virtualization-aware Access Control for Multitenant Filesystems”, Feb. 18, 2013, pp. 1-6.
Hitz, Dave et al., “Merging NT and UNIX filesystem Permissions”, Proceedings of the 2nd USENIX Windows NT Symposium, Seattle, Washington, Aug. 3-4, 1998, pp. 1-10.
Office Communication for U.S. Appl. No. 16/234,334 dated Oct. 11, 2019, pp. 1-16.
Office Communication for U.S. Appl. No. 15/473,051 dated Jun. 30, 2017, pp. 1-23.
Extended European Search Report for European U.S. Appl. No. 15/473,051 dated Apr. 17, 2018, pp. 1-15.
Office Communication for U.S. Appl. No. 16/004,182 dated Aug. 23, 2018, pp. 1-43.
Office Communication for U.S. Appl. No. 16/004,132 dated Mar. 5, 2019, pp. 1-46.
Office Communication for U.S. Appl. No. 16/004,132 dated Jul. 3, 2019, pp. 1-45.
Office Communication for U.S. Appl. No. 15/694,604 dated Jun. 3, 2019, pp. 1-8.
Office Communication for U.S. Appl. No. 16/004,182 dated May 22, 2019, pp. 1-4.
Office Communication for U.S. Appl. No. 14/595,043 dated May 4, 2017, pp. 1-30.
Office Communication for U.S. Appl. No. 14/595,043 dated Feb. 23, 2018, pp. 1-16.
Office Communication for U.S. Appl. No. 14/595,043 dated May 25, 2018, pp. 1-7.
Office Communication for U.S. Appl. No. 14/595,043 dated Oct. 5, 2018, pp. 1-17.
Office Communication for U.S. Appl. No. 14/595,043 dated Jun. 7, 2019, pp. 1-19.
Office Communication for U.S. Appl. No. 14/595,043 dated Aug. 27, 2019, pp. 1-17.
Office Communication for U.S. Appl. No. 14/658,015 dated Apr. 27, 2017, pp. 1-7.
Office Communication for U.S. Appl. No. 14/658,015 dated Jan. 4, 2018, pp. 1-28.
Office Communication for U.S. Appl. No. 14/658,015 dated Jul. 13, 2018, pp. 1-8.
Office Communication for U.S. Appl. No. 14/859,061 dated Sep. 22, 2017, pp. 1-16.
Office Communication for U.S. Appl. No. 15/831,236 dated Mar. 30, 2018, pp. 1-8.
Office Communication for U.S. Appl. No. 14/859,114 dated Aug. 15, 2018, pp. 1-14.
Office Communication for U.S. Appl. No. 14/859,114 dated Jul. 24, 2017, pp. 1-41.
Office Communication for U.S. Appl. No. 14/859,114 dated Feb. 21, 2018, pp. 1-25.
Office Communication for U.S. Appl. No. 14/859,114 dated May 11, 2018, pp. 1-5.
Office Communication for U.S. Appl. No. 14/859,114 dated Jun. 27, 2018, pp. 1-33.
Office Communication for U.S. Appl. No. 14/859,114 dated Nov. 19, 2018, pp. 1-35.
Office Communication for U.S. Appl. No. 14/859,114 dated Jan. 31, 2019, pp. 1-4.
Office Communication for U.S. Appl. No. 14/859,114 dated Mar. 7, 2019, pp. 1-32.
Office Communication for U.S. Appl. No. 14/859,114 dated Jun. 26, 2019, pp. 1-21.
Office Communication for U.S. Appl. No. 14/859,114 dated Sep. 13, 2019, pp. 1-6.
Office Communication for U.S. Appl. No. 14/859,114 dated Nov. 26, 2019, pp. 1-21.
Office Communication for U.S. Appl. No. 15/288,853 dated Sep. 19, 2018, pp. 1-13.
Chimera, Richard, “Value Bars: An information Visualization and Navigation Tool for Multi-attribute Listings”, CHI '92, Monterey, CA, May 3-7, 1992, pp. 293-294.
Office Communication for U.S. Appl. No. 15/288,853 dated Mar. 25, 2019, pp. 1-10.
Cudre-Mauroux, Philippe et al., “TrajStore: An Adaptive Storage System for Very Large Trajectory Sets”, ICDE 2010, Long Beach, CA, Mar. 1-6, 2010; pp. 109-120.
Office Communication for U.S. Appl. No. 16/436,825 dated Jul. 11, 2019, pp. 1-9.
Office Communication for U.S. Appl. No. 15/474,047 dated Sep. 18, 2017, pp. 1-14.
Office Communication for U.S. Appl. No. 15/474,047 dated Mar. 9, 2018, pp. 1-8.
Office Communication for U.S. Appl. No. 15/474,047 dated Jun. 11, 2018, pp. 1-6.
Office Communication for U.S. Appl. No. 15/474,047 dated Aug. 15, 2018, pp. 1-11.
Office Communication for U.S. Appl. No. 15/957,809 dated Jun. 28, 2018, pp. 1-27.
Office Communication for U.S. Appl. No. 15/957,809 dated Jan. 24, 2019, pp. 1-11.
Office Communication for U.S. Appl. No. 16/434,157 dated Jul. 25, 2019, pp. 1-8.
Office Communication for U.S. Appl. No. 15/854,447 dated May 6, 2019, pp. 1-9.
Office Communication for U.S. Appl. No. 16/505,562 dated Aug. 30, 2019, pp. 1-11.
Extended European Search Report for European Patent Application No. 17206518.7 dated Apr. 5, 2018, pp. 1-8.
Karatza et al., “Epoch Load Sharing in a Network of Workstations,” Simulation Symposium, 2001. Proceedings. 34th Annual Apr. 22-26, 2001, Piscataway, NJ, USA, IEEE, XP010541274, ISBN: 978-0-7695-1092-7, pp. 36-42.
Office Communication for U.S. Appl. No. 16/004,182 dated Jan. 7, 2020, pp. 1-46.
Office Communication for U.S. Appl. No. 16/125,573 dated Nov. 21, 2019, pp. 1-13.
Office Communication for U.S. Appl. No. 16/226,587 dated Oct. 24, 2019, pp. 1-4.
Office Communication for U.S. Appl. No. 16/262,790 dated Dec. 12, 2019, pp. 1-10.
Office Communication for U.S. Appl. No. 16/234,334 dated Jan. 16, 2020, pp. 1-8.
Office Communication for U.S. Appl. No. 15/694,604 dated Nov. 20, 2019, pp. 1-8.
Office Communication for U.S. Appl. No. 16/262,756 dated Jan. 23, 2020, pp. 1-21.
Office Communication for U.S. Appl. No. 16/434,157 dated Jan. 29, 2020, pp. 1-9.
Office Communication for U.S. Appl. No. 16/262,790 dated Feb. 6, 2020, pp. 1-5.
Office Communication for U.S. Appl. No. 14/859,114 dated Mar. 13, 2020, pp. 1-21.
Office Communication for U.S. Appl. No. 16/752,451 dated Mar. 12, 2020, pp. 1-14.
Office Communication for U.S. Appl. No. 16/775,041 dated Mar. 11, 2020, pp. 1-8.
Office Communication for U.S. Appl. No. 16/779,362 dated Mar. 26, 2020, pp. 1-10.
Wikipedia clustered file system page from date Jul. 9, 2019, retrieved using the WayBackMachine, From https://web.archive.org/web/20190709083400/https://en.wikipedia.org/wiki/Clustered_file_system (Year: 2019), pp. 1-6.
Wikipedia raft page from date Jul. 16, 2019, retrieved using the WayBackMachine, from https://web.archive.org/web/20190716115001/https://en.wikipedia.org/wiki/Raft (computer_ science) (Year: 2019), pp. 1-4.
Office Communication for U.S. Appl. No. 16/004,182 dated Mar. 23, 2020, pp. 1-4.
Office Communication for U.S. Appl. No. 16/752,509 dated Apr. 2, 2020, pp. 1-8.
Office Communication for U.S. Appl. No. 16/152,277 dated Apr. 3, 2020, pp. 1-10.
Office Communication for U.S. Appl. No. 16/004,182 dated Apr. 23, 2020, pp. 1-51.
Office Communication for U.S. Appl. No. 16/152,259 dated Apr. 29, 2020, pp. 1-19.
Office Communication for U.S. Appl. No. 14/859,114 dated Jun. 5, 2020, pp. 1-5.
Office Communication for U.S. Appl. No. 16/262,756 dated Jun. 8, 2020, pp. 1-22.
Office Communication for U.S. Appl. No. 14/595,593 dated Jul. 9, 2020, pp. 1-19.
Office Communication for U.S. Appl. No. 16/752,451 dated Jul. 23, 2020, pp. 1-8.
Office Communication for U.S. Appl. No. 14/859,114 dated Jul. 23, 2020, pp. 1-21.
Office Communication for U.S. Appl. No. 16/152,615 dated Aug. 6, 2020, pp. 1-7.
Office Communication for U.S. Appl. No. 16/779,362 dated Aug. 7, 2020, pp. 1-11.
Office Communication for U.S. Appl. No. 16/883,922 dated Aug. 7, 2020, pp. 1-13.
Office Communication for U.S. Appl. No. 16/775,041 dated Aug. 18, 2020, pp. 1-9.
Office Communication for U.S. Appl. No. 16/883,879 dated Sep. 1, 2020, pp. 1-11.
Extended European Search Report for European Patent Application No. 16812585.4 dated Nov. 7, 2018, pp. 1-9.
Comer, Douglas, “The Ubiquitous B-Tree,” Computing Surveys, vol. 11, No. 2, Jun. 1979, Computer Science Department, Purdue University, West Lafayette, Indiana 47907, pp. 121-137.
Office Communication for European Patent Application No, 16812585.4 dated Jan. 2, 2020, pp. 1-6.
International Search Report and Written Opinion for International Patent Application No. PCT/US2016/038242 dated Oct. 11, 2016, pp. 1-11.
Office Communication for U.S. Appl. No. 14/595,598 dated Jul. 31, 2019, pp. 1-5.
Office Communication for U.S. Appl. No. 14/595,598 dated Sep. 20, 2018, pp. 1-18.
Office Communication for U.S. Appl. No. 14/595,598 dated Dec. 15, 2017, pp. 1-18.
Office Communication for U.S. Appl. No. 14/595,598 dated Feb. 24, 2017, pp. 1-8.
Office Communication for U.S. Appl. No. 14/595,598 dated Apr. 19, 2018, pp. 1-5.
Bloom, Burton H., “Space/Time Trade-offs in Hash Coding with Allowable Errors,” Communications of the ACM, vol. 13, No. 7, Jul. 1970. Computer Usage Company, Newton Upper Falls, Massachusetts, pp. 422-426.
Office Communication for U.S. Appl. No. 16/262,756 dated Aug. 24, 2020, pp. 1-7.
Office Communication for European Patent Application No. 18155779.4 dated Oct. 8, 2019, pp. 1-4.
Office Communication for U.S. Appl. No. 16/152,259 dated Aug. 28, 2020, pp. 1-5.
Office Communication for U.S. Appl. No. 16/752,509 dated Aug. 11, 2020, pp. 1-7.
Office Communication for U.S. Appl. No. 14/595,598 dated Sep. 25, 2020, pp. 1-7.
Office Communication for U.S. Appl. No. 16/152,277 dated Oct. 16, 2020, pp. 1-10.
Office Communication for U.S. Appl. No. 16/152,615 dated Oct. 20, 2020, pp. 1-7.
Office Communication for U.S. Appl. No. 16/775,041 dated Nov. 3, 2020, pp. 1-5.
Office Communication for U.S. Appl. No. 17/062,500 dated Nov. 12, 2020, pp. 1-12.
Office Communication for U.S. Appl. No. 16/004,182 dated Nov. 30, 2020, pp. 1-55.
Office Communication for U.S. Appl. No. 14/859,114 dated Dec. 1, 2020, pp. 1-24.
Office Communication for U.S. Appl. No. 16/883,922 dated Dec. 2, 2020, pp. 1-9.
Office Communication for U.S. Appl. No. 16/883,879 dated Dec. 8, 2020, pp. 1-5.
Office Communication for U.S. Appl. No. 16/152,277 dated Dec. 23, 2020, pp. 1-5.
Office Communication for U.S. Appl. No. 16/004,132 dated Jan. 28, 2021, pp. 1-4.
Office Communication for U.S. Appl. No. 14/595,598 dated Feb. 4, 2021, pp. 1-19.
Office Communication for U.S. Appl. No. 17/115,529 dated Feb. 8, 2021, pp. 1-15.
Office Communication for U.S. Appl. No. 16/262,756 dated Feb. 10, 2021, pp. 1-19.
Office Communication for U.S. Appl. No. 17/114,384 dated Feb. 17, 2021, pp. 1-12.
Examination Report for European Patent Application No. 17206518.7 dated Feb. 23, 2021, pp. 1-6.
Office Communication for U.S. Appl. No. 14/859,114 dated Mar. 8, 2021, pp. 1-4.
Office Communication for U.S. Appl. No. 16/004,182 dated Mar. 8, 2021, pp. 1-60.
Office Communication for U.S. Appl. No. 17/062,500 dated Mar. 9, 2021, pp. 1-17.
Office Communication for U.S. Appl. No. 16/152,277 dated Mar. 16, 2021, pp. 1-10.
Office Communication for U.S. Appl. No. 17/160,698 dated Mar. 18, 2021, pp. 1-11.
Office Communication for U.S. Appl. No. 16/231,354 dated Jul. 10, 2019, pp. 1-8.
Office Communication for U.S. Appl. No. 16/228,716 dated Feb. 28, 2019, pp. 1-15.
Office Communication for U.S. Appl. No. 16/262,790 dated Apr. 18, 2019, pp. 1-14.
Office Communication for U.S. Appl. No. 14/595,598 dated Dec. 31, 2019, pp. 1-16.
Extended European Search Report for European Patent Application No. 18155779.4 dated Apr. 17, 2018, pp. 1-15.
Office Communication for U.S. Appl. No. 16/004,182 dated Mar. 5, 2019, pp. 1-46.
Office Communication for U.S. Appl. No. 16/004,182 dated Jul. 3, 2019, pp. 1-45.
Office Communication for U.S. Appl. No. 16/694,604 dated Jun. 3, 2019, pp. 1-8.
Office Communication for U.S. Appl. No. 15/831,236 dated Aug. 15, 2018, pp. 1-14.
Office Communication for U.S. Appl. No. 16/262,756 dated Jan. 28, 2020, pp. 1-21.
Office Communication for U.S. Appl. No. 16/262,790 dated Feb. 6, 2020, pp. 1-8.
Office Communication for U.S. Appl. No. 16/004,182 dated Apr. 28, 2020, pp. 1-51.
Office Communication for U.S. Appl. No. 14/595,598 dated Jul. 9, 2020, pp. 1-19.
Office Communication for U.S. Appl. No. 16/152,277 dated Dec. 28, 2020, pp. 1-5.
Office Communication for U.S. Appl. No. 16/004,182 dated Jan. 28, 2021, pp. 1-4.
Office Communication for U.S. Appl. No. 16/152,277 dated Mar. 18, 2021, pp. 1-10.
Office Communication for U.S. Appl. No. 16/152,277 dated Jun. 25, 2021, pp. 1-10.
Office Communication for U.S. Appl. No. 17/160,698 dated Jul. 1, 2021, pp. 1-58.
Office Communication for U.S. Appl. No. 17/160,698 dated Jul. 2, 2021, pp. 1-12.
International Search Report and Written Opinion for International Patent Application No. PCT/US2021/023531 dated Jul. 6, 2021, pp. 1-7.
Office Communication for U.S. Appl. No. 17/062,500 dated Jul. 12, 2021, pp. 1-18.
Office Communication for U.S. Appl. No. 17/114,384 dated Jul. 21, 2021, pp. 1-11.
Office Communication for U.S. Appl. No. 17/114,384 dated Aug. 3, 2021, pp. 1-4.
Office Communication for U.S. Appl. No. 14/595,598 dated Aug. 6, 2021, pp. 1-20.
Office Communication for U.S. Appl. No. 17/115,529 dated Aug. 12, 2021, pp. 1-4.
Office Communication for U.S. Appl. No. 17/114,384 dated Aug. 27, 2021, pp. 1-11.
Office Communication for U.S. Appl. No. 17/114,384 dated Sep. 2, 2021, pp. 1-5.
Office Communication for U.S. Appl. No. 16/152,277 dated Sep. 3, 2021, pp. 1-4.
Office Communication for U.S. Appl. No. 16/004,182 dated Sep. 10, 2021, pp. 1-4.
Office Communication for U.S. Appl. No. 17/190,653 dated Nov. 10, 2021, pp. 1-6.
Office Communication for U.S. Appl. No. 17/484,167 dated Nov. 13, 2021, pp. 1-15.
Office Communication for U.S. Appl. No. 17/504,289 dated Dec. 7, 2021, pp. 1-15.
Office Communication for U.S. Appl. No. 17/190,653 dated Dec. 14, 2021, pp. 1-7.
Office Communication for U.S. Appl. No. 17/190,653 dated Dec. 21, 2021, pp. 1-12.
Office Communication for U.S. Appl. No. 17/508,869 dated Dec. 22, 2021, pp. 1-9.
Office Communication for U.S. Appl. No. 17/491,017 dated Dec. 23, 2021, pp. 1-41.
Office Communication for U.S. Appl. No. 17/062,500 dated Dec. 29, 2021, pp. 1-19.
Office Communication for U.S. Appl. No. 17/062,500 dated Jan. 7, 2022, pp. 1-4.
Office Communication for U.S. Appl. No. 16/741,567 dated Jan. 11, 2022, pp. 1-6.
Office Communication for U.S. Appl. No. 17/510,043 dated Jan. 21, 2022, pp. 1-13.
Office Communication for U.S. Appl. No. 16/741,567 dated Feb. 7, 2022, pp. 1-8.
Office Communication for U.S. Appl. No. 16/004,182 dated Sep. 29, 2021, pp. 1-11.
Office Communication for U.S. Appl. No. 16/152,277 dated Oct. 18, 2021, pp. 1-5.
International Search Report and Written Opinion for International Patent Application No. PCT/US2021/023525 dated Oct. 12, 2021, pp. 1-7.
Office Communication for U.S. Appl. No. 17/115,529 dated Oct. 22, 2021, pp. 1-20.
Office Communication for U.S. Appl. No. 17/062,500 dated Oct. 27, 2021, pp. 1-17.
Office Communication for U.S. Appl. No. 14/595,598 dated Oct. 28, 2021, pp. 1-6.
Office Communication for U.S. Appl. No. 16/741,567 dated Oct. 28, 2021, pp. 1-11.
Office Communication for U.S. Appl. No. 17/530,420 dated Feb. 10, 2022, pp. 1-24.
Office Communication for U.S. Appl. No. 16/004,182 dated Feb. 18, 2022, pp. 1-11.
Office Communication for U.S. Appl. No. 17/115,529 dated Feb. 18, 2022, pp. 1-20.
Office Communication for U.S. Appl. No. 17/484,167 dated Mar. 11, 2022, pp. 1-11.
Office Communication for U.S. Appl. No. 17/062,500 dated Mar. 22, 2022, pp. 1-19.
Office Communication for U.S. Appl. No. 17/504,289 dated Mar. 28, 2022, pp. 1-9.
Office Communication for U.S. Appl. No. 17/588,120 dated Apr. 11, 2022, pp. 1-36.
Office Communication for U.S. Appl. No. 17/588,895 dated Apr. 27, 2022, pp. 1-6.
Office Communication for U.S. Appl. No. 17/190,653 dated Apr. 28, 2022, pp. 1-13.
Office Communication for U.S. Appl. No. 17/510,043 dated Apr. 29, 2022, pp. 1-10.
Office Communication for U.S. Appl. No. 17/115,529 dated Apr. 29, 2022, pp. 1-4.
Office Communication for U.S. Appl. No. 17/491,017 dated May 12, 2022, pp. 1-50.
Office Communication for U.S. Appl. No. 17/484,167 dated May 17, 2022, pp. 1-3.
Office Communication for U.S. Appl. No. 17/484,167 dated Jun. 10, 2022, pp. 1-5.
Office Communication for U.S. Appl. No. 14/595,598 dated Jul. 13, 2022, pp. 1-9.
Office Communication for U.S. Appl. No. 17/062,500 dated Jul. 26, 2022, pp. 1-20.
Office Communication for U.S. Appl. No. 17/588,120 dated Jul. 27, 2022, pp. 1-34.
Office Communication for U.S. Appl. No. 17/190,653 dated Aug. 2, 2022, pp. 1-8.
Office Communication for U.S. Appl. No. 17/115,529 dated Aug. 8, 2022, pp. 1-21.
Office Communication for U.S. Appl. No. 17/588,895 dated Aug. 12, 2022, pp. 1-12.
Office Communication for U.S. Appl. No. 17/491,017 dated Aug. 17, 2022, pp. 1-5.
Office Communication for U.S. Appl. No. 17/491,017 dated Sep. 15, 2022, pp. 1-55.
Office Communication for U.S. Appl. No. 17/864,190 dated Sep. 19, 2022, pp. 1-10.
Office Communication for U.S. Appl. No. 17/062,500 dated May 18, 2021, pp. 1-4.
Office Communication for U.S. Appl. No. 17/203,371 dated May 20, 2021, pp. 1-10.
Office Communication for U.S. Appl. No. 17/115,529 dated May 25, 2021, pp. 1-18.
Office Communication for U.S. Appl. No. 14/859,114 dated May 26, 2021, pp. 1-11.
Office Communication for U.S. Appl. No. 16/262,756 dated May 27, 2021, pp. 1-7.
Office Communication for U.S. Appl. No. 17/114,384 dated May 27, 2021, pp. 1-13.
Office Communication for U.S. Appl. No. 17/190,653 dated May 27, 2021, pp. 1-11.
Office Communication for U.S. Appl. No. 16/741,567 dated Jun. 8, 2021, pp. 1-5.

Related Publications (1)

	Number	Date	Country
	20220300155 A1	Sep 2022	US

Managing cloud storage for distributed file systems

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

International Classifications

Abstract

Description

Claims

US Referenced Citations (339)

Foreign Referenced Citations (6)

Non-Patent Literature Citations (210)

Related Publications (1)