Linux Containers Authors: Elizabeth White, Mano Marks, Pat Romanski, Carmen Gonzalez, Mark Ross-Smith

Related Topics: Linux Containers, Open Source Cloud, Containers Expo Blog

Linux Containers: Article

ZFS on Linux

How ZFS on Linux compares to ZFS on Illumos or FreeBSD

On March 27, 2013, ZoL maintainers announced that the 0.6.1 release was ready for wide scale deployment on everything from desktops to servers. Yet, due to lack of maturity and adoption of the ZoL project, maintainers and/or advocates of ZFS aren't comfortable to run ZoL in production yet.

The reason behind the reluctance to use ZoL in production is that ZFS on Solaris took a large number of years to reach maturity and went through ups and downs of bugs related to data corruption and other issues. In the same way, ZoL will need some time to mature as product. It will take about a year to be mature as more people deploy it in production. If developers want to take advantage of ZFS, they can start rolling out less important database servers (i.e. reporting servers, 3rd slave databases) into production and experience the product for about 6 months before rolling out to all database servers. This will give users the confidence and experience to work with ZoL. Alternatively, developers may want to run ZFS on OmniOS because it's been battle tested for decades now.

How ZFS on Linux Compares to ZFS on Illumos or FreeBSD
The implementation of ZFS on Linux when compared to running ZFS on Illumos or FreeBSD is not very different from the perspective of the system administrator. The management and general usage is nearly identical. The only differences are OS specific functionality. For example, on FreeBSD if a user wants to use a zvol for swap space, he/she sets the org.freebsd:swap=on property on the zvol to turn swap on. On Linux, a developer would create a vanilla zvol and set up swap like any other partition with mkswap and swapon. Under the latest versions of all three operating systems mentioned, the Zpool version is at the same level, which is to say based on zpool v28 with additional features added by way of feature flags. They are compatible, users can create a zpool on Illumos/OmniOS, use it, export it, move the disks to a FreeBSD server, import the zpool, use it, export it, move to a Linux server, import the zpool, use it, etc. This exact scenario is something we have done at OmniTI and it worked without a hitch. One issue however is that the ACL support/usability is different on each OS so you'd the user will likely have to clean up the permissions a bit.

Caveats for Running ZFS on Arch Linux in a Production Environment
ZFS under Arch Linux is not part of the main package repository. As ZFS and its utilities are maintained by a third party, developers must rely on the third party to keep the packages up to date. One issue is that every time a new kernel is released (frequently) the ZFS kernel modules must be rebuilt as well. If the company upgrades its system (pacman -Syu) and reboots, but the ZFS modules were not recompiled well, Zpools will not initialize. This becomes especially important when developers have the rootfs under ZFS since this would leave the system unbootable and the user would be forced to recover by means of Rescue CD or, in the case of AWS, moving the EBS volumes to another instance and recovering from there. Linux does have a mechanism for automating this process other than DKMS. However, the arch zfs-modules-dkms package that provides this functionality is not kept up to date, and shouldn't be used.

Also, as briefly mentioned above, it should be noted that one cannot boot directly from ZFS on Linux, users must maintain a Linux bootloader compatible file system for /boot such as ext[234].

Currently, many of the utilities that output information about the filesystem are not ZFS aware and developers can get strange results running commands such as "df" for example, since it does not know the relationship between datasets and their parents. These will not necessarily prevent anything from running, but it is worth noting. Generally it's best to use "zfs list" rather than "df" to get accurate results.

ZFS natively uses NFSv4-style ACLs and is not compatible with Posix-style ACLs. Any applications that rely on Posix-style ACLs will have issues. Default GNU utilities like "ls" for example are not NFSv4 ACL aware.

Lastly, the ZoL project proclaims that ZFS on Linux is production ready, however it is worthwhile to note that it is still very immature at this point. ZFS itself has been around and tested for quite some time and is mature, so be careful and test before using it in a production environment.

How To Install ZFS on Arch with RootFS on ZFS
The Arch Wiki page for Installing Linux on ZFS goes into great detail on how to install Linux on ZFS. The key points are as follows:

  • The ZFS utilities and kernel modules must be built/installed prior to beginning the installation (within the CD Boot environment)
  • Even though you can have the Root FS on ZFS, the Linux bootloaders cannot load the kernel from ZFS currently so you still need a small ext2/3 partition for /boot to hold the kernel, the initramfs, and files that the bootloader requires.
  • There is no "beadm" in Linux to support multiple Boot Environment snapshots currently. One of the benefits of ZFS on Illumos/OmniOS is the ability to rollback to an earlier boot environment when applying updates.
  • When building the initramfs image, the zfs hook must come before the filesystems hook and you should not use the fsck hook at all.
  • You need to enable the ZFS service in systemd as this is not enabled by default. Under a ZFS Root system, this is very important if you like your systems to boot.
  • The "kernel" line of the bootloader needs to include a parameter telling the kernel where the root FS resides. For example, if the root FS is on a Zpool named "rpool" and its dataset is rpool/ROOT/default, then this parameter would be zfs=rpool/ROOT/default.

It is important to remember to export the zpool prior to rebooting after installation otherwise ZFS will complain that the system is different and will not import itself. This is because the new system is, in fact, a different system than the CD Media boot environment. Also, it's a very good idea to rebuild the initramfs (mkinitcpio -p linux) right away once you log into the installed system for the first time to avoid any "pool may be in use" errors due to differences in the CD Media Boot environment when the ramdisk was created initially.

Included at the end of this article are portions of a script used to build ArchLinux on ZFS. The only parts that have been removed are things that are specific to my environment. This is given as an example only to illustrate the steps that can be used, but note that it may or may not match the methods typically used for your environment.

ZFS on Linux Main Page: http://zfsonlinux.org

Arch Wiki - Installing Linux on ZFS: https://wiki.archlinux.org/index.php/Installing_Arch_Linux_on_ZFS

Arch Wiki - ZFS: https://wiki.archlinux.org/index.php/ZFS

Appendix A - Excerpts from Vagrant install script

The following are the commands we use when installing ZFS on ArchLinux under Vagrant. The Vagrant specific bits have been removed as they would not apply for installation on a production server. The full script can be found here: https://github.com/Loki22/scripts/blob/master/Vagrant/archzfs_vagrant_install.sh

pacman -Syy

pacman -S --noconfirm base-devel

mkdir /root/build

cd /root/build

wget https://aur.archlinux.org/packages/sp/spl-utils/spl-utils.tar.gz

wget https://aur.archlinux.org/packages/sp/spl/spl.tar.gz

wget https://aur.archlinux.org/packages/zf/zfs-utils/zfs-utils.tar.gz

wget https://aur.archlinux.org/packages/zf/zfs/zfs.tar.gz

for i in spl-utils spl zfs-utils zfs


cd /root/build && tar zxvf ${i}.tar.gz

cd /root/build/${i}

makepkg -s --asroot --noconfirm && pacman -U --noconfirm ./${i}*.pkg.tar.xz


# Install packages needed for ZFS

pacman -S --noconfirm archzfs dosfstools gptfdisk

# Clear the disk and initialize in GPT Format

sgdisk -o -g /dev/sda

# Partitioning - 3 Partitions (BIOS Boot Partition, /boot, and ZFS)

sgdisk -n 2:2048:+512M -c 2:"Linux Boot Partition" -t 2:8300 /dev/sda

sgdisk -n 3:0:0 -c 3:"ZFS Root Pool" -t 3:bf00 /dev/sda

sgdisk -n 1:34:2047 -c 1:"BIOS Boot Partition" -t 1:ef02 /dev/sda

# Create filesystem for /boot partition

mkfs.ext4 -L BOOT /dev/sda2

# Set up the ZFS Root Pool

modprobe zfs

zpool create rpool /dev/sda3

zfs set checksum=fletcher4 rpool

zfs set atime=off rpool

zfs set compression=lzjb rpool

zfs set mountpoint=none rpool

zpool export rpool

zpool import -d /dev/disk/by-id -R /mnt rpool

# Set up the initial BE (linux doesn't have beadm at this point, but not a bad idea to think ahead)

zfs create rpool/ROOT

zfs create -o mountpoint=/ rpool/ROOT/default

zpool set bootfs=rpool/ROOT/default rpool

# Set up datasets that are not part of the BE

zfs create -o mountpoint=/home -o setuid=off rpool/home

zfs create -o mountpoint=/root -o setuid=off rpool/roothome

# Create swap (example here is 2GB, use 4K block size for 64 bit systems)

zfs create -V 2G -b 4K rpool/swap

mkswap -Lswap -f /dev/rpool/swap

swapon /dev/rpool/swap

# Mount /boot

mkdir /mnt/boot

mount /dev/sda2 /mnt/boot

# Change ZFS repo to core now that we have it installed. This is so the new system will use updated modules linked to the new kernel as opposed to the somewhat more stale kernel that is used on the Install CD.

sed -i 's/demz-repo-archiso/demz-repo-core/' /etc/pacman.conf

# Bootstrap the new installation

pacstrap /mnt base base-devel archzfs sudo gnupg vim

# Generate the fstab minus the ZFS bits of which mounting is handled by ZFS

genfstab -U -p /mnt | grep boot >> /mnt/etc/fstab

# Configuration

CHROOT="arch-chroot /mnt"

# Hostname

echo "myhostname" > /mnt/etc/hostname

# Timezone and Clock

ln -s /usr/share/zoneinfo/America/New_York /mnt/etc/localtime

hwclock --systohc --utc

# Locale

sed -i 's/^#\(en_US.*\)/\1/' /mnt/etc/locale.gen

$CHROOT locale-gen

echo 'LANG="en_US.UTF-8"' > /mnt/etc/locale.conf

# Keymap

echo "KEYMAP=us" > /mnt/etc/vconsole.conf

# Mkinitcpio

sed -i 's/^\(HOOKS.*\)filesystems keyboard fsck/\1keyboard zfs filesystems/' /mnt/etc/mkinitcpio.conf

$CHROOT mkinitcpio -p linux

# Enable ZFS at boot

$CHROOT systemctl enable zfs.service

# Install GRUB

$CHROOT pacman -S --noconfirm grub-bios

modprobe dm-mod

$CHROOT grub-install --target=i386-pc --recheck --debug /dev/sda

cp /mnt/usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /mnt/boot/grub/locale/en.mo

mv /mnt/boot/grub/grub.cfg /mnt/boot/grub/grub.cfg.orig

cat > /mnt/boot/grub/grub.cfg <<EOF

set timeout=2

set default=0

# (0) Arch Linux

menuentry "Arch Linux" {

set root=(hd0,2)

linux /vmlinuz-linux zfs=rpool/ROOT/default

initrd /initramfs-linux.img


# (1) Arch Linux (fallback)

menuentry "Arch Linux - Fallback" {

set root=(hd0,2)

linux /vmlinuz-linux zfs=rpool/ROOT/default

initrd /initramfs-linux-fallback.img




$CHROOT pacman -S --noconfirm openssh

ln -s '/usr/lib/systemd/system/sshd.service' \


# Networking on installed system

# Manual linking because systemd isn't running yet

# Run 'ip link' to check the network interface and make sure it's enp0s3

ln -s '/usr/lib/systemd/system/dhcpcd@.service' \

[email protected]rvice'

# Clean up

# Remove downloaded packages

$CHROOT pacman -Scc --noconfirm

# Set your root password

passwd root

# Unmount filesystems, change ZFS mountpoints, and reboot

umount /mnt/boot

zfs umount -a

zpool export rpool

echo "If there were no errors, it would now be safe to reboot into the new system."

Appendix B - Recovery process if ZFS modules are not rebuilt on kernel upgrade
As mentioned above, the ZFS modules need to be rebuilt on every kernel upgrade. If this isn't done, you need to recover from a rescue environment. The recovery process (assuming booting from CD) is to build the ZFS modules/utils from the AUR (spl-utils, spl, zfs-utils, and zfs) in the temporary rescue environment, loading the ZFS module, mounting the Zpool under /mnt, mounting the /boot FS at /mnt/boot, chrooting, building the ZFS modules/utils again against the kernel in the chroot environment, rebuilding initramfs (mkinitcpio -p linux), and rebooting. Needless to say, not fun while people are screaming at you because the production server is down. This problem will be alleviated at some point when the ZFS packages are adopted into the main repositories and maintained with the rest of the release process.

More Stories By Kevin Loukinen

Kevin Loukinen is Site Reliability Engineer at OmniTI. Prior to that, he worked both as a Systems Administrator and Network Administrator for more than 12 years across several industries (financial, government and telecommunications).

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@ThingsExpo Stories
In his General Session at 16th Cloud Expo, David Shacochis, host of The Hybrid IT Files podcast and Vice President at CenturyLink, investigated three key trends of the “gigabit economy" though the story of a Fortune 500 communications company in transformation. Narrating how multi-modal hybrid IT, service automation, and agile delivery all intersect, he will cover the role of storytelling and empathy in achieving strategic alignment between the enterprise and its information technology.
Buzzword alert: Microservices and IoT at a DevOps conference? What could possibly go wrong? In this Power Panel at DevOps Summit, moderated by Jason Bloomberg, the leading expert on architecting agility for the enterprise and president of Intellyx, panelists peeled away the buzz and discuss the important architectural principles behind implementing IoT solutions for the enterprise. As remote IoT devices and sensors become increasingly intelligent, they become part of our distributed cloud enviro...
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place June 6-8, 2017, at the Javits Center in New York City, New York, is co-located with 20th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry p...
"LinearHub provides smart video conferencing, which is the Roundee service, and we archive all the video conferences and we also provide the transcript," stated Sunghyuk Kim, CEO of LinearHub, in this SYS-CON.tv interview at @ThingsExpo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Things are changing so quickly in IoT that it would take a wizard to predict which ecosystem will gain the most traction. In order for IoT to reach its potential, smart devices must be able to work together. Today, there are a slew of interoperability standards being promoted by big names to make this happen: HomeKit, Brillo and Alljoyn. In his session at @ThingsExpo, Adam Justice, vice president and general manager of Grid Connect, will review what happens when smart devices don’t work togethe...
"There's a growing demand from users for things to be faster. When you think about all the transactions or interactions users will have with your product and everything that is between those transactions and interactions - what drives us at Catchpoint Systems is the idea to measure that and to analyze it," explained Leo Vasiliou, Director of Web Performance Engineering at Catchpoint Systems, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York Ci...
The 20th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held June 6-8, 2017, at the Javits Center in New York City, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Containers, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportunity. Submit your speaking proposal ...
Discover top technologies and tools all under one roof at April 24–28, 2017, at the Westin San Diego in San Diego, CA. Explore the Mobile Dev + Test and IoT Dev + Test Expo and enjoy all of these unique opportunities: The latest solutions, technologies, and tools in mobile or IoT software development and testing. Meet one-on-one with representatives from some of today's most innovative organizations
20th Cloud Expo, taking place June 6-8, 2017, at the Javits Center in New York City, NY, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy.
SYS-CON Events announced today that Super Micro Computer, Inc., a global leader in Embedded and IoT solutions, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 7-9, 2017, at the Javits Center in New York City, NY. Supermicro (NASDAQ: SMCI), the leading innovator in high-performance, high-efficiency server technology, is a premier provider of advanced server Building Block Solutions® for Data Center, Cloud Computing, Enterprise IT, Hadoop/Big Data, HPC and E...
SYS-CON Events announced today that Linux Academy, the foremost online Linux and cloud training platform and community, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Linux Academy was founded on the belief that providing high-quality, in-depth training should be available at an affordable price. Industry leaders in quality training, provided services, and student certification passes, its goal is to c...
WebRTC is the future of browser-to-browser communications, and continues to make inroads into the traditional, difficult, plug-in web communications world. The 6th WebRTC Summit continues our tradition of delivering the latest and greatest presentations within the world of WebRTC. Topics include voice calling, video chat, P2P file sharing, and use cases that have already leveraged the power and convenience of WebRTC.
"Matrix is an ambitious open standard and implementation that's set up to break down the fragmentation problems that exist in IP messaging and VoIP communication," explained John Woolf, Technical Evangelist at Matrix, in this SYS-CON.tv interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
WebRTC sits at the intersection between VoIP and the Web. As such, it poses some interesting challenges for those developing services on top of it, but also for those who need to test and monitor these services. In his session at WebRTC Summit, Tsahi Levent-Levi, co-founder of testRTC, reviewed the various challenges posed by WebRTC when it comes to testing and monitoring and on ways to overcome them.
"A lot of times people will come to us and have a very diverse set of requirements or very customized need and we'll help them to implement it in a fashion that you can't just buy off of the shelf," explained Nick Rose, CTO of Enzu, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
DevOps is being widely accepted (if not fully adopted) as essential in enterprise IT. But as Enterprise DevOps gains maturity, expands scope, and increases velocity, the need for data-driven decisions across teams becomes more acute. DevOps teams in any modern business must wrangle the ‘digital exhaust’ from the delivery toolchain, "pervasive" and "cognitive" computing, APIs and services, mobile devices and applications, the Internet of Things, and now even blockchain. In this power panel at @...
Every successful software product evolves from an idea to an enterprise system. Notably, the same way is passed by the product owner's company. In his session at 20th Cloud Expo, Oleg Lola, CEO of MobiDev, will provide a generalized overview of the evolution of a software product, the product owner, the needs that arise at various stages of this process, and the value brought by a software development partner to the product owner as a response to these needs.
WebRTC services have already permeated corporate communications in the form of videoconferencing solutions. However, WebRTC has the potential of going beyond and catalyzing a new class of services providing more than calls with capabilities such as mass-scale real-time media broadcasting, enriched and augmented video, person-to-machine and machine-to-machine communications. In his session at @ThingsExpo, Luis Lopez, CEO of Kurento, introduced the technologies required for implementing these idea...
The WebRTC Summit New York, to be held June 6-8, 2017, at the Javits Center in New York City, NY, announces that its Call for Papers is now open. Topics include all aspects of improving IT delivery by eliminating waste through automated business models leveraging cloud technologies. WebRTC Summit is co-located with 20th International Cloud Expo and @ThingsExpo. WebRTC is the future of browser-to-browser communications, and continues to make inroads into the traditional, difficult, plug-in web co...
Internet of @ThingsExpo, taking place June 6-8, 2017 at the Javits Center in New York City, New York, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. @ThingsExpo New York Call for Papers is now open.