1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

OverlayFS File-System Proposed For Linux 3.10 Kernel

Linux Kernel

Published on 13 March 2013 08:32 PM EDT
Written by Michael Larabel in Linux Kernel
7 Comments

The Overlay File-System has been in development for several years and is used by some notable Linux distributions, but has yet to be merged into the mainline Linux kernel after having to be pulled a few times in the past. The new plan is to merge OverlayFS for the Linux 3.10 kernel.

With the patches now up to their sixteenth revision, Miklos Szeredi has called upon Linus Torvalds and Al Viro (the VFS maintainer) to consider pulling OverlayFS for inclusion into the Linux 3.10 release.

Szeredi writes in his latest plea with the Linux kernel developers, "It's included in Ubuntu and openSUSE, used by OpenWrt and various other projects. I regularly get emails asking when it will be included in mainline."

Introducing the new Linux file-system is made-up of thirteen patches and the v16 revision to them can be found on the kernel mailing list.

As far as the Overlay File-System approach to a union file-system, the kernel documentation describes itself:
This document describes a prototype for a new approach to providing overlay-filesystem functionality in Linux (sometimes referred to as union-filesystems). An overlay-filesystem tries to present a filesystem which is the result over overlaying one filesystem on top of the other.

The result will inevitably fail to look exactly like a normal filesystem for various technical reasons. The expectation is that many use cases will be able to ignore these differences.

This approach is 'hybrid' because the objects that appear in the filesystem do not all appear to belong to that filesystem. In many cases an object accessed in the union will be indistinguishable from accessing the corresponding object from the original filesystem. This is most obvious from the 'st_dev' field returned by stat(2).

While directories will report an st_dev from the overlay-filesystem, all non-directory objects will report an st_dev from the lower or upper filesystem that is providing the object. Similarly st_ino will only be unique when combined with st_dev, and both of these can change over the lifetime of a non-directory object. Many applications and tools ignore these values and will not be affected.
Linus Torvalds looks like he may finally pull the file-system for Linux 3.10. He already responded to the thread:
Yes, I think we should just do it. It's in use, it's pretty small, and the other alternatives are worse. Let's just plan on getting this thing done with.

Al, I realize you may not love this, but can you please give this alook? People clearly want to use it. In particular the new interfaces, like the inode ops open function with dentry passed in or whatever? The changes outside of overlayfs looked fine to me.
Al's response at the moment is, "I'll post a review tonight or tomorrow. FWIW, I was not too happy with it the last time I looked, but I'll obviously need to reread the whole thing."

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. CompuLab Intense-PC2: An Excellent, Fanless, Mini PC Powered By Intel's i7 Haswell
  2. From The Atom 330 To Haswell ULT: Intel Linux Performance Benchmarks
  3. AMD Radeon R9 285 Tonga Performance On Linux
  4. Apotop Wi-Copy
Latest Linux Articles
  1. AMD Moves Forward With Unified Linux Driver Strategy, New Kernel Driver
  2. MSI: Update Your BIOS From The Linux Desktop
  3. NVIDIA vs. AMD 2D Linux Drivers: Catalyst Is Getting Quite Good At 2D
  4. 15-Way GPU Comparison With Mesa 10.3 + Linux 3.17
Latest Linux News
  1. NVIDIA's NVPTX Support For GCC Is Close To Being Merged
  2. KDE's KWin On Wayland Begins Using Libinput
  3. Khronos Releases OpenVX 1.0 Specification
  4. Linux Kernel Working Towards GNU11/C11 Compatibility
  5. Ubuntu 15.04 Is Codenamed After A Monkey: Vivid Vervet
  6. Following GCC, Clang Looks To Default To C11
  7. Users/Developers Threatening Fork Of Debian GNU/Linux
  8. Linux 3.18-rc1 Released One Week Early With Many Changes
  9. The VC4 Gallium3D Driver Is Still Moving Along For The Raspberry Pi
  10. Direct3D 9 Support Might Land Within Mainline Mesa 3D Drivers
Latest Forum Discussions
  1. Users/Developers Threatening Fork Of Debian GNU/Linux
  2. HOPE: The Ease Of Python With The Speed Of C++
  3. NVIDIA Presents Its Driver Plans To Support Mir/Wayland & KMS On Linux
  4. AMD Is Restructuring Again, Losing 7% Of Employees
  5. Bye bye BSD, Hello Linux: A Sys Admin's Story
  6. Open-Source AMD Fusion E-350 Support Takes A Dive
  7. Upgrade to Kaveri, very slow VDPAU performance
  8. ChromeOS Drops Support For EXT2/EXT3/EXT4 File-Systems