Write Ahead Physical Block Logging
Write Ahead Physical Block Logging (WAPBL) provides meta data journaling for file systems in conjunction with Fast File System (FFS) to accomplish rapid filesystem consistency after an unclean shutdown of the filesystem and better general use performance over regular FFS. With the journal, fsck is no longer required at system boot; instead, the system can replay the journal in order to correct any inconsistencies in the filesystem if the system has been shutdown in an unclean fashion.
- Wasabi Systems Inc. (2008). "Wasabi JFS".
- Federico Biancuzzi (2008-05-18). "NetBSD WAPBL". O'Reilly Media. Retrieved 2019-03-24.
- The NetBSD Foundation, Inc. (2008–2012). "WAPBL(4) — Write Ahead Physical Block Logging file system journaling". BSD Cross Reference. NetBSD. Lay summary.CS1 maint: date format (link)
- The NetBSD Foundation, Inc. (2015). "WAPBL(9) — write-ahead physical block logging for file systems". BSD Cross Reference. NetBSD. Lay summary.
- The NetBSD Foundation, Inc. (2008). "sys/wapbl.h". BSD Cross Reference. NetBSD.
- The NetBSD Project (2009-04-29). "Announcing NetBSD 5.0". NetBSD.
Some highlights are: a preview of metadata journaling for FFS file systems (known as WAPBL, Write Ahead Physical Block Logging)
- The NetBSD Project (2012-10-17). "Components removed from NetBSD". Announcing NetBSD 6.0. NetBSD.
“softdep” support is no longer available in FFS; use wapbl(4) logging instead.
- Adam Hamsik (2009-02-23). "Soft dependencies removed". NetBSD.
|This computer-storage-related article is a stub. You can help Wikipedia by expanding it.|