Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
May the source be with you, but remember the KISS principle ;-)
Bigger doesn't imply better. Bigger often is a sign of obesity, of lost control, of overcomplexity, of cancerous cells



Unix filesystems

Recommended Books

Recommended Links



Ext2/Ext3 File System

Snapper In-place conversion from ext3/4       Sysadmin Horror Stories Humor Etc

Btrfs (B-tree FS or Butter FS as in "I Can't Believe This is Butter!" hinting to competition with ZFS) tried to provide Linux an enterprise class file system (the role, for which previously ReiserFS was shooting  before Hans Reiser went to prison for killing his former wife). Like ReiserFS, ZFS and NTFS it is a B-tree based filesystem.

Competition with ZFS was the main driver in development and Btrfs provides  the set of features very similar to ZFS. As of 2012 it is close to production quality and actually was included in SLES 11 SP2 (which was essentially a beta misnamed as a production release ;-). As of Linux 3.2 (released January 4, 2012), Btrfs implements:

  1. Online defragmentation
  2. Online volume growth and shrinking
  3. Online block device addition and removal
  4. Online balancing (movement of objects between block devices to balance load)
  5. RAID0, RAID1, and RAID10
  6. Subvolumes (one or more separately mountable filesystem roots within each physical partition)
  7. Transparent compression (zlib and LZO)
  8. Snapshots (read-only[23] or copy-on-write clones of subvolumes)
  9. File cloning (copy-on-write on individual files, or byte ranges thereof)
  10. Checksums on data and metadata (CRC-32C[24])
  11. In-place conversion (with rollback) from ext3/4 to Btrfs[25]
  12. File system seeding[26] (Btrfs on read-only storage used as a copy-on-write backing for a writeable Btrfs)
  13. Block discard support (reclaims space on some virtualized setups and improves wear leveling on SSDs with TRIM)
  14. Offline filesystem check[27]

Chris Mason, who moved to Oracle from Suse in 2007 started the project the same year . Oracle has released the project under the GPL license. Paradoxically Oracle bought Sun and now owns ZFS so this is kind of internal compertition between two projects. Still Mason and Oracle decided to move on with Btrfs development. Here is a relevant quote from A short history of btrfs []

At the same time that Chris was figuring out the technical design of btrfs, he was also figuring out how to fund the development of btrfs in both the short and the long term. Chris had recently moved from SUSE to a special Linux group at Oracle, one that employs several high-level Linux storage developers, including Martin K. Petersen, Zach Brown, and Jens Axboe. Oracle funds a lot of Linux development, some of it obviously connected to the Oracle database (OCFS2, DIF/DIX), and some of it less so (generic block layer work, syslets). Here's how Chris put it in a recent interview with Amanda McPherson from the Linux Foundation:

Amanda: Why did you start this project? Why is Oracle supporting this project so prominently?

Chris: I started Btrfs soon after joining Oracle. I had a unique opportunity to take a detailed look at the features missing from Linux, and felt that Btrfs was the best way to solve them.

Linux is a very important platform for Oracle. We use it heavily for our internal operations, and it has a broad customer base for us. We want to keep Linux strong as a data center operating system, and innovating in storage is a natural way for Oracle to contribute.

In other words, Oracle likes having Linux as a platform, and is willing to invest development effort in it even if it's not directly related to Oracle database performance. Look at it this way: how many operating systems are written and funded in large part by your competitors? While it is tempting to have an operating system entirely under your control - like Solaris - it also means that you have to pay for most of the development on that platform. In the end, Oracle believes it is in its own interest to use its in-house expertise to help keep Linux strong.

After a few months of hacking and design discussions with Zach Brown and many others, Chris posted btrfs for review. From there on out, you can trace the history of btrfs like any other open source project through the mailing lists and source code history. Btrfs is now in the mainline kernel and developers from Red Hat, SUSE, Intel, IBM, HP, Fujitsu, etc. are all working on it. Btrfs is a true open source project - not just in the license, but also in the community.

Btrfs has a gained a very large following within the Linux community and has whipped up a good deal of buzz. Some of the features of btrfs that have led to this buzz are:

SLES implementation

The SP3 update to SUSE Linux Enterprise 11 (SLES 11) also updates its Btrfs support for handling quotas with sub-volumes and also to provide faster snapshotting, better performance, and other newer Btrfs features. While SUSE has toyed with Btrfs on their enterprise platform, it isn't yet the default SLES file-system.

it is not default filesystem in SLES

It is default filesystem in OpenSuse and sysadmins used to ext2/ext/ext4 might make several mistakes installing it.

First of all btrfs is a merge of filesystem and lofical file manager.

So it does not make sense to subpurtion drive on partitions like /boot, /var, etc like in ext3/ext4. Instread you create single partition mounted as /


Top Visited
Past week
Past month


Old News ;-)

[Mar 03, 2015] The SP3 update to SUSE Linux Enterprise 11 (SLES 11) also updates its Btrfs support

handling quotas with sub-volumes improved. It also to provide faster snapshotting, better performance, and other newer Btrfs features. While SUSE has toyed with Btrfs in SLES, it isn't yet the default file-system.

[Nov 27, 2012] Rollback To A Working State With btrfs + apt-btrfs-snapshot On Ubuntu 12.10 by Falko Timme

Nov 26, 2012 | HowtoForge - Linux Howtos and Tutorials

This tutorial explains how you can revert failed apt operations (like apt-get upgrade) and roll back to the previous system state with apt-btrfs-snapshot on an Ubuntu 12.10 system that uses the btrfs file system. apt-btrfs-snapshot creates a snapshot of the system before the apt operation. Being able to easily restore the previous system state after a failed apt operation takes away much of the pain system administrators have to deal with normally and is one of the greatest features of the btrfs file system.

[Sep 07, 2012] Linux Don't Need No Stinkin' ZFS BTRFS Intro & Benchmarks Linux Magazine

Copy on Write yes
Snapshots yes
Snapshots of snapshots yes
Performance degradation at near 98-100% disk usage Most likely yes
Block level compression Currently a mount option
Disk encryption Planned but not currently in kernel. Encryptfs could be an option
Online resizing yes
Online defragmentation yes
Write checksums yes
Built-in RAID yes (0, 1, 10)
ACL yes
Direct IO Writes yes. Reads No – Planned
Quotas yes

[Mar 16, 2012] SUSE Linux Enterprise Server 11 SP2 review by Koen Vervloesem

Mar 14, 2012 |

Such a big jump in kernel version between service packs is not common for enterprise Linux distributions, which are usually quite conservative. For instance, Red Hat Enterprise Linux 5 is still using kernel version 2.6.18, even for its 8th update (RHEL 5.8), released a week after SLES 11 SP2, and in the same way RHEL 6.2 is still using kernel version 2.6.32. Of course these kernel versions contain a lot of backported features from newer kernel versions, but it's a lot of work to patch these features in and to keep maintaining them.

Instead of backporting and maintaining all those interesting features, SUSE's engineers have decided to use Linux 3.0 for SLES 11 SP2. This wasn't done rashly: they did an extensive code review of Linux 3.0 and verified that the kernel's Application Binary Interface (ABI) is completely compatible with SLE 11′s original 2.6.27 kernel. This guarantees that all software that ran on this kernel can expect exactly the same behaviour from the newer kernel release. So any software that has been certified for SLE 11 is still certified for SLE 11 SP2.

Ext3 is still the distro's default filesystem, but this is the first time Btrfs (which was introduced as a technology preview in SP1) is officially supported. However, SP2 still uses GRUB Legacy which can't boot from Btrfs, so when you choose Btrfs in the installer, SLE uses it as your root file system but creates a /boot partition with an Ext3 filesystem.

SUSE has also integrated the Snapper tool that it introduced in openSUSE 12.1 to manage Btrfs snapshots and rollbacks. The basic idea of Snapper is that it automatically creates a snapshot before and after running YaST or Zypper, compares the two snapshots and therefore provides the means to revert the differences between these two snapshots. You can list all the snapshots, see the differences between snapshots and roll them back using a user-friendly YaST module or with the commandline snapper tool. There's just one caveat: because the boot partition doesn't use Btrfs, you can't roll back kernel updates or changes to the boot configuration.

Thanks to Snapper, you can mess up system configuration changes or package installations or updates without having to restore from an old backup and risking to lose some files. Just revert to the snapshot before your problematic change and you're fine. But Snapper also helps with audits: it's very easy to discover which changes were made by which YaST or Zypper transaction. Snapper also creates cron jobs for periodic snapshots (which is configurable), so you'll be able to undo other manual changes too.

SP2 still offers Xen and KVM for virtualization, but it also introduces support for LXC (Linux containers), which is a form of operating system-level virtualization: when you create LXC containers, they are separate virtual servers, but all running on the same underlying Linux kernel of the host system. This lightweight virtualization method has a negligible overhead, as it's essentially a "chroot on steroids". On SP2, you can use LXC to isolate various system services from each other.

Recommended Links

Google matched content

Softpanorama Recommended

Top articles


Btrfs - Wikipedia, the free encyclopedia

Main Page - btrfs Wiki

Project- Btrfs - - Free and Open Source Software

btrfs - Community Ubuntu Documentation

A short history of btrfs [] (2009)


"btrfs- Readonly snapshots"



Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy


War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes


Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law


Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

Copyright © 1996-2018 by Dr. Nikolai Bezroukov. was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case is down you can use the at


The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: October 15, 2018