Intent log
An intent log is a mechanism used to make computer operations more resilient in the event of failures. They are used in database software, transaction managers, and some file systems. In database area, transaction log is widely used. In file system area, intent log is used more often.[1]
Before performing an operation, a record of the intent to perform it is written, usually to some relatively permanent medium such as a hard disk drive. After the operation is performed, another record is written. Usually, an operation will change some data in a system. In some cases, the intent record will contain a copy of the data before and after the operation.[2]
This adds overhead, sometimes a significant amount. Enough data is written to the log to either redo or to undo the operation later.
If a failure occurs, then when the system is recovering, it can use the intent log to detect what operations were still in process during the failure, and use the intent log to help recover from the failure, usually by either undoing a partially completed operation, or by redoing one that might need to be completed.[2][3]
See also
References
- ↑ "Understanding intent logging". Uw714doc.sco.com. 2004-04-22. http://uw714doc.sco.com/en/HANDBOOK/fsC.intentlog.html. Retrieved 2014-03-07.
- ↑ 2.0 2.1 Aaron Toponce (2013-04-19). "ZFS Administration, Appendix A- Visualizing The ZFS Intent LOG (ZIL)". Pthree.org. https://pthree.org/2013/04/19/zfs-administration-appendix-a-visualizing-the-zfs-intent-log/. Retrieved 2014-03-07.
- ↑ "About the Veritas File System intent log". Sort.symantec.com. https://sort.symantec.com/public/documents/sfha/6.1/solaris/productguides/html/sf_admin/ch01s04s01.htm. Retrieved 2014-03-07.
 |  |
