Contents
Can a ZFS pool be created with a single disk?
Dynamic strip – Its a very basic pool which can be created with a single disk or a concatenation of disk. We have already seen zpool creation using a single disk in the example of creating zpool with disks. Lets see how we can create concatenated zfs pool.
Is it possible to shrink a ZFS root pool?
Since shrinking a pool is not supported by ZFS directly, the procedure is a little more elaborate. This assumes that your running a ZFS root pool named oldpool using a “classic” disk layout, e.g.: And a simple pool layout, e.g.: It also assumes that you’re replacing one disk with another (HDD to SSD in this case).
Is it safe to destroy a ZF pool?
However, be cautious when performing these operations. Although checks are performed to prevent using devices known to be in use in a new pool, ZFS cannot always know when a device is already in use. Destroying a pool is easier than creating one. Use zpool destroy with caution.
How to create a ZFS volume in FreeNAS?
Creating a FreeNAS ZFS volume Once you’ve got your partitions set up, you can create a ZFS pool (volume). There’s one fly in the ointment: by default, FreeBSD mounts ZFS pools at the root of the filesystem, but FreeNAS mounts them under /mnt. So, you need to tell ZFS where the mount point is using the -m flag to zpool:
Is there a zpool that Grub can read?
This probelm is present in Grub installed from ArchLinux and also Fedora 28. Ubuntu, however, appears to have patched their Grub to fix this (confirmed with Ubuntu 16.10). Grub can, however, read the files required to boot. You can create a zpool that Grub will boot like this:
Is there a way to install Arch Linux on ZFS?
The Arch Linux wiki page about Installing Arch Linux on ZFS highlights certain bugs but doesn’t really explain how to overcome them. The linked pages explain that Grub supports a subset of zpool features and cannot read a pool that uses features that it doesn’t support.
Is there a way to read a grub pool?
The linked pages explain that Grub supports a subset of zpool features and cannot read a pool that uses features that it doesn’t support. They go on to explain how to configure a suitable pool but I have been unable to make it work.
Why does zpool not import / Dev / disk by id?
One in a while, zpool import -d /dev/disk/by-id doesn’t work. I’ve noticed this on more than one environment. I have an import script that, beyond also doing some magic logic and showing physically attached ZFS devices, also does basically this:
How to create zpool with / Dev / SDX devices?
Create your zpool with /dev/sdX devices first, then do this: I would still prefer to be able to do this with the initial zpool create though if possible. I know this thread is sort of stale, but there is an answer. You need to update your cache file after you import. This example shows the default location for the cache file.
When to use / dev / disk / by-id?
When creating pools, I always reference drives by their serials in /dev/disk/by-id/ (or /dev/disk/gpt on FreeBSD) for resiliency. Drives aren’t always in the same order in /dev when a machine reboots, and if you have other drives in the machine the pool may fail to mount correctly. For example, running zpool status on a 14.04 box I get this: