|Developer(s)||Miklos Szeredi, Open Source Community|
|Full name||Overlay File System|
|File system permissions||POSIX|
|Supported operating systems||Linux, FreeBSD and NetBSD|
The need and specification of a kernel mode Linux union mount filesystem was identified in late 2009. The initial RFC patchset of OverlayFS was submitted by Miklos Szeredi in 2010. By 2011, OpenWrt had already adopted it for their use.
The main mechanics of OverlayFS relate to the merging of directory access when both filesystems present a directory for the same name. Otherwise, OverlayFS presents the object, if any, yielded by one or the other, with the "upper" filesystem taking precedence. Unlike some other overlay filesystems, the directory subtrees being merged by OverlayFS do not necessarily have to be from distinct filesystems.
OverlayFS does not support renaming files without performing a full copy-up of the file, however renaming directories in an upper filesystem has limited support.
OverlayFS does not support merging changes from an upper filesystem to a lower filesystem.
- Aurora, Valerie (March 18, 2009). "Unioning file systems: Architecture, features, and design choices". LWN.net. Retrieved 2018-01-17.
- Edge, Jake (September 1, 2010). "Another union filesystem approach". LWN.net. Retrieved 2018-01-17.
- Corbet, Jonathan (June 15, 2011). "Debating overlayfs". LWN.net. Retrieved 2018-01-17.
- "OverlayFS commit to Linux".
- "OverlayFS Proposed For The Linux 3.18 Kernel".
- "Select a storage driver - Docker". archive.is. 2016-12-06. Archived from the original on 2016-12-06. Retrieved 2017-06-05.CS1 maint: BOT: original-url status unknown (link)
- "slackware:liveslak - SlackDocs". docs.slackware.com. Retrieved 2017-06-05.
- "OverlayFS documentation". kernel.org.