SYSTEMS AND METHODS FOR CONTINUOUSLY AVAILABLE NETWORK FILE SYSTEM (NFS) STATE DATA
First Claim
1. A method comprising:
- receiving, by a network file system (NFS) server, instructions to change a state corresponding to a data object accessible by the NFS server from a current state to a new state;
storing, by the NFS server, an indication of the new state in volatile memory, the indication being stored in association with an identifier of the data object;
writing, by the NFS server, metadata representing the new state at a location in non-volatile storage, wherein the metadata is written in association with a same or different identifier of the data object;
detecting, by the NFS server, a failure involving the NFS server;
retrieving, by the NFS server, the metadata representing the new state from the location in the non-volatile storage; and
resuming service, by the NFS server, in accordance with the new state.
1 Assignment
0 Petitions
Accused Products
Abstract
According to some embodiments of the invention, systems and methods are provided for capturing and storing state information corresponding to various states of the network file system (NFS) for use in recovery during a system failure. In various aspects, the disclosed systems and methods may automatically collect and synchronously write state changes made to the NFS to non-volatile storage. In the event of an NFS system failure or crash (e.g., a failure of the NFS server), the state information corresponding to the NFS system may be automatically imported from the non-volatile storage, thereby enabling NFS services to be resumed immediately and transparently.
5 Citations
20 Claims
-
1. A method comprising:
-
receiving, by a network file system (NFS) server, instructions to change a state corresponding to a data object accessible by the NFS server from a current state to a new state; storing, by the NFS server, an indication of the new state in volatile memory, the indication being stored in association with an identifier of the data object; writing, by the NFS server, metadata representing the new state at a location in non-volatile storage, wherein the metadata is written in association with a same or different identifier of the data object; detecting, by the NFS server, a failure involving the NFS server; retrieving, by the NFS server, the metadata representing the new state from the location in the non-volatile storage; and resuming service, by the NFS server, in accordance with the new state. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A device comprising:
-
one or more processors; and a non-transitory computer-readable medium containing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including; receiving instructions to change a state corresponding to a data object accessible by the NFS server from a current state to a new state; storing an indication of the new state in volatile memory, the indication being stored in association with an identifier of the data object; writing metadata representing the new state at a location in non-volatile storage, wherein the metadata is written in association with a same or different identifier of the data object; detecting a failure involving the NFS server; retrieving the metadata representing the new state from the location in the non-volatile storage; and resuming service in accordance with the new state. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A computer-program product tangibly embodied in a non-transitory machine-readable storage medium of a device, including instructions that, when executed by one or more processors, cause the one or more processors to:
-
receive instructions to change a state corresponding to a data object accessible by the NFS server from a current state to a new state; store an indication of the new state in volatile memory, the indication being stored in association with an identifier of the data object; write metadata representing the new state at a location in non-volatile storage, wherein the metadata is written in association with a same or different identifier of the data object; detect a failure involving the NFS server; retrieve the metadata representing the new state from the location in the non-volatile storage; and resume service in accordance with the new state. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification