Difference between pages "Pt-br/Funtoo 1.0 Profile" and "ZFS Install Guide"

(Difference between pages)
(Utilizando eselect)
 
(Install genkernel and initial kernel build)
 
Line 1: Line 1:
== O que é um profile? ==
+
== Introduction ==
  
No Gentoo e no Funtoo Linux, profiles são utilizado para definir as configurações do sistema base (base system settings), e historicamente tem um monte de potenciais inexplorados. No Funtoo Linux, eu quis tirar vantagem de alguns desses potenciais para permitir aos usuários de Funtoo Linux facilmente planejar seu sistema para vários tipos de funções. entre o novo  Funtoo profile system.
+
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.
  
== O Que É ==
+
=== Introduction to ZFS ===
  
Historicamente, usuários tem que adicionar uma tonelada de configurações ao <code>/etc/[[make.conf]]</code> para customizar seu sistema Gentoo ou Funtoo Linux, que torna a instalação do sistema operacional mais difícil do que deveria ser.
+
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:
  
No Gentoo Linux, é possível definir somente um ''system profile''. Pense em um system profile como configurações padrão que o Portage utiliza para a construção de tudo no seu sistema.
+
* 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.
  
No Funtoo Linux, múltiplos profiles podem ser habilitados ao mesmo tempo. Esses incluem:
+
* 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.
  
* '''arch''' - um perfil de arquitetura (arch profile) é habilitdo, na hora da construção, e não é alterado. Isso define configurações específicas de arquitetura do CPU.
+
* 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.
* '''build''' - um perfil de construção (build profile) é habilitado, na hora da construção, e geralmente não é alterado. ele define o tipo de construção, tal como 'current' ou 'stable', e configurações associadas.
+
* '''flavor''' - um sabor (flavor) é habilitado por sistema, e pode ser alterado pelo usuário. Isso define o uso geral do sistema, tal como 'minimal', 'core', 'workstation' ou 'desktop'
+
* '''mix-in''' - zero ou mais mix-ins podem ser habilitados que habilitam configurações específicas para uma subset particular de recursos, tal como 'gnome', 'kde', 'media', 'mate', 'X', 'hardened'
+
  
{{note|1=
+
* ZFS has the ZFS Intent Log and SLOG devices, which accelerates small synchronous write performance.
Veja  [[Flavors and Mix-ins]] para uma lista completa de todos os sabores e mix-ins disponíveis no Funtoo Linux, juntamente com descrições de o que cada um faz.}}
+
  
=== Origens e Benefícios ===
+
* 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.
  
Esse novo sistema é realmente uma realização do original design do cascading profile que foi desenvolvido por Daniel Robbins e implementado por Seemant Kulleen como poarte do Portage. Funtoo Profiles desenvolvido para alavancar o cascading profile system existente e prover algo muito mais utilizável e sustentável para usuários e desenvolvedores também. Aqui estão alguns de seus benefícios:
+
* 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.
  
* Mais algumas configurações em <code>/etc/make.conf</code>. <code>CHOST</code> e <code>ARCH</code> não mais configure em <code>/etc/make.conf</code>.
+
* ZFS send/receive implementation supports incremental update when doing backups. btrfs' send/receive implementation requires sending the entire snapshot.
* Separação de interesse -- configurações de arch, build, e flavor-related são organizadas juntas.
+
* Flexibilidade do usuário - qualquer número de mix-ins podem ser habilitados para beliscar configurações masks ou USE como necessitado.
+
  
{{note|Veja [[Custom Profiles]] para informações em como estender o profile system.}}
+
* ZFS supports data deduplication, which is a memory hog and only works well for specialized workloads. btrfs has no equivalent.
  
== Migrando para o Funtoo 1.0 Profile ==
+
* ZFS datasets have a hierarchical namespace while btrfs subvolumes have a flat namespace.
  
=== Utilizando eselect ===
+
* 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.
O método preferido de adicionar e remover profiles é utilizar o [[eselect|eselect profile]]. Isso assegurará de que os profiles são adicionados corretamente e na ordem aadequada. A ordem é imperativa para as coisas funcionarem direito.
+
 
 +
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.  
 +
 
 +
Today is 2015-05-12. ZFS has undertaken an upgrade - from 0.6.3 to 0.6.4. Please ensure that you use a RescueCD with ZFS 0.6.3. At present date grub 2.02 is not able to deal with those new ZFS parameters. If you want to use ZFS 0.6.4 for pool creation, you should use the compatability mode.
 +
 
 +
You should upgrade an existing pool only when grub is able to deal with - in a future version ... If not, you will not be able to boot into your system, and no rollback will help!
 +
 
 +
Please inform yourself!}}
 +
 
 +
{{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:
  
Digite o seguinte para visualizar uma lista de opções disponíveis para '''eselect profile''':
 
 
<console>
 
<console>
###i## eselect profile help
+
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>
 
</console>
  
Para um inicio, vamos ver o que a configuração padrão tem a oferecer. Obtenha uma vsão geral utilizando o comando '''list''':
+
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>
 
<console>
###i## eselect profile list
+
# ##i##sgdisk -Z /dev/sda
##b####g##Currently available arch profiles:
+
  ##b##[1]  funtoo/1.0/linux-gnu/arch/x86-64bit##!b## *
+
  ##b##[2]##!b##  funtoo/1.0/linux-gnu/arch/pure64
+
##b####g##Currently available build profiles:
+
  ##b##[3]##!b##  funtoo/1.0/linux-gnu/build/stable
+
  ##b##[4]  funtoo/1.0/linux-gnu/build/current##!b## *
+
  ##b##[5]##!b##  funtoo/1.0/linux-gnu/build/experimental
+
##b####g##Currently available flavor profiles:
+
  ##b##[6]##!b##  funtoo/1.0/linux-gnu/flavor/minimal
+
  ##b##[7]  funtoo/1.0/linux-gnu/flavor/core##!b## *
+
  ##b##[8]##!b##  funtoo/1.0/linux-gnu/flavor/desktop
+
  ##b##[9]##!b##  funtoo/1.0/linux-gnu/flavor/workstation
+
  ##b##[10]##!b##  funtoo/1.0/linux-gnu/flavor/hardened
+
##b####g##Currently available mix-ins profiles:
+
  ##b##[11]##!b##  funtoo/1.0/linux-gnu/mix-ins/audio
+
  ##b##[12]##!b##  funtoo/1.0/linux-gnu/mix-ins/cinnamon
+
  ##b##[13]##!b##  funtoo/1.0/linux-gnu/mix-ins/console-extras
+
  ##b##[14]##!b##  funtoo/1.0/linux-gnu/mix-ins/dvd
+
  ##b##[15]##!b##  funtoo/1.0/linux-gnu/mix-ins/gnome
+
  ##b##[16]##!b##  funtoo/1.0/linux-gnu/mix-ins/kde
+
  ##b##[17]##!b##  funtoo/1.0/linux-gnu/mix-ins/mate
+
  ##b##[18]##!b##  funtoo/1.0/linux-gnu/mix-ins/media
+
  ##b##[19]##!b##  funtoo/1.0/linux-gnu/mix-ins/print
+
  ##b##[20]##!b##  funtoo/1.0/linux-gnu/mix-ins/python3-only
+
  ##b##[21]##!b##  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
+
  ##b##[22]##!b##  funtoo/1.0/linux-gnu/mix-ins/server-db
+
  ##b##[23]##!b##  funtoo/1.0/linux-gnu/mix-ins/server-mail
+
  ##b##[24]##!b##  funtoo/1.0/linux-gnu/mix-ins/server-web
+
  ##b##[25]##!b##  funtoo/1.0/linux-gnu/mix-ins/X
+
  ##b##[26]##!b##  funtoo/1.0/linux-gnu/mix-ins/xfce
+
  ##b##[27]##!b##  funtoo/1.0/linux-gnu/mix-ins/vmware-guest
+
  ##b##[28]##!b##  funtoo/1.0/linux-gnu/mix-ins/hardened
+
 
</console>
 
</console>
  
Como e várias outras utilidades do Funtoo, uma estrela ('''*''') à direita indica um item ativo (seu caso pode diferenciar do exemplo acima).
+
{{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.}}
Em muitos casos você vai querer definir seu "flavor" primeiro. Lembre-se de que você pode somente definir ''um'' flavor de cada vez.
+
  
Para escolher seu flavor favorito utilize o comando '''set-flavor''' incluindo sua seleção. Nesse exemplo, definiremos o flavor '''desktop''':
+
Now that we have a clean drive, we will create the new layout.
{{note|Você ''deve'' utilizar números para referenciar os profiles que você quiser.}}
+
 
<console>###i## eselect profile set-flavor 8</console>
+
First open up the application:
Visualize o resultado:
+
 
<console>###i## eselect profile list
+
<console>
##b####g##Currently available arch profiles:
+
# ##i##gdisk /dev/sda
  ##b##[1]  funtoo/1.0/linux-gnu/arch/x86-64bit##!b## *
+
  ##b##[2]##!b##  funtoo/1.0/linux-gnu/arch/pure64
+
##b####g##Currently available build profiles:
+
  ##b##[3]##!b##  funtoo/1.0/linux-gnu/build/stable
+
  ##b##[4]  funtoo/1.0/linux-gnu/build/current##!b## *
+
  ##b##[5]##!b##  funtoo/1.0/linux-gnu/build/experimental
+
##b####g##Currently available flavor profiles:
+
  ##b##[6]##!b##  funtoo/1.0/linux-gnu/flavor/minimal
+
  ##b##[7]##!b##  funtoo/1.0/linux-gnu/flavor/core
+
  ##b##[8]  funtoo/1.0/linux-gnu/flavor/desktop##!b## *
+
  ##b##[9]##!b##  funtoo/1.0/linux-gnu/flavor/workstation
+
  ##b##[10]##!b##  funtoo/1.0/linux-gnu/flavor/hardened
+
##b####g##Currently available mix-ins profiles:
+
  ##b##[11]  funtoo/1.0/linux-gnu/mix-ins/audio (auto)
+
  ##b##[12]##!b##  funtoo/1.0/linux-gnu/mix-ins/cinnamon
+
  ##b##[13]  funtoo/1.0/linux-gnu/mix-ins/console-extras (auto)
+
  ##b##[14]  funtoo/1.0/linux-gnu/mix-ins/dvd (auto)
+
  ##b##[15]##!b##  funtoo/1.0/linux-gnu/mix-ins/gnome
+
  ##b##[16]##!b##  funtoo/1.0/linux-gnu/mix-ins/kde
+
  ##b##[17]##!b##  funtoo/1.0/linux-gnu/mix-ins/mate
+
  ##b##[18]  funtoo/1.0/linux-gnu/mix-ins/media (auto)
+
  ##b##[19]  funtoo/1.0/linux-gnu/mix-ins/print (auto)
+
  ##b##[20]##!b##  funtoo/1.0/linux-gnu/mix-ins/python3-only
+
  ##b##[21]##!b##  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
+
  ##b##[22]##!b##  funtoo/1.0/linux-gnu/mix-ins/server-db
+
  ##b##[23]##!b##  funtoo/1.0/linux-gnu/mix-ins/server-mail
+
  ##b##[24]##!b##  funtoo/1.0/linux-gnu/mix-ins/server-web
+
  ##b##[25]  funtoo/1.0/linux-gnu/mix-ins/X (auto)
+
  ##b##[26]##!b##  funtoo/1.0/linux-gnu/mix-ins/xfce
+
  ##b##[27]##!b##  funtoo/1.0/linux-gnu/mix-ins/vmware-guest
+
  ##b##[28]##!b##  funtoo/1.0/linux-gnu/mix-ins/hardened
+
 
</console>
 
</console>
Como você vê nas entradas '''(auto)''', o flavor '''desktop''' já pré-definiu alguns mix-ins para você.
 
  
Agora, vamos em frente e adicionar alguns mix-ins. Para adicionar, digamos, os mix-ins '''gnome''' e '''kde''' teríamos que entrar:
+
'''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>
 
<console>
###i## eselect profile add 15
+
# ##i##mkfs.ext2 -m 1 /dev/sda1
###i## eselect profile add 16
+
 
</console>
 
</console>
  
Ou, em um one-shot:
+
=== 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>
 
<console>
###i## eselect profile add 15 16
+
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>
 
</console>
  
Se quisermos remover um  mix-in, por exemplo '''gnome''', simplesmente entre:
+
== Installing Funtoo ==
 +
 
 +
=== Pre-Chroot ===
  
 
<console>
 
<console>
###i## eselect profile remove 15
+
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>
 
</console>
  
Verificação:
+
[[Funtoo_Linux_Installation|Now download and extract the Funtoo stage3 ...]]
  
<console>###i## eselect profile list
+
 
##b####g##Currently available arch profiles:
+
{{fancynote|It is trully recommended to use the current version and generic64. That reduces the risk of a broken build.
  ##b##[1]  funtoo/1.0/linux-gnu/arch/x86-64bit##!b## *
+
 
  ##b##[2]##!b##  funtoo/1.0/linux-gnu/arch/pure64
+
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)}}
##b####g##Currently available build profiles:
+
 
  ##b##[3]##!b##  funtoo/1.0/linux-gnu/build/stable
+
 
  ##b##[4]  funtoo/1.0/linux-gnu/build/current##!b## *
+
 
  ##b##[5]##!b##  funtoo/1.0/linux-gnu/build/experimental
+
Once you've extracted the stage3, do a few more preparations and chroot into your new funtoo environment:
##b####g##Currently available flavor profiles:
+
 
  ##b##[6]##!b##  funtoo/1.0/linux-gnu/flavor/minimal
+
<console>
  ##b##[7]##!b##  funtoo/1.0/linux-gnu/flavor/core
+
Bind the kernel related directories
  ##b##[8]  funtoo/1.0/linux-gnu/flavor/desktop##!b## *
+
# ##i##mount -t proc none proc
  ##b##[9]##!b##  funtoo/1.0/linux-gnu/flavor/workstation
+
# ##i##mount --rbind /dev dev
  ##b##[10]##!b##  funtoo/1.0/linux-gnu/flavor/hardened
+
# ##i##mount --rbind /sys sys
##b####g##Currently available mix-ins profiles:
+
 
  ##b##[11]  funtoo/1.0/linux-gnu/mix-ins/audio (auto)
+
Copy network settings
  ##b##[12]##!b##  funtoo/1.0/linux-gnu/mix-ins/cinnamon
+
# ##i##cp -f /etc/resolv.conf etc
  ##b##[13]  funtoo/1.0/linux-gnu/mix-ins/console-extras (auto)
+
 
  ##b##[14]  funtoo/1.0/linux-gnu/mix-ins/dvd (auto)
+
Make the zfs folder in 'etc' and copy your zpool.cache
  ##b##[15]##!b##  funtoo/1.0/linux-gnu/mix-ins/gnome
+
# ##i##mkdir etc/zfs
  ##b##[16]  funtoo/1.0/linux-gnu/mix-ins/kde *
+
# ##i##cp /tmp/zpool.cache etc/zfs
  ##b##[17]##!b##  funtoo/1.0/linux-gnu/mix-ins/mate
+
 
  ##b##[18]  funtoo/1.0/linux-gnu/mix-ins/media (auto)
+
Chroot into Funtoo
  ##b##[19]  funtoo/1.0/linux-gnu/mix-ins/print (auto)
+
# ##i##env -i HOME=/root TERM=$TERM chroot . bash -l
  ##b##[20]##!b##  funtoo/1.0/linux-gnu/mix-ins/python3-only
+
  ##b##[21]##!b##  funtoo/1.0/linux-gnu/mix-ins/rhel5-compat
+
  ##b##[22]##!b##  funtoo/1.0/linux-gnu/mix-ins/server-db
+
  ##b##[23]##!b##  funtoo/1.0/linux-gnu/mix-ins/server-mail
+
  ##b##[24]##!b##  funtoo/1.0/linux-gnu/mix-ins/server-web
+
  ##b##[25]  funtoo/1.0/linux-gnu/mix-ins/X (auto)
+
  ##b##[26]##!b##  funtoo/1.0/linux-gnu/mix-ins/xfce
+
  ##b##[27]##!b##  funtoo/1.0/linux-gnu/mix-ins/vmware-guest
+
  ##b##[28]##!b##  funtoo/1.0/linux-gnu/mix-ins/hardened
+
 
</console>
 
</console>
  
Nenhuma mágica aqui, seja o que for que você adicionar é colocado dentro do arquivo <code>/etc/portage/make.profile/parent</code> pelo portage.
+
{{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>
  
No nosso caso, esse arquivo contem:
+
{{: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==
 +
=== Install genkernel and initial kernel build ===
 +
 
 +
We need to build a genkernel initially:
 
<console>
 
<console>
###i## cat /etc/portage/make.profile/parent
+
# ##i##emerge genkernel
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
+
 
gentoo:funtoo/1.0/linux-gnu/build/current
+
Build initial kernel (required for checks in sys-kernel/spl and sys-fs/zfs):
gentoo:funtoo/1.0/linux-gnu/flavor/desktop
+
# ##i##genkernel kernel --no-clean --no-mountboot
gentoo:funtoo/1.0/linux-gnu/mix-ins/kde
+
 
 
</console>
 
</console>
{{fancywarning|Please, do not add anything manually into <code>parent</code> file. This may result in profile breakage.}}
 
  
== For Developers ==
+
=== 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:
  
=== Define the profile sub-sets you will use ===
+
<console>
 +
# ##i##emerge zfs
 +
</console>
  
So far in Funtoo we have used the exact same profiles as Gentoo thus Funtoo/2008.0 was strictly the same thing as Gentoo/2008.0 or the barely the same 10.0. This (monolithic) profile was set though a symbolic link named <code>/etc/make.profile</code> pointing on a complex directory architecture located somewhere under <code>/usr/portage/profiles</code>. This is no longer valid with the Funtoo 1.0 profiles as they are split in several smaller bricks which are then glued together via the  <code>/etc/portage/make.profile/parent</code> file (You do not need to include everything, just use the "bricks" you need). Those bricks belongs to several categories:
+
Check to make sure that the zfs tools are working. The <code>zpool.cache</code> file that you copied before should be displayed.
  
# MANDATORY -- An "arch" profile which defines settings for a particular architecture. You'll want to set this to whatever arch your system is and leave it alone. '''Setting it to a different arch than your system could severely break it.'''
+
<console>
# MANDATORY -- A "build" profile which should match the tree you wish to use. '''Stable''', '''Current''' (~arch), or '''Experimental''' (use it if you are brave enough and find '''current''' too stable).
+
# ##i##zpool status
# MANDATORY -- A "flavor" profile (what was previously known as ''profiles'' is still known as such in Gentoo) which describes the kind of system you want:
+
# ##i##zfs list
#* minimal - Be warned, minimal is exactly what it says, the minimal profile stuff you need for a usable system, nothing else. This is really for people who know what they're doing.
+
</console>
#* core - This is the core profile. This is for stuff that affects both desktops and servers.
+
 
#* desktop - Exactly what it says. If you're using a desktop, you should set this as your flavor.
+
Add the zfs tools to openrc.
#* server - If you're running a server, you should set this as your flavor.
+
<console># ##i##rc-update add zfs boot</console>
# OPTIONAL -- One or more "mix-ins" profiles which describe optional add-ons. 'mix-ins' are the heart of the Funtoo 1.0 profiles. Unlike the monolithic profiles which sets a massive amount of use flags and options for you, we've split them into logical add-on profiles. For instance if you want support for gnome, you would add the gnome mix-in to your current profiles. That mix-in sets all the proper use flags and such for gnome. Same with others. Want dvd support? Add that one in. Using a rhel5 kernel which requires special versions of packages such as udev? There's a mix-in for that too. Run a mail server? web server? There's mix-ins for those also. Expect this category to grow in the future as new mix-ins are created.
+
 
 +
If everything worked, continue.
 +
 
 +
=== Install GRUB 2  ===
 +
 
 +
Install grub2:
 +
<console>
 +
# ##i##echo "sys-boot/grub libzfs -truetype" >> /etc/portage/package.use
 +
# ##i##emerge grub
 +
</console>
 +
 
 +
Now install grub to the drive itself (not a partition):
 +
<console>
 +
# ##i##grub-install /dev/sda
 +
</console>
 +
 
 +
=== Emerge genkernel and initial kernel build ===
 +
Install genkernel using:
 +
<console>
 +
# ##i##echo "sys-kernel/genkernel zfs" >> /etc/portage/package.use
 +
# ##i##emerge genkernel
 +
 
 +
Build now kernel and initramfs with --zfs
 +
# ##i##genkernel all --zfs --no-clean --no-mountboot --callback="emerge @module-rebuild"
 +
</console>
 +
 
 +
 
 +
{{fancynote|During the build, ZFS configurations should be observed.
 +
 
 +
If the build breaks, restart it again.}}
 +
 
 +
=== Configuring the Bootloader ===
  
The contents of <code>/etc/portage/make.profile/parent</code> for a basic setup might look like this:
+
Using the genkernel you must add 'real_root=ZFS=<root>' and 'dozfs' to your params.
 +
Edit the  entry for <code>/etc/boot.conf</code>:
  
{{file|name=/etc/portage/make.profile/parent|body=
+
{{file|name=/etc/boot.conf|desc= |body=
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
+
"Funtoo ZFS" {
gentoo:funtoo/1.0/linux-gnu/build/current
+
        kernel kernel[-v]
gentoo:funtoo/1.0/linux-gnu/flavor/core
+
        initrd initramfs-genkernel-x86_64[-v]
 +
        params real_root=ZFS=tank/funtoo/root
 +
        params += dozfs=force
 +
}
 
}}
 
}}
  
A more rounded setup for a desktop might look like this:
+
The command <code>boot-update</code> should take care of grub configuration:
  
{{file|name=/etc/portage/make.profile/parent|body=
+
<console>
gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit
+
Install boot-update (if it is missing):
gentoo:funtoo/1.0/linux-gnu/build/current
+
###i##emerge boot-update
gentoo:funtoo/1.0/linux-gnu/flavor/desktop
+
 
gentoo:funtoo/1.0/linux-gnu/mix-ins/dvd
+
Run boot-update to update grub.cfg
gentoo:funtoo/1.0/linux-gnu/mix-ins/media
+
###i##boot-update
 +
</console>
 +
 
 +
{{fancynote|If <code>boot-update</code>fails, try this:
 +
<console>
 +
# ##i##grub-mkconfig -o /boot/grub/grub.cfg
 +
</console>
 
}}
 
}}
 +
Now you should have a new installation of the kernel, initramfs and grub which are zfs capable. The configurtion files should be updated, and the system should come up during the next reboot.
 +
 +
{{fancynote|If The <code>luks</code> integration works basically the same way.}}
 +
 +
== 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"
  
== Related ==
 
* [[Flavors and Mix-ins]]
 
  
[[Category:Funtoo features]]
 
[[Category:Portage]]
 
[[Category:Labs]]
 
 
[[Category:HOWTO]]
 
[[Category:HOWTO]]
[[Category:Official Documentation]]
+
[[Category:Filesystems]]
 +
[[Category:Featured]]
 +
[[Category:Install]]
 +
 
 +
__NOTITLE__

Revision as of 15:57, May 13, 2015

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).

For a quick tour of ZFS and have a big picture of its common operations you can consult the page ZFS Fun.

Disclaimers

Warning

This guide is a work in progress. Expect some quirks.

Today is 2015-05-12. ZFS has undertaken an upgrade - from 0.6.3 to 0.6.4. Please ensure that you use a RescueCD with ZFS 0.6.3. At present date grub 2.02 is not able to deal with those new ZFS parameters. If you want to use ZFS 0.6.4 for pool creation, you should use the compatability mode.

You should upgrade an existing pool only when grub is able to deal with - in a future version ... If not, you will not be able to boot into your system, and no rollback will help!

Please inform yourself!

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!

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.

Name: sysresccd-4.2.0_zfs_0.6.2.iso  (545 MB)
Release Date: 2014-02-25
md5sum 01f4e6929247d54db77ab7be4d156d85


Download System Rescue CD with ZFS

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:

Make a temporary directory
# mkdir /tmp/loop

Mount the iso
# mount -o ro,loop /root/sysresccd-4.2.0_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.

Booting the ISO

Warning

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 /dev/sda is the target drive.

# sgdisk -Z /dev/sda
Warning

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:

# gdisk /dev/sda

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 partition

# mkfs.ext2 -m 1 /dev/sda1

Create the zpool

We will first create the pool. The pool will be named tank. Feel free to name your pool as you want. We will use ashift=12 option which is used for a hard drives with a 4096 sector size.

#   zpool create -f -o ashift=12 -o cachefile=/tmp/zpool.cache -O normalization=formD -m none -R /mnt/funtoo tank /dev/sda3 

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: /home, /usr/src, and /usr/portage.

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

Optional, but recommended datasets: /home
# zfs create -o mountpoint=/home tank/funtoo/home

Optional datasets: /usr/src, /usr/portage/{distfiles,packages}
# zfs create -o mountpoint=/usr/src tank/funtoo/src
# zfs create -o mountpoint=/usr/portage -o compression=off tank/funtoo/portage
# zfs create -o mountpoint=/usr/portage/distfiles tank/funtoo/portage/distfiles
# zfs create -o mountpoint=/usr/portage/packages tank/funtoo/portage/packages

Installing Funtoo

Pre-Chroot

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

Make a boot folder and mount your boot drive
# mkdir boot
# mount /dev/sda1 boot

Now download and extract the Funtoo stage3 ...


Note

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 eselect profile set ... 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:

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

Copy network settings
# cp -f /etc/resolv.conf etc

Make the zfs folder in 'etc' and copy your zpool.cache
# mkdir etc/zfs
# cp /tmp/zpool.cache etc/zfs

Chroot into Funtoo
# env -i HOME=/root TERM=$TERM chroot . bash -l
Note

How to create zpool.cache file?

If no zpool.cache file is available, the following command will create one:

# zpool set cachefile=/etc/zfs/zpool.cache tank


Downloading the Portage tree

Note

For an alternative way to do this, see Installing Portage From Snapshot.

Now it's time to install a copy of the Portage repository, which contains package scripts (ebuilds) that tell portage how to build and install thousands of different software packages. To create the Portage repository, simply run emerge --sync from within the chroot. This will automatically clone the portage tree from GitHub:

(chroot) # emerge --sync
Important

If you receive the error with initial emerge --sync due to git protocol restrictions, change SYNC variable in /etc/portage/make.conf:

SYNC="https://github.com/funtoo/ports-2012.git"
Note

To update the Funtoo Linux system just type:

(chroot) # emerge -auDN @world


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 our /boot is, so that it can place the files in there.

Edit /etc/fstab:

/etc/fstab
# <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>

/dev/sda1               /boot           ext2            defaults        0 2

Building kernel, initramfs and grub to work with zfs

Install genkernel and initial kernel build

We need to build a genkernel initially:

# emerge genkernel

Build initial kernel (required for checks in sys-kernel/spl and sys-fs/zfs):
# genkernel kernel --no-clean --no-mountboot 

Installing the ZFS userspace tools and kernel modules

Emerge No results. This package will bring in No results, and No results as its dependencies:

# emerge 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

Add the zfs tools to openrc.

# rc-update add zfs boot

If everything worked, continue.

Install GRUB 2

Install grub2:

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

Now install grub to the drive itself (not a partition):

# grub-install /dev/sda

Emerge genkernel and initial kernel build

Install genkernel using:

# echo "sys-kernel/genkernel zfs" >> /etc/portage/package.use
# emerge genkernel

Build now kernel and initramfs with --zfs
# genkernel all --zfs --no-clean --no-mountboot --callback="emerge @module-rebuild"


Note

During the build, ZFS configurations should be observed.

If the build breaks, restart it again.

Configuring the Bootloader

Using the genkernel you must add 'real_root=ZFS=<root>' and 'dozfs' to your params. Edit the entry for /etc/boot.conf:

/etc/boot.conf
"Funtoo ZFS" {
        kernel kernel[-v]
        initrd initramfs-genkernel-x86_64[-v]
        params real_root=ZFS=tank/funtoo/root
        params += dozfs=force
}

The command boot-update should take care of grub configuration:

Install boot-update (if it is missing):
#emerge boot-update

Run boot-update to update grub.cfg
#boot-update
Note

If boot-updatefails, try this:

# grub-mkconfig -o /boot/grub/grub.cfg

Now you should have a new installation of the kernel, initramfs and grub which are zfs capable. The configurtion files should be updated, and the system should come up during the next reboot.

Note

If The luks integration works basically the same way.

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.

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/tank/swap

Export the zpool
# cd /
# zpool export tank

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

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:

# zpool import -f -R /mnt/funtoo tank
# chroot /mnt/funtoo bash -l
# passwd
# exit
# zpool export -f tank
# 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 tank@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 tank/funtoo/root@install
Important

For a detailed overview, presentation of ZFS' capabilities, as well as usage examples, please refer to the 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:

Destroy the pool and any snapshots and datasets it has
# 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.
# mkfs.ext2 /dev/sda1
# sgdisk -Z /dev/sda

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.

import the pool reusing all existing datasets:
# zpool import -f -R /mnt/funtoo tank

Now you should wipe the previous installation off:

let's go to our base installation directory:
# cd /mnt/funtoo

and delete the old installation: 
# rm -rf *

Now start the guide again, at "Pre-Chroot"