MANAGING DATA ACCESS REQUESTS AFTER PERSISTENT SNAPSHOTS
A client node on which a file system is mounted can be configured to efficiently handle content access requests after a snapshot is created. The client node can maintain generation numbers at a data block, a file, and a fileset level to determine whether a data block is part of a snapshot generation...
Saved in:
Main Authors | , , , |
---|---|
Format | Patent |
Language | English |
Published |
31.01.2013
|
Subjects | |
Online Access | Get full text |
Cover
Loading…
Summary: | A client node on which a file system is mounted can be configured to efficiently handle content access requests after a snapshot is created. The client node can maintain generation numbers at a data block, a file, and a fileset level to determine whether a data block is part of a snapshot generation and consequently whether the data block is writable in a current generation. Data block mappings and write access permissions associated with the data blocks need not be revoked at the client node prior to creating the snapshot. Cached data block mappings can be accessed to identify data blocks for servicing a read request. The data block can be updated in place if the data block is not part of the snapshot generation. The write request can be serviced at a new data block if the data block is part of the snapshot generation. |
---|---|
Bibliography: | Application Number: US201213632340 |