Skip to main content

How to automatically import a ZFS pool built on top of iSCSI devices with systemd

When using ZFS on top of iSCSI devices one needs to deal with the fact that iSCSI devices usually appear late in the boot process. ZFS on the other hand is loaded early and the iSCSI devices are not present at the time ZFS scans available devices for pools to import.

This means that not all ZFS pools might be imported after the system has completed boot, even if the underlying devices are present and functional. A quick and dirty solution would be to run zpool import <poolname> after boot, either manually or from cron.

A better, more elegant solution is instead to hook into systemd events and trigger zpool import as soon as the devices are created.
This solution has been tested with ZOL 0.6.4 and Centos 7 as of 2015/12.

First you will need to figure out the systemd disk ids that you wan systemd to notify you about.
This can be done by running systemctl list-units --all --full | grep disk from a shell with all disks mounted and/or connected. Disk ids are in the first column and the last part of the disk id is the same as the name found under /dev/disk/by-id/.

iSCSI disks helpfully report iSCSI_Storage under the last column.

Once you have figured out the systemd device id you need to create a custom service unit like the following (/etc/systemd/system/itank-pool.service):

IMPORTANT: Replace the device ids referenced by After and WantedBy with your device id.

Now try rebooting your server or systemctl reload, export the pool and restart the iscsi service. You should notice that just after the iSCSI devices appear systemd will run the zpool import service (one shot).

Comments

Popular posts from this blog

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

A not so short guide to TDD SaltStack formulas

One of the hardest parts about Infrastructure As Code and Configuration Management is establishing a discipline on developing, testing and deploying changes.
Developers follow established practices and tools have been built and perfected over the last decade and a half. On the other hand sysadmins and ops people do not have the same tooling and culture because estensive automation has only become a trend recently.

So if Infrastructure As Code allows you to version the infrastructure your code runs on, what good is it if then there are no tools or established practices to follow?

Luckily the situation is changing and in this post I'm outlining a methodology for test driven development of SaltStack Formulas.

The idea is that with a single command you can run your formula against a matrix of platforms (operating systems) and suites (or configurations). Each cell of the matrix will be tested and the result is a build failure or success much alike to what every half-decent developer of…