Difference between pages "Download" and "ZFS Install Guide"

From Funtoo
(Difference between pages)
Jump to: navigation, search
(Download Funtoo Linux)
 
(letting users know to use 64 bit alternative kernel not the standard one)
 
Line 1: Line 1:
__NOTITLE__
+
== Introduction ==
= Download Funtoo Linux = i dont really knw anything im just think thats wat it is soo yea
+
  
Here are the steps you should follow to download Funtoo Linux stage3 tarball. If you need an install CD, please see [[Funtoo Linux Installation]] for Live Media recommendations. Funtoo Linux currently doesn't have its own LiveCD, but there are many that you can use for installation.
+
This tutorial will show you how to install Funtoo on ZFS (rootfs). This tutorial is meant to be an "overlay" over the [[Funtoo_Linux_Installation|Regular Funtoo Installation]]. Follow the normal installation and only use this guide for steps 2, 3, and 8.
  
== First, Pick a Mirror... ==
+
=== Introduction to ZFS ===
  
Funtoo Linux can be downloaded at the following locations:
+
Since ZFS is a new technology for Linux, it can be helpful to understand some of its benefits, particularly in comparison to BTRFS, another popular next-generation Linux filesystem:
  
* Main US mirror: [http://ftp.osuosl.org/pub/funtoo/ The Oregon State University Open Source Lab]
+
* On Linux, the ZFS code can be updated independently of the kernel to obtain the latest fixes. btrfs is exclusive to Linux and you need to build the latest kernel sources to get the latest fixes.
* Main EU mirror: [http://ftp.heanet.ie/mirrors/funtoo/ HEAnet]
+
* Main JP mirror: [http://mirrors.go-parts.com/funtoo/ Go-parts]
+
  
== Now... pick a build ==
+
* ZFS is supported on multiple platforms. The platforms with the best support are Solaris, FreeBSD and Linux. Other platforms with varying degrees of support are NetBSD, Mac OS X and Windows. btrfs is exclusive to Linux.
  
'''Now you'll first need to pick a ''build'' of Funtoo Linux to install.''' Builds are like different versions of Funtoo Linux. ''Our '''funtoo-current''' build is the most up-to-date and recommended build.'' We also offer '''funtoo-stable'''. Both current and stable share the use the same Portage tree (package repository), but newer packages are unmasked (made available for install) in '''funtoo-current'''.
+
* ZFS has the Adaptive Replacement Cache replacement algorithm while btrfs uses the Linux kernel's Last Recently Used replacement algorithm. The former often has an overwhelmingly superior hit rate, which means fewer disk accesses.
  
There is also a '''funtoo-experimental''', which contains our experimental development work. As you might guess, funtoo-experimental is for developers and testers only, and it has its own experimental Portage tree that is separate from the others.
+
* ZFS has the ZFS Intent Log and SLOG devices, which accelerates small synchronous write performance.
  
If you don't know which one to choose, pick '''funtoo-current'''.
+
* ZFS handles internal fragmentation gracefully, such that you can fill it until 100%. Internal fragmentation in btrfs can make btrfs think it is full at 10%. Btrfs has no automatic rebalancing code, so it requires a manual rebalance to correct it.
  
Picked one? Great! Open a mirror in a new window, and select the appropriate build directory from the list.
+
* ZFS has raidz, which is like RAID 5/6 (or a hypothetical RAID 7 that supports 3 parity disks), except it does not suffer from the RAID write hole issue thanks to its use of CoW and a variable stripe size. btrfs gained integrated RAID 5/6 functionality in Linux 3.9. However, its implementation uses a stripe cache that can only partially mitigate the effect of the RAID write hole.
  
<pre>
+
* ZFS send/receive implementation supports incremental update when doing backups. btrfs' send/receive implementation requires sending the entire snapshot.
funtoo-current ->
+
</pre>
+
  
== Next... pick an arch ==
+
* ZFS supports data deduplication, which is a memory hog and only works well for specialized workloads. btrfs has no equivalent.
  
'''Next, it's time to pick an ''architecture'''''. If you have a modern 64-bit PC-compatible desktop or server, you generally want '''x86-64bit'''.  If you have an older 32-bit PC-compatible desktop or server, you'll want to use '''x86-32bit'''. 32-bit is also an option for 64-bit x86 systems if you don't want or need 64-bit support.
+
* ZFS datasets have a hierarchical namespace while btrfs subvolumes have a flat namespace.
  
We also bundle virtualization directories alongside the architecture directories, so if you want to install an [[OpenVZ]] container of Funtoo Linux, select '''openvz''', then pick the correct ''architecture'' within. Likewise, if you're looking for a [[VagrantUp|Vagrant]] run image of Funtoo Linux, look in the '''vagrant''' directory.
+
* ZFS has the ability to create virtual block devices called zvols in its namespace. btrfs has no equivalent and must rely on the loop device for this functionality, which is cumbersome.
  
If you are installing Funtoo Linux on an ARM system, choose '''arm-32bit'''. Finally, if you are installing Funtoo Linux on a Sparc64 system, choose '''sparc-64bit'''.
+
The only area where btrfs is ahead of ZFS is in the area of small file
 +
efficiency. btrfs supports a feature called block suballocation, which
 +
enables it to store small files far more efficiently than ZFS. It is
 +
possible to use another filesystem (e.g. reiserfs) on top of a ZFS zvol
 +
to obtain similar benefits (with arguably better data integrity) when
 +
dealing with many small files (e.g. the portage tree).
 +
 
 +
=== Disclaimers ===
 +
 
 +
{{fancywarning|This guide is a work in progress. Expect some quirks.}}
 +
{{fancyimportant|'''Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms'''!}}
 +
 
 +
== Video Tutorial ==
 +
 
 +
As a companion to the install instructions below, a YouTube video ZFS install tutorial is now available:
 +
 
 +
{{#widget:YouTube|id=kxEdSXwU0ZI|width=640|height=360}}
 +
 
 +
== Downloading the ISO (With ZFS) ==
 +
In order for us to install Funtoo on ZFS, you will need an environment that provides the ZFS tools. Therefore we will download a customized version of System Rescue CD with ZFS already included. When booting, use the "alternate"-kernel. The ZFS-module won't work with the default kernel.  
  
 
<pre>
 
<pre>
funtoo-current -> x86-64bit
+
Name: sysresccd-3.8.1_zfs_0.6.2.iso  (510 MB)
 +
Release Date: 2013-11-03
 +
md5sum aa33ef61c5d85ad564372327940498c3
 
</pre>
 
</pre>
  
== Now... select a sub-arch ==
 
  
Now, you'll need to pick a ''sub-architecture'' of Funtoo Linux that suits your needs. A sub-architecture is a build of Funtoo Linux that is optimized for your particular CPU.  
+
'''[http://ftp.osuosl.org/pub/funtoo/distfiles/sysresccd/ Download System Rescue CD with ZFS]'''<br />
  
If you are building a Linux-based appliance or grabbing an image for mass-deployment, you might want to choose a generic sub-architecture that will be compatible with a wide range of processors. Otherwise, choose the most optimized sub-architecture that your processor supports.
+
== Creating a bootable USB from ISO ==
 +
After you download the iso, you can do the following steps to create a bootable USB:
  
Note that we offer the greatest number of choices for '''funtoo-current'''. Other builds will have a more limited number of sub-arches available.
+
<console>
 +
Make a temporary directory
 +
# ##i##mkdir /tmp/loop
  
=== x86-64bit ===
+
Mount the iso
 +
# ##i##mount -o ro,loop /root/sysresccd-3.7.1_zfs_0.6.2.iso /tmp/loop
  
* Intel
+
Run the usb installer
** '''corei7''': Intel Core i3, Core i5 and Core i7 desktop processors or higher. Xeon 5500, 5600 and 7500 series server processors or higher. (Nehalem, Sandy Bridge)
+
# ##i##/tmp/loop/usb_inst.sh
** '''core2_64''': Intel Core 2 series or higher, which include the Core 2 Solo, Duo, Quad and Extreme. Also suitable for Nehalem.
+
</console>
** '''atom_64''': Intel Atom optimized. Compatible with Core 2 series.
+
* AMD
+
** '''amd64-k10''': AMD Phenom, Phenom II and compatible, or higher
+
** '''amd64-k8''': AMD Opteron or Athlon 64 processors, or higher
+
* Generic
+
** '''generic_64''' : Generic 64-bit Intel/AMD processor
+
  
 +
That should be all you need to do to get your flash drive working.
  
=== pure64 ===
+
When you are booting into system rescue cd, make sure you select the '''alternative 64 bit kernel'''. ZFS support was specifically added to the alternative 64 bit kernel rather than the standard 64 bit kernel.
<pre>
+
funtoo-current -> pure64
+
</pre>
+
Special flavor of 64-bit stages, that building against pure64 profile, formerly known as no-multilib. 
+
* Intel
+
** '''corei7-pure64''': Intel Core i3, Core i5 and Core i7 desktop processors or higher. Xeon 5500, 5600 and 7500 series server processors or higher. (Nehalem, Sandy Bridge)
+
* Generic
+
** '''generic_64-pure64''' : Generic 64-bit Intel/AMD processor
+
  
=== x86-32bit ===
+
== Creating partitions ==
 +
There are two ways to partition your disk: You can use your entire drive and let ZFS automatically partition it for you, or you can do it manually.
  
*'''core2_32''': Intel Core 2 series or compatible, which include the Core 2 Solo, Duo, Quad and Extreme. Also suitable for Nehalem.
+
We will be showing you how to partition it '''manually''' because if you partition it manually you get to create your own layout, you get to have your own separate /boot partition (Which is nice since not every bootloader supports booting from ZFS pools), and you get to boot into RAID10, RAID5 (RAIDZ) pools and any other layouts due to you having a separate /boot partition.
*'''atom_32''': Intel Atom optimized. Compatible with Core 2 series.
+
*'''amd64-k8_32''': AMD Opteron or Athlon 64 processors, or higher.
+
*'''athlon-xp''': Athlon XP or Opteron/Athlon 64.
+
*'''i686''': Generic P6-class system (generic modern 32-bit)
+
*'''i486''': Intel 80486+ system (generic 32-bit)
+
  
=== arm-32bit ===
+
==== gdisk (GPT Style) ====
  
*'''armv6j_hardfp''': Hardware floating points ARMv6J architecture (Raspberry Pi, etc.).
+
'''A Fresh Start''':
*'''armv7a_hardfp''': Hardware floating points ARMv7A architecture (PandaBoard, ODROID-X2, ODROID-U2, etc.).
+
  
You should now grab the most recent stage3 for the sub-architecture that you've chosen:
+
First lets make sure that the disk is completely wiped from any previous disk labels and partitions.
 +
We will also assume that <tt>/dev/sda</tt> is the target drive.<br />
  
<pre>
+
<console>
funtoo-current -> x86-64bit -> corei7 -> stage3-latest.tar.xz
+
# ##i##gdisk /dev/sda
</pre>
+
 
 +
Command: ##i##x ↵
 +
Expert command: ##i##z ↵
 +
About to wipe out GPT on /dev/sda. Proceed?: ##i##y ↵
 +
GPT data structures destroyed! You may now partition the disk using fdisk or other utilities.
 +
Blank out MBR?: ##i##y ↵
 +
</console>
 +
 
 +
{{fancywarning|This is a destructive operation. Make sure you really don't want anything on this disk.}}
 +
 
 +
Now that we have a clean drive, we will create the new layout.
 +
 
 +
'''Create Partition 1''' (boot):
 +
<console>
 +
Command: ##i##n ↵
 +
Partition Number: ##i##↵
 +
First sector: ##i##↵
 +
Last sector: ##i##+250M ↵
 +
Hex Code: ##i##↵
 +
</console>
 +
 
 +
'''Create Partition 2''' (BIOS Boot Partition):
 +
<console>Command: ##i##n ↵
 +
Partition Number: ##i##↵
 +
First sector: ##i##↵
 +
Last sector: ##i##+32M ↵
 +
Hex Code: ##i##EF02 ↵
 +
</console>
 +
 
 +
'''Create Partition 3''' (ZFS):
 +
<console>Command: ##i##n ↵
 +
Partition Number: ##i##↵
 +
First sector: ##i##↵
 +
Last sector: ##i##↵
 +
Hex Code: ##i##bf00 ↵
 +
 
 +
Command: ##i##p ↵
 +
 
 +
Number  Start (sector)    End (sector)  Size      Code  Name
 +
  1            2048          514047  250.0 MiB  8300  Linux filesystem
 +
  2          514048          579583  32.0 MiB    EF02  BIOS boot partition
 +
  3          579584      1953525134  931.2 GiB  BF00  Solaris root
 +
 
 +
Command: ##i##w ↵
 +
</console>
 +
 
 +
 
 +
=== Format your boot volume ===
 +
Format your separate /boot partition:
 +
<console># ##i##mkfs.ext2 /dev/sda1</console>
 +
 
 +
=== Encryption (Optional) ===
 +
If you want encryption, then create your encrypted vault(s) now by doing the following:
 +
 
 +
<console>
 +
# ##i##cryptsetup luksFormat /dev/sda3
 +
# ##i##cryptsetup luksOpen /dev/sda3 vault_1
 +
</console>
 +
 
 +
=== Create the zpool ===
 +
We will first create the pool. The pool will be named `rpool` and the disk will be aligned to 4096 (using ashift=12)
 +
<console># ##i##zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sda3</console>
 +
 
 +
{{fancyimportant|If you are using encrypted root, change '''/dev/sda3 to /dev/mapper/vault_1'''.}}
 +
 
 +
{{fancynote|'''ashift<nowiki>=</nowiki>12''' should be use if you have a newer, advanced format disk that has a sector size of 4096 bytes. If you have an older disk with 512 byte sectors, you should use '''ashift<nowiki>=</nowiki>9''' or don't add the option for auto detection}}
 +
 
 +
{{fancynote|If you have a previous pool that you would like to import, you can do a: '''zpool import -f -R /mnt/funtoo <pool_name>'''}}
 +
 
 +
=== Create the zfs datasets ===
 +
We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: /home, /var, /usr/src, and /usr/portage.
 +
 
 +
<console>
 +
Create some empty containers for organization purposes, and make the dataset that will hold /
 +
# ##i##zfs create rpool/ROOT
 +
# ##i##zfs create -o mountpoint=/ rpool/ROOT/funtoo
 +
 
 +
Optional, but recommended datasets: /home
 +
# ##i##zfs create -o mountpoint=/home rpool/HOME
 +
 
 +
Optional, portage tree, distfiles, and binary packages:
 +
# ##i##zfs create rpool/FUNTOO
 +
# ##i##zfs create -o mountpoint=/usr/portage -o compression=off rpool/FUNTOO/portage
 +
# ##i##zfs create -o mountpoint=/usr/portage/distfiles rpool/FUNTOO/portage/distfiles
 +
# ##i##zfs create -o mountpoint=/usr/portage/packages rpool/FUNTOO/portage/packages
 +
 
 +
Optional datasets: /usr/src
 +
# ##i##zfs create -o mountpoint=/usr/src rpool/FUNTOO/src
 +
</console>
 +
 
 +
=== Create your swap zvol ===
 +
'''Make your swap +1G greater than your RAM. An 8G machine would have 9G of SWAP (This is kinda big though). For machines with this much memory, You could just make it 2G if you don't have any problems.'''
 +
<console>
 +
# ##i##zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -o volblocksize=4K -V 1G rpool/swap
 +
</console>
 +
 
 +
=== Format your swap zvol ===
 +
<console>
 +
# ##i##mkswap -f /dev/zvol/rpool/swap
 +
# ##i##swapon /dev/zvol/rpool/swap
 +
</console>
 +
 
 +
 
 +
=== Last minute checks and touches ===
 +
Check to make sure everything appears fine. Your output may differ depending on the choices you made above:
 +
<console>
 +
# ##i##zpool status
 +
  pool: rpool
 +
state: ONLINE
 +
  scan: none requested
 +
config:
 +
 
 +
        NAME        STATE    READ WRITE CKSUM
 +
        rpool      ONLINE      0    0    0
 +
          sda2      ONLINE      0    0    0
 +
 
 +
errors: No known data errors
 +
 
 +
# ##i##zfs list
 +
rpool              3.10G  15.5G  136K  none
 +
rpool/HOME          136K  15.5G  136K  /mnt/funtoo/home
 +
rpool/ROOT          308K  15.5G  136K  none
 +
rpool/ROOT/funtoo  172K  15.5G  172K  /mnt/funtoo
 +
rpool/swap        3.09G  18.6G    76K  -
 +
</console>
 +
 
 +
Now we will continue to install funtoo.
 +
 
 +
== Installing Funtoo ==
 +
[[Funtoo_Linux_Installation|Download and extract the Funtoo stage3 and continue installation as normal.]]
 +
 
 +
Then once you've extracted the stage3, chroot into your new funtoo environment:
 +
<console>
 +
Go into the directory that you will chroot into
 +
# ##i##cd /mnt/funtoo
 +
 
 +
Mount your boot drive
 +
# ##i##mount /dev/sda1 /mnt/funtoo/boot
 +
 
 +
Bind the kernel related directories
 +
# ##i##mount -t proc none /mnt/funtoo/proc
 +
# ##i##mount --rbind /dev /mnt/funtoo/dev
 +
# ##i##mount --rbind /sys /mnt/funtoo/sys
 +
 
 +
Copy network settings
 +
# ##i##cp /etc/resolv.conf /mnt/funtoo/etc/
 +
 
 +
chroot into your new funtoo environment
 +
# ##i##env -i HOME=/root TERM=$TERM chroot /mnt/funtoo /bin/bash --login
 +
 
 +
Place your mountpoints into your /etc/mtab file
 +
# ##i##cat /proc/mounts > /etc/mtab
 +
 
 +
Sync your tree
 +
# ##i##emerge --sync
 +
</console>
 +
 
 +
=== Add filesystems to /etc/fstab ===
 +
 
 +
Before we continue to compile and or install our kernel in the next step, we will edit the /etc/fstab file because if we decide to install our kernel through portage, portage will need to know where is your /boot so that it can place the files in there. We also need to update /etc/mtab so our system knows what is mounted
 +
 
 +
<console>
 +
# ##i##nano /etc/fstab
 +
 
 +
# <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>
 +
# Do not add the /boot line below if you are using whole-disk zfs
 +
/dev/sda1              /boot          ext2            defaults        0 2
 +
/dev/zvol/rpool/swap    none            swap            sw              0 0
 +
</console>
 +
 
 +
== Kernel Configuration ==
 +
To speed up this step, you can install "bliss-kernel" since it's already properly configured for ZFS and a lot of other configurations. The kernel is also compiled and ready to go. To install 'bliss-kernel' type the following:
 +
 
 +
<console>
 +
# ##i##emerge bliss-kernel
 +
</console>
 +
 
 +
Now make sure that your /usr/src/linux symlink is pointing to this kernel by typing the following:
 +
 
 +
<console>
 +
# ##i##eselect kernel list
 +
Available kernel symlink targets:
 +
[1]  linux-3.10.10-FB.01 *
 +
</console>
 +
 
 +
You should see a star next to the bliss-kernel version you installed. In this case it was 3.10.10-FB.01. If it's not set, you can type '''eselect kernel set #'''.
 +
 
 +
== Installing the ZFS userspace tools ==
 +
 
 +
<console># ##i##emerge -av zfs</console>
 +
 
 +
Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be displayed.
 +
 
 +
<console>
 +
# ##i##zpool status
 +
# ##i##zfs list
 +
</console>
 +
 
 +
If everything worked, continue.
 +
 
 +
== Install the bootloader ==
 +
=== GRUB 2 ===
 +
Before you do this, make sure this checklist is followed:
 +
* Installed kernel and kernel modules
 +
* Installed zfs package from the tree
 +
* /dev, /proc, /sys are mounted in the chroot environment
 +
 
 +
Once all this is checked, let's install grub2. First we need to enable the "libzfs" use flag so zfs support is compiled for grub2.
 +
 
 +
<console># ##i##echo "sys-boot/grub libzfs" >> /etc/portage/package.use</console>
 +
 
 +
Then we will compile grub2:
 +
 
 +
<console># ##i##emerge -av grub</console>
 +
 
 +
Once this is done, you can check that grub is version 2.00 by doing the following command:
 +
<console>
 +
# ##i##grub-install --version
 +
grub-install (GRUB) 2.00
 +
</console>
 +
 
 +
Now try to install grub2:
 +
<console># ##i##grub-install --no-floppy /dev/sda</console>
 +
 
 +
You should receive the following message
 +
<console>Installation finished. No error reported.</console>
 +
 
 +
If not, then go back to the above checklist.
 +
 
 +
=== LILO ===
 +
Before you do this, make sure the following checklist is followed:
 +
* /dev/, /proc and /sys are mounted.
 +
* Installed the sys-fs/zfs package from the tree.
 +
Once the above requirements are met, LILO can be installed.
 +
 
 +
Now we will install LILO.
 +
<console># ##i##emerge -av sys-boot/lilo</console>
 +
Once the installation of LILO is complete we will need to edit the lilo.conf file.
 +
<console># ##i##nano /etc/lilo.conf
 +
boot=/dev/sda
 +
prompt
 +
timeout=4
 +
default=Funtoo
 +
 
 +
image=/boot/bzImage
 +
      label=Funtoo
 +
      read-only
 +
      append="root=rpool/ROOT/funtoo"
 +
      initrd=/boot/initramfs
 +
</console>
 +
All that is left now is to install the bootcode to the MBR.
 +
 
 +
This can be accomplished by running:
 +
<console># ##i##/sbin/lilo</console>
 +
If it is successful you should see:
 +
<console>
 +
Warning: LBA32 addressing assumed
 +
Added Funtoo + *
 +
One warning was issued
 +
</console>
 +
 
 +
== Create the initramfs ==
 +
There are two ways to do this, you can use genkernel, or you can use my bliss initramfs creator. I will show you both.
 +
 
 +
=== genkernel ===
 +
<console>
 +
# ##i##emerge -av sys-kernel/genkernel
 +
# You only need to add --luks if you used encryption
 +
# ##i##genkernel --zfs --luks initramfs
 +
</console>
 +
 
 +
=== Bliss Initramfs Creator ===
 +
If you are encrypting your drives, then add the "luks" use flag to your package.use before emerging:
 +
 
 +
<console>
 +
# ##i##echo "sys-kernel/bliss-initramfs luks" >> /etc/portage/package.use
 +
</console>
 +
 
 +
Now install the creator:
 +
 
 +
<console>
 +
# ##i##emerge bliss-initramfs
 +
</console>
 +
 
 +
 
 +
Then go into the install directory, run the script as root, and place it into /boot:
 +
<console># ##i##cd /opt/bliss-initramfs
 +
# ##i##./createInit
 +
# ##i##mv initrd-<kernel_name> /boot
 +
</console>
 +
'''<kernel_name>''' is the name of what you selected in the initramfs creator, and the name of the outputted file.
 +
 
 +
== Using boot-update ==
 +
=== /boot on separate partition ===
 +
If you created a separate non-zfs partition for boot then configuring boot-update is almost exactly the same as a normal install except that auto detection for root does not work. You must tell boot-update what your root is.
 +
==== Genkernel ====
 +
If your using genkernel you must add 'real_root=ZFS=<root>' and 'dozfs' to your params.
 +
Example entry for boot.conf:
 +
<console>
 +
"Funtoo ZFS" {
 +
        kernel vmlinuz[-v]
 +
        initrd initramfs-genkernel-x86_64[-v]
 +
        params real_root=ZFS=rpool/ROOT/funtoo
 +
        params += dozfs
 +
        # Also add 'params += crypt_root=/dev/sda2' if you used encryption
 +
        # Adjust the above setting to your system if needed
 +
}
 +
</console>
 +
 
 +
==== Bliss Initramfs Creator ====
 +
If you used the Bliss Initramfs Creator then all you need to do is add 'root=<root>' to your params.
 +
Example entry for boot.conf:
 +
<console>
 +
"Funtoo ZFS" {
 +
        kernel vmlinuz[-v]
 +
        initrd initrd[-v]
 +
        params root=rpool/ROOT/funtoo quiet
 +
        # If you have an encrypted device with a regular passphrase,
 +
        # you can add the following line
 +
        params += enc_root=/dev/sda3 enc_type=pass
 +
}
 +
</console>
 +
 
 +
After editing /etc/boot.conf, you just need to run boot-update to update grub.cfg
 +
<console># ##i##boot-update</console>
 +
 
 +
=== /boot on ZFS ===
 +
TBC - pending update to boot-update to support this
 +
 
 +
== Final configuration ==
 +
=== Add the zfs tools to openrc ===
 +
<console># ##i##rc-update add zfs boot</console>
 +
 
 +
=== Clean up and reboot ===
 +
We are almost done, we are just going to clean up, '''set our root password''', and unmount whatever we mounted and get out.
 +
 
 +
<console>
 +
Delete the stage3 tarball that you downloaded earlier so it doesn't take up space.
 +
# ##i##cd /
 +
# ##i##rm stage3-latest.tar.xz
 +
 
 +
Set your root password
 +
# ##i##passwd
 +
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!
 +
 
 +
Get out of the chroot environment
 +
# ##i##exit
 +
 
 +
Unmount all the kernel filesystem stuff and boot (if you have a separate /boot)
 +
# ##i##umount -l proc dev sys boot
 +
 
 +
Turn off the swap
 +
# ##i##swapoff /dev/zvol/rpool/swap
 +
 
 +
Export the zpool
 +
# ##i##cd /
 +
# ##i##zpool export rpool
 +
 
 +
Reboot
 +
# ##i##reboot
 +
</console>
 +
 
 +
{{fancyimportant|'''Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.'''}}
 +
 
 +
and that should be enough to get your system to boot on ZFS.
 +
 
 +
== After reboot ==
 +
=== Create initial ZFS Snapshot ===
 +
Continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant.
 +
 
 +
To take the snapshot of your system, type the following:
 +
<console># ##i##zfs snapshot -r rpool@install</console>
 +
 
 +
To see if your snapshot was taken, type:
 +
<console># ##i##zfs list -t snapshot</console>
 +
 
 +
If your machine ever fails and you need to get back to this state, just type (This will only revert your / dataset while keeping the rest of your data intact):
 +
<console># ##i##zfs rollback rpool/ROOT/funtoo@install</console>
 +
 
 +
{{fancyimportant|'''For a detailed overview, presentation of ZFS' capabilities, as well as usage examples, please refer to the [[ZFS_Fun|ZFS Fun]] page.'''}}
 +
 
 +
[[Category:HOWTO]]
 +
[[Category:Filesystems]]
 +
[[Category:Featured]]
 +
 
 +
__NOTITLE__

Revision as of 21:37, 8 November 2013

Contents

Introduction

This tutorial will show you how to install Funtoo on ZFS (rootfs). This tutorial is meant to be an "overlay" over the Regular Funtoo Installation. Follow the normal installation and only use this guide for steps 2, 3, and 8.

Introduction to ZFS

Since ZFS is a new technology for Linux, it can be helpful to understand some of its benefits, particularly in comparison to BTRFS, another popular next-generation Linux filesystem:

  • On Linux, the ZFS code can be updated independently of the kernel to obtain the latest fixes. btrfs is exclusive to Linux and you need to build the latest kernel sources to get the latest fixes.
  • ZFS is supported on multiple platforms. The platforms with the best support are Solaris, FreeBSD and Linux. Other platforms with varying degrees of support are NetBSD, Mac OS X and Windows. btrfs is exclusive to Linux.
  • ZFS has the Adaptive Replacement Cache replacement algorithm while btrfs uses the Linux kernel's Last Recently Used replacement algorithm. The former often has an overwhelmingly superior hit rate, which means fewer disk accesses.
  • ZFS has the ZFS Intent Log and SLOG devices, which accelerates small synchronous write performance.
  • ZFS handles internal fragmentation gracefully, such that you can fill it until 100%. Internal fragmentation in btrfs can make btrfs think it is full at 10%. Btrfs has no automatic rebalancing code, so it requires a manual rebalance to correct it.
  • ZFS has raidz, which is like RAID 5/6 (or a hypothetical RAID 7 that supports 3 parity disks), except it does not suffer from the RAID write hole issue thanks to its use of CoW and a variable stripe size. btrfs gained integrated RAID 5/6 functionality in Linux 3.9. However, its implementation uses a stripe cache that can only partially mitigate the effect of the RAID write hole.
  • ZFS send/receive implementation supports incremental update when doing backups. btrfs' send/receive implementation requires sending the entire snapshot.
  • ZFS supports data deduplication, which is a memory hog and only works well for specialized workloads. btrfs has no equivalent.
  • ZFS datasets have a hierarchical namespace while btrfs subvolumes have a flat namespace.
  • ZFS has the ability to create virtual block devices called zvols in its namespace. btrfs has no equivalent and must rely on the loop device for this functionality, which is cumbersome.

The only area where btrfs is ahead of ZFS is in the area of small file efficiency. btrfs supports a feature called block suballocation, which enables it to store small files far more efficiently than ZFS. It is possible to use another filesystem (e.g. reiserfs) on top of a ZFS zvol to obtain similar benefits (with arguably better data integrity) when dealing with many small files (e.g. the portage tree).

Disclaimers

Warning: This guide is a work in progress. Expect some quirks.
Important: Since ZFS was really designed for 64 bit systems, we are only recommending and supporting 64 bit platforms and installations. We will not be supporting 32 bit platforms!

Video Tutorial

As a companion to the install instructions below, a YouTube video ZFS install tutorial is now available:

Downloading the ISO (With ZFS)

In order for us to install Funtoo on ZFS, you will need an environment that provides the ZFS tools. Therefore we will download a customized version of System Rescue CD with ZFS already included. When booting, use the "alternate"-kernel. The ZFS-module won't work with the default kernel.

Name: sysresccd-3.8.1_zfs_0.6.2.iso   (510 MB)
Release Date: 2013-11-03
md5sum aa33ef61c5d85ad564372327940498c3


Download System Rescue CD with ZFS

Creating a bootable USB from ISO

After you download the iso, you can do the following steps to create a bootable USB:

Make a temporary directory
# mkdir /tmp/loop

Mount the iso
# mount -o ro,loop /root/sysresccd-3.7.1_zfs_0.6.2.iso /tmp/loop

Run the usb installer
# /tmp/loop/usb_inst.sh

That should be all you need to do to get your flash drive working.

When you are booting into system rescue cd, make sure you select the alternative 64 bit kernel. ZFS support was specifically added to the alternative 64 bit kernel rather than the standard 64 bit kernel.

Creating partitions

There are two ways to partition your disk: You can use your entire drive and let ZFS automatically partition it for you, or you can do it manually.

We will be showing you how to partition it manually because if you partition it manually you get to create your own layout, you get to have your own separate /boot partition (Which is nice since not every bootloader supports booting from ZFS pools), and you get to boot into RAID10, RAID5 (RAIDZ) pools and any other layouts due to you having a separate /boot partition.

gdisk (GPT Style)

A Fresh Start:

First lets make sure that the disk is completely wiped from any previous disk labels and partitions. We will also assume that /dev/sda is the target drive.

# gdisk /dev/sda

Command: x ↵
Expert command: z ↵
About to wipe out GPT on /dev/sda. Proceed?: y ↵
GPT data structures destroyed! You may now partition the disk using fdisk or other utilities.
Blank out MBR?: y ↵
Warning: This is a destructive operation. Make sure you really don't want anything on this disk.

Now that we have a clean drive, we will create the new layout.

Create Partition 1 (boot):

Command: n ↵
Partition Number: 
First sector: 
Last sector: +250M ↵
Hex Code: 

Create Partition 2 (BIOS Boot Partition):

Command: n ↵
Partition Number: 
First sector: 
Last sector: +32M ↵
Hex Code: EF02 ↵

Create Partition 3 (ZFS):

Command: n ↵
Partition Number: 
First sector: 
Last sector: 
Hex Code: bf00 ↵

Command: p ↵

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          514047   250.0 MiB   8300  Linux filesystem
   2          514048          579583   32.0 MiB    EF02  BIOS boot partition
   3          579584      1953525134   931.2 GiB   BF00  Solaris root

Command: w ↵


Format your boot volume

Format your separate /boot partition:

# mkfs.ext2 /dev/sda1

Encryption (Optional)

If you want encryption, then create your encrypted vault(s) now by doing the following:

# cryptsetup luksFormat /dev/sda3
# cryptsetup luksOpen /dev/sda3 vault_1

Create the zpool

We will first create the pool. The pool will be named `rpool` and the disk will be aligned to 4096 (using ashift=12)

# zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sda3
Important: If you are using encrypted root, change /dev/sda3 to /dev/mapper/vault_1.
Note: ashift=12 should be use if you have a newer, advanced format disk that has a sector size of 4096 bytes. If you have an older disk with 512 byte sectors, you should use ashift=9 or don't add the option for auto detection
Note: If you have a previous pool that you would like to import, you can do a: zpool import -f -R /mnt/funtoo <pool_name>

Create the zfs datasets

We will now create some datasets. For this installation, we will create a small but future proof amount of datasets. We will have a dataset for the OS (/), and your swap. We will also show you how to create some optional datasets: /home, /var, /usr/src, and /usr/portage.

Create some empty containers for organization purposes, and make the dataset that will hold /
# zfs create rpool/ROOT
# zfs create -o mountpoint=/ rpool/ROOT/funtoo

Optional, but recommended datasets: /home
# zfs create -o mountpoint=/home rpool/HOME

Optional, portage tree, distfiles, and binary packages:
# zfs create rpool/FUNTOO
# zfs create -o mountpoint=/usr/portage -o compression=off rpool/FUNTOO/portage
# zfs create -o mountpoint=/usr/portage/distfiles rpool/FUNTOO/portage/distfiles
# zfs create -o mountpoint=/usr/portage/packages rpool/FUNTOO/portage/packages

Optional datasets: /usr/src
# zfs create -o mountpoint=/usr/src rpool/FUNTOO/src

Create your swap zvol

Make your swap +1G greater than your RAM. An 8G machine would have 9G of SWAP (This is kinda big though). For machines with this much memory, You could just make it 2G if you don't have any problems.

# zfs create -o sync=always -o primarycache=metadata -o secondarycache=none -o volblocksize=4K -V 1G rpool/swap

Format your swap zvol

# mkswap -f /dev/zvol/rpool/swap
# swapon /dev/zvol/rpool/swap


Last minute checks and touches

Check to make sure everything appears fine. Your output may differ depending on the choices you made above:

# zpool status
  pool: rpool
 state: ONLINE
  scan: none requested
config:

        NAME        STATE     READ WRITE CKSUM
        rpool       ONLINE       0     0     0
          sda2      ONLINE       0     0     0

errors: No known data errors

# zfs list
rpool              3.10G  15.5G   136K  none
rpool/HOME          136K  15.5G   136K  /mnt/funtoo/home
rpool/ROOT          308K  15.5G   136K  none
rpool/ROOT/funtoo   172K  15.5G   172K  /mnt/funtoo
rpool/swap         3.09G  18.6G    76K  -

Now we will continue to install funtoo.

Installing Funtoo

Download and extract the Funtoo stage3 and continue installation as normal.

Then once you've extracted the stage3, chroot into your new funtoo environment:

Go into the directory that you will chroot into
# cd /mnt/funtoo

Mount your boot drive
# mount /dev/sda1 /mnt/funtoo/boot

Bind the kernel related directories
# mount -t proc none /mnt/funtoo/proc
# mount --rbind /dev /mnt/funtoo/dev
# mount --rbind /sys /mnt/funtoo/sys

Copy network settings
# cp /etc/resolv.conf /mnt/funtoo/etc/

chroot into your new funtoo environment
# env -i HOME=/root TERM=$TERM chroot /mnt/funtoo /bin/bash --login

Place your mountpoints into your /etc/mtab file
# cat /proc/mounts > /etc/mtab

Sync your tree
# emerge --sync

Add filesystems to /etc/fstab

Before we continue to compile and or install our kernel in the next step, we will edit the /etc/fstab file because if we decide to install our kernel through portage, portage will need to know where is your /boot so that it can place the files in there. We also need to update /etc/mtab so our system knows what is mounted

# nano /etc/fstab

# <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>
# Do not add the /boot line below if you are using whole-disk zfs
/dev/sda1               /boot           ext2            defaults        0 2
/dev/zvol/rpool/swap    none            swap            sw              0 0

Kernel Configuration

To speed up this step, you can install "bliss-kernel" since it's already properly configured for ZFS and a lot of other configurations. The kernel is also compiled and ready to go. To install 'bliss-kernel' type the following:

# emerge bliss-kernel

Now make sure that your /usr/src/linux symlink is pointing to this kernel by typing the following:

# eselect kernel list
Available kernel symlink targets:
[1]   linux-3.10.10-FB.01 *

You should see a star next to the bliss-kernel version you installed. In this case it was 3.10.10-FB.01. If it's not set, you can type eselect kernel set #.

Installing the ZFS userspace tools

# emerge -av zfs

Check to make sure that the zfs tools are working, the zpool.cache file that you copied before should be displayed.

# zpool status
# zfs list

If everything worked, continue.

Install the bootloader

GRUB 2

Before you do this, make sure this checklist is followed:

  • Installed kernel and kernel modules
  • Installed zfs package from the tree
  • /dev, /proc, /sys are mounted in the chroot environment

Once all this is checked, let's install grub2. First we need to enable the "libzfs" use flag so zfs support is compiled for grub2.

# echo "sys-boot/grub libzfs" >> /etc/portage/package.use

Then we will compile grub2:

# emerge -av grub

Once this is done, you can check that grub is version 2.00 by doing the following command:

# grub-install --version
grub-install (GRUB) 2.00

Now try to install grub2:

# grub-install --no-floppy /dev/sda

You should receive the following message

Installation finished. No error reported.

If not, then go back to the above checklist.

LILO

Before you do this, make sure the following checklist is followed:

  • /dev/, /proc and /sys are mounted.
  • Installed the sys-fs/zfs package from the tree.

Once the above requirements are met, LILO can be installed.

Now we will install LILO.

# emerge -av sys-boot/lilo

Once the installation of LILO is complete we will need to edit the lilo.conf file.

# nano /etc/lilo.conf
boot=/dev/sda
prompt
timeout=4
default=Funtoo

image=/boot/bzImage
      label=Funtoo
      read-only
      append="root=rpool/ROOT/funtoo"
      initrd=/boot/initramfs

All that is left now is to install the bootcode to the MBR.

This can be accomplished by running:

# /sbin/lilo

If it is successful you should see:

Warning: LBA32 addressing assumed
Added Funtoo + *
One warning was issued

Create the initramfs

There are two ways to do this, you can use genkernel, or you can use my bliss initramfs creator. I will show you both.

genkernel

# emerge -av sys-kernel/genkernel
# You only need to add --luks if you used encryption
# genkernel --zfs --luks initramfs

Bliss Initramfs Creator

If you are encrypting your drives, then add the "luks" use flag to your package.use before emerging:

# echo "sys-kernel/bliss-initramfs luks" >> /etc/portage/package.use

Now install the creator:

# emerge bliss-initramfs


Then go into the install directory, run the script as root, and place it into /boot:

# cd /opt/bliss-initramfs
# ./createInit
# mv initrd-<kernel_name> /boot

<kernel_name> is the name of what you selected in the initramfs creator, and the name of the outputted file.

Using boot-update

/boot on separate partition

If you created a separate non-zfs partition for boot then configuring boot-update is almost exactly the same as a normal install except that auto detection for root does not work. You must tell boot-update what your root is.

Genkernel

If your using genkernel you must add 'real_root=ZFS=<root>' and 'dozfs' to your params. Example entry for boot.conf:

"Funtoo ZFS" {
        kernel vmlinuz[-v]
        initrd initramfs-genkernel-x86_64[-v]
        params real_root=ZFS=rpool/ROOT/funtoo
        params += dozfs
        # Also add 'params += crypt_root=/dev/sda2' if you used encryption
        # Adjust the above setting to your system if needed
}

Bliss Initramfs Creator

If you used the Bliss Initramfs Creator then all you need to do is add 'root=<root>' to your params. Example entry for boot.conf:

"Funtoo ZFS" {
        kernel vmlinuz[-v]
        initrd initrd[-v]
        params root=rpool/ROOT/funtoo quiet
        # If you have an encrypted device with a regular passphrase,
        # you can add the following line
        params += enc_root=/dev/sda3 enc_type=pass
}

After editing /etc/boot.conf, you just need to run boot-update to update grub.cfg

# boot-update

/boot on ZFS

TBC - pending update to boot-update to support this

Final configuration

Add the zfs tools to openrc

# rc-update add zfs boot

Clean up and reboot

We are almost done, we are just going to clean up, set our root password, and unmount whatever we mounted and get out.

Delete the stage3 tarball that you downloaded earlier so it doesn't take up space.
# cd /
# rm stage3-latest.tar.xz

Set your root password
# passwd
>> Enter your password, you won't see what you are writing (for security reasons), but it is there!

Get out of the chroot environment
# exit

Unmount all the kernel filesystem stuff and boot (if you have a separate /boot)
# umount -l proc dev sys boot

Turn off the swap
# swapoff /dev/zvol/rpool/swap

Export the zpool
# cd /
# zpool export rpool

Reboot
# reboot
Important: Don't forget to set your root password as stated above before exiting chroot and rebooting. If you don't set the root password, you won't be able to log into your new system.

and that should be enough to get your system to boot on ZFS.

After reboot

Create initial ZFS Snapshot

Continue to set up anything you need in terms of /etc configurations. Once you have everything the way you like it, take a snapshot of your system. You will be using this snapshot to revert back to this state if anything ever happens to your system down the road. The snapshots are cheap, and almost instant.

To take the snapshot of your system, type the following:

# zfs snapshot -r rpool@install

To see if your snapshot was taken, type:

# zfs list -t snapshot

If your machine ever fails and you need to get back to this state, just type (This will only revert your / dataset while keeping the rest of your data intact):

# zfs rollback rpool/ROOT/funtoo@install
Important: For a detailed overview, presentation of ZFS' capabilities, as well as usage examples, please refer to the ZFS Fun page.