|
|
| Line 1: |
Line 1: |
| == Introduction ==
| | Hey Jake, thanks for this excellent article! |
|
| |
|
| 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.
| | However I have found that your explanation about the naming convention "KDE SC 5" is not really correct. There is no "KDE Software Compilation" anymore. instead the devs split KDE 5 into three components: KDE Frameworks, KDE Plasma and KDE Applications. So now there's not one single name for it all... I wonder how they imagine to call their entire DE then; I guess it should be KDE Plasma 5. Kind of a turmoil if you ask me :/ |
|
| |
|
| === Introduction to ZFS ===
| | For further information you may read: |
|
| |
|
| 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:
| | https://wiki.archlinux.org/index.php/KDE (intro and first paragraph) |
|
| |
|
| * 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.
| | http://blog.jospoortvliet.com/2014/07/it-all-comes-together-no-more-software.html |
|
| |
|
| * 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.
| | http://en.wikipedia.org/wiki/KDE_Software_Compilation#Post-fourth_series |
|
| |
|
| * 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.
| | http://en.wikipedia.org/wiki/KDE_Frameworks_5#/media/File:Evolution_and_development_of_KDE_software.svg |
| | |
| * 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).
| |
| | |
| For a quick tour of ZFS and have a big picture of its common operations you can consult the page [[ZFS Fun]].
| |
| | |
| === Disclaimers ===
| |
| | |
| {{fancywarning|This guide is a work in progress. Expect some quirks. }}
| |
| | |
| {{fancynote|Some tests showed that the kernel build and grub installation is working when using somehow the basic line from: https://github.com/ryao/zfs-overlay/blob/master/zfs-install.
| |
| | |
| The guide will be changed accordingly in the next days...}}
| |
| | |
| {{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'''!}}
| |
| | |
| == Downloading the ISO (With ZFS) ==
| |
| In order for us to install Funtoo on ZFS, you will need an environment that already provides the ZFS tools. Therefore we will download a customized version of System Rescue CD with ZFS included.
| |
| | |
| <pre>
| |
| Name: sysresccd-4.2.0_zfs_0.6.2.iso (545 MB)
| |
| Release Date: 2014-02-25
| |
| md5sum 01f4e6929247d54db77ab7be4d156d85
| |
| </pre>
| |
| | |
| | |
| '''[http://ftp.osuosl.org/pub/funtoo/distfiles/sysresccd/ Download System Rescue CD with ZFS]'''<br />
| |
| | |
| == Creating a bootable USB from ISO (From a Linux Environment) ==
| |
| After you download the iso, you can do the following steps to create a bootable USB:
| |
| | |
| <console>
| |
| Make a temporary directory
| |
| # ##i##mkdir /tmp/loop
| |
| | |
| Mount the iso
| |
| # ##i##mount -o ro,loop /root/sysresccd-4.2.0_zfs_0.6.2.iso /tmp/loop
| |
| | |
| Run the usb installer
| |
| # ##i##/tmp/loop/usb_inst.sh
| |
| </console>
| |
| | |
| That should be all you need to do to get your flash drive working.
| |
| | |
| == Booting the ISO ==
| |
| | |
| {{fancywarning|'''When booting into the ISO, Make sure that you select the "Alternate 64 bit kernel (altker64)". The ZFS modules have been built specifically for this kernel rather than the standard kernel. If you select a different kernel, you will get a fail to load module stack error message.'''}}
| |
| | |
| == 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 <tt>/dev/sda</tt> is the target drive.<br />
| |
| | |
| <console>
| |
| # ##i##sgdisk -Z /dev/sda
| |
| </console>
| |
| | |
| {{fancywarning|This is a destructive operation and the program will not ask you for confirmation! Make sure you really don't want anything on this disk.}}
| |
| | |
| Now that we have a clean drive, we will create the new layout.
| |
| | |
| First open up the application:
| |
| | |
| <console>
| |
| # ##i##gdisk /dev/sda
| |
| </console>
| |
| | |
| '''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 partition ===
| |
| | |
| <console>
| |
| # ##i##mkfs.ext2 -m 1 /dev/sda1
| |
| </console>
| |
| | |
| === Create the zpool ===
| |
| We will first create the pool. The pool will be named <code>tank</code>. Feel free to name your pool as you want. We will use <code>ashift=12</code> option which is used for a hard drives with a 4096 sector size.
| |
| <console># ##i## zpool create -f -o ashift=12 -o cachefile=/tmp/zpool.cache -O normalization=formD -m none -R /mnt/funtoo tank /dev/sda3 </console>
| |
| | |
| === 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 as examples ones: <code>/home</code>, <code>/usr/src</code>, and <code>/usr/portage</code>.
| |
| | |
| <console>
| |
| Create some empty containers for organization purposes, and make the dataset that will hold /
| |
| # ##i##zfs create -p tank/funtoo
| |
| # ##i##zfs create -o mountpoint=/ tank/funtoo/root
| |
| | |
| Optional, but recommended datasets: /home
| |
| # ##i##zfs create -o mountpoint=/home tank/funtoo/home
| |
| | |
| Optional datasets: /usr/src, /usr/portage/{distfiles,packages}
| |
| # ##i##zfs create -o mountpoint=/usr/src tank/funtoo/src
| |
| # ##i##zfs create -o mountpoint=/usr/portage -o compression=off tank/funtoo/portage
| |
| # ##i##zfs create -o mountpoint=/usr/portage/distfiles tank/funtoo/portage/distfiles
| |
| # ##i##zfs create -o mountpoint=/usr/portage/packages tank/funtoo/portage/packages
| |
| </console>
| |
| | |
| == Installing Funtoo ==
| |
| | |
| === Pre-Chroot ===
| |
| | |
| <console>
| |
| Go into the directory that you will chroot into
| |
| # ##i##cd /mnt/funtoo
| |
| | |
| Make a boot folder and mount your boot drive
| |
| # ##i##mkdir boot
| |
| # ##i##mount /dev/sda1 boot
| |
| </console>
| |
| | |
| [[Funtoo_Linux_Installation|Now download and extract the Funtoo stage3 ...]]
| |
| | |
| | |
| {{fancynote|It is trully recommended to use the current version and generic64. That reduces the risk of a broken build.
| |
| | |
| After successfull ZFS installation and successfull first boot, the kernel may be changed using the <code> eselect profile set ... </code> command. If you create a snapshot before, you may allways come back to your previous installation, with some simple steps ... (rollback your pool and in the worst case configure and install the bootloader again)}}
| |
| | |
| | |
| | |
| Once you've extracted the stage3, do a few more preparations and chroot into your new funtoo environment:
| |
| | |
| <console>
| |
| Bind the kernel related directories
| |
| # ##i##mount -t proc none proc
| |
| # ##i##mount --rbind /dev dev
| |
| # ##i##mount --rbind /sys sys
| |
| | |
| Copy network settings
| |
| # ##i##cp -f /etc/resolv.conf etc
| |
| | |
| Make the zfs folder in 'etc' and copy your zpool.cache
| |
| # ##i##mkdir etc/zfs
| |
| # ##i##cp /tmp/zpool.cache etc/zfs
| |
| | |
| Chroot into Funtoo
| |
| # ##i##env -i HOME=/root TERM=$TERM chroot . bash -l
| |
| </console>
| |
| | |
| {{fancynote|How to create zpool.cache file?}}
| |
| If no <code>zpool.cache</code> file is available, the following command will create one:
| |
| <console>
| |
| # ##i##zpool set cachefile=/etc/zfs/zpool.cache tank | |
| </console>
| |
| | |
| {{:Install/PortageTree}}
| |
| | |
| === Add filesystems to /etc/fstab ===
| |
| | |
| Before we continue to compile and or install our kernel in the next step, we will edit the <code>/etc/fstab</code> file because if we decide to install our kernel through portage, portage will need to know where our <code>/boot</code> is, so that it can place the files in there.
| |
| | |
| Edit <code>/etc/fstab</code>:
| |
| | |
| {{file|name=/etc/fstab|desc= |body=
| |
| # <fs> <mountpoint> <type> <opts> <dump/pass>
| |
| | |
| /dev/sda1 /boot ext2 defaults 0 2
| |
| }}
| |
| | |
| == Building kernel, initramfs and grub to work with zfs==
| |
| === Initial kernel build before emerging zfs ===
| |
| Install genkernel using:
| |
| <console>
| |
| # ##i##emerge genkernel
| |
| | |
| Build initial kernel (required for checks in sys-kernel/spl and sys-fs/zfs):
| |
| # ##i##genkernel kernel --no-clean --no-mount-boot
| |
| | |
| </console>
| |
| | |
| === Installing the ZFS userspace tools and kernel modules ===
| |
| Emerge {{Package|sys-fs/zfs}}. This package will bring in {{Package|sys-kernel/spl}}, and {{Package|sys-fs/zfs-kmod}} as its dependencies:
| |
| | |
| <console>
| |
| # ##i##emerge zfs
| |
| </console>
| |
| | |
| Check to make sure that the zfs tools are working. The <code>zpool.cache</code> file that you copied before should be displayed.
| |
| | |
| <console>
| |
| # ##i##zpool status
| |
| # ##i##zfs list
| |
| </console>
| |
| | |
| If everything worked, continue.
| |
| | |
| === Add the zfs tools to openrc ===
| |
| <console># ##i##rc-update add zfs boot</console>
| |
| | |
| == Create kernel and initramfs ==
| |
| === Emerge genkernel and initial kernel build ===
| |
| Install genkernel using:
| |
| <console>
| |
| # ##i##emerge genkernel
| |
| | |
| Build initial kernel (required for checks in sys-kernel/spl and sys-fs/zfs):
| |
| # ##i##genkernel kernel --no-clean --no-mount-boot
| |
| | |
| </console>
| |
| | |
| == Installing & Configuring the Bootloader ==
| |
| | |
| === boot-update ===
| |
| boot-update comes as a dependency of grub2, so if you already installed grub, it's already on your system!
| |
| | |
| ==== Genkernel ====
| |
| If your using genkernel you must add 'real_root=ZFS=<root>' and 'dozfs' to your params.
| |
| Example entry for <code>/etc/boot.conf</code>:
| |
| | |
| {{file|name=/etc/boot.conf|desc= |body=
| |
| "Funtoo ZFS" {
| |
| kernel kernel[-v]
| |
| initrd initramfs-genkernel-x86_64[-v]
| |
| params real_root=ZFS=tank/funtoo/root
| |
| params += dozfs=force
| |
| }
| |
| }}
| |
| | |
| After editing /etc/boot.conf, you just need to run boot-update to update grub.cfg
| |
| | |
| <console>
| |
| ###i## boot-update
| |
| </console>
| |
| | |
| | |
| {{fancynote|If <code>boou-update</code>fails, try this:}}
| |
| <console>
| |
| # ##i##grub-mkconfig -o /boot/grub/grub.cfg
| |
| </console>
| |
| | |
| == Final configuration ==
| |
| === 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/tank/swap
| |
| | |
| Export the zpool
| |
| # ##i##cd /
| |
| # ##i##zpool export tank
| |
| | |
| 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 ==
| |
| | |
| === Forgot to reset password? ===
| |
| ==== System Rescue CD ====
| |
| If you aren't using bliss-initramfs, then you can reboot back into your sysresccd and reset through there by mounting your drive, chrooting, and then typing passwd.
| |
| | |
| Example:
| |
| <console>
| |
| # ##i##zpool import -f -R /mnt/funtoo tank
| |
| # ##i##chroot /mnt/funtoo bash -l
| |
| # ##i##passwd
| |
| # ##i##exit
| |
| # ##i##zpool export -f tank
| |
| # ##i##reboot
| |
| </console>
| |
| | |
| === 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 tank@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 tank/funtoo/root@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.'''}}
| |
| | |
| == Troubleshooting ==
| |
| | |
| === Starting from scratch ===
| |
| If your installation has gotten screwed up for whatever reason and you need a fresh restart, you can do the following from sysresccd to start fresh:
| |
| | |
| <console>
| |
| Destroy the pool and any snapshots and datasets it has
| |
| # ##i##zpool destroy -R -f tank
| |
| | |
| This deletes the files from /dev/sda1 so that even after we zap, recreating the drive in the exact sector
| |
| position and size will not give us access to the old files in this partition.
| |
| # ##i##mkfs.ext2 /dev/sda1
| |
| # ##i##sgdisk -Z /dev/sda
| |
| </console>
| |
| | |
| Now start the guide again :).
| |
| | |
| | |
| === Starting again reusing the same disk partitions and the same pool ===
| |
| | |
| If your installation has gotten screwed up for whatever reason and you want to keep your pole named tank than you should boou into the Rescue CD / USB as done before.
| |
| | |
| <console>import the pool reusing all existing datasets:
| |
| # ##i##zpool import -f -R /mnt/funtoo tank
| |
| </console>
| |
| | |
| Now you should wipe the previous installation off:
| |
| | |
| <console>
| |
| let's go to our base installation directory:
| |
| # ##i##cd /mnt/funtoo
| |
| | |
| and delete the old installation:
| |
| # ##i##rm -rf *
| |
| </console>
| |
| | |
| Now start the guide again, at "Pre-Chroot"
| |
| | |
| | |
| [[Category:HOWTO]]
| |
| [[Category:Filesystems]]
| |
| [[Category:Featured]]
| |
| [[Category:Install]]
| |
| | |
| __NOTITLE__
| |
