Export translations

Settings

Group

Language

Format

Export for off-line translation

Export in native format

<div lang="en" dir="ltr" class="mw-content-ltr">
ZFS is an advanced filesystem that is available for use in Funtoo Linux, thanks to the ZFS on Linux project.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It is easy to set up and use ZFS. In this simple introduction, we're going to set up ZFS under Funtoo Linux using an existing {{c|debian-sources}} or {{c|debian-sources-lts}} kernel like the one that comes pre-built for you with Funtoo Linux, and we will also be using our ZFS storage pool for storing data that isn't part of the Funtoo Linux installation itself. This means that we don't need to worry about enabling ZFS support in GRUB, or mounting ZFS to actually boot Funtoo Linux. Funtoo Linux will boot from a non-ZFS filesystem, and as part of the initialization process will initialize our ZFS storage pool and mount it at the location of our choice.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Installation ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To install ZFS, perform the following steps:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{console|body=
# ##i##emerge zfs
}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This will emerge the ZFS userspace tools ({{c|zfs}}) as well as ZFS kernel modules ({{c|zfs-kmod}} and {{c|spl}}). Once complete, enable ZFS in your default runlevel as follows:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{console|body=
# ##i##rc-update add zfs-import default
# ##i##rc
}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
ZFS is now initialized and ready for use.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== ZFS Concepts ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Unlike traditional filesystems like ext4 and xfs, ZFS is an all-inclusive storage technology that manages its own filesystems without using {{f|/etc/fstab}}. The ZFS concept of ''importing'' volumes and their associated filesystems makes them available for use by the operating system. This will be performed when the system boots via the {{c|zfs-import}} startup script.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
ZFS also generally manages the physical disks that it uses, and physical disks are added to a ZFS storage pool. Then, ZFS can create volumes from the storage pool on which
files can be stored.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Unlike traditional Linux filesystems, ZFS filesystems will allocate storage on-demand from the underlying storage pool. Thus, we can set the "size" of a ZFS volume, but this space only actually allocated when files are stored on the filesystem. In contrast, traditional Linux filesystems like ext4 and xfs must be assigned underlying block storage in advance.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
In ZFS terminology, a ZFS ''storage pool'' can hold the following things, all of which are considered to be ''datasets'':
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* ''filesystems'' - these are what get mounted and you store files in. Generally, this is the main thing people use ZFS for.
* ''clones'' - a filesystem that is created as a copy of an existing ''snapshot''.
* ''snapshots'' - a read-only copy of a filesystem at a given point in time.
* ''volume'' - a dataset that acts as a block device, such as a swap device.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When you inspect the contents of a ZFS storage pool, you will see potentially all these different types of things listed as the contents of the pool, and their names will appear in a {{c|pool/path[@snapshot]}} format. ''Pool'' is the name of the storage pool. ''Path'' is a slash-delimited path name for the component, and the slashes don't represent directories but a logical organizational hierarchy for the dataset in the pool.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Creating a Storage Pool ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To create a basic ZFS storage pool, you will need an extra empty disk. Perform the following steps:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{console|body=
# ##i##zpool create mypool /dev/sdxy
}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{c|/dev/sdxy}} should be an unused disk. You may need to use the following command if this disk contains any pre-existing data on it:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{console|body=
# ##i##zpool create -f mypool /dev/sdxy
}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Once your storage pool is created, you can verify its existence with the {{c|zpool status}} command:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{console|body=
# ##i##zpool status
  pool: mypool
 state: ONLINE
  scan: none requested
config:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
NAME        STATE     READ WRITE CKSUM
	mypool      ONLINE       0     0     0
	  sdb       ONLINE       0     0     0
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
errors: No known data errors
#
}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
And if you type {{c|zfs list}}, you will likely see something like this:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{console|body=
# ##i### zfs list
NAME                                                                          USED  AVAIL  REFER  MOUNTPOINT
mypool                                                                       2.19G   459G    96K  none
}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Notice the ''mountpoint'' entry of {{c|None}}. While it is possible to mount your storage pool directly and use it as a filesystem, it is best to create a filesystem as a sub-path within your pool's namespace, as follows:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{console|body=
# ##i##zfs create mypool/home
# ##i##zfs list
NAME                                                                          USED  AVAIL  REFER  MOUNTPOINT
mypool                                                                       2.19G   459G    96K  none
mypool/home                                                                    96K   459G    96K  none
}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As you can see above, although we have created a ZFS filesystem, it is only using 96K of storage on our pool, although there are 459GB available. You can also see that the filesystem is currently not mounted. Rather than use the {{c|mount}} command, let's change that the ZFS way:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{console|body=
# ##i##mkdir /data/home
# ##i##zfs set mountpoint=/data/home mypool/home
# ##i##mount
...
mypool/home on /data/home type zfs (rw,xattr,posixacl)
}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
We have now set the {{c|mountpoint}} property on our filesystem, and can see that it is now mounted where we want it. ZFS will remember that our {{c|mypool/home}} filesystem gets mounted at {{f|/data/home}}. Most people will want their filesystems to be automatically mounted at boot and will perform the following steps to make this happen:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{console|body=
# ##i##rc-update add zfs-mount default
}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You should now be at the point where you can begin to use ZFS for a variety of tasks. While there is a lot more to ZFS than what is covered in this short introduction, you should now have a good understanding of the fundamental concepts on which ZFS is based.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[[Category:ZFS]]
[[Category:Filesystems]]
[[Category:HOWTO]]
[[Category:Official Documentation]]
</div>

Export translations

Navigation menu

Search