WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.
Architecture - Punch and Extent Migration Requirements
From Obsolete Lustre Wiki
Jump to navigationJump to search
Note: The content on this page reflects the state of design of a Lustre feature at a particular point in time and may contain outdated information.
| tag | summary |
| checkvers | optionally an inode version can be passed to the punch call and the punch will only take place if the inode, when locked has the version passed into the call. This enables handling races between modifying inodes and punching data from them. |
| access | there is an ioctl to probe the presence of data in an extent. If any data in the extent has been punched, the ioctl will indicate so. The success case is that all data in the extent is present in the inode |
| punchextentmap | an EA can be installed that points to or contains an extent map that describes the extents that have been punched from the file. |
| sparseispunched | optionally, the recorded extents can be omitted and data is deemed punched if a sparse area is found in the file. |
| punchmigrate | punched data can be migrated to another offset in another inode instead of freed |
