Zfs

I’ve been a happy ZFS user for years, appreciating its robustness and features. Yet, in all that time, I’d never had to rename a pool. That changed today. Whether it’s for better organization, a server migration, or just because you’ve had a change of heart about a name, renaming a ZFS pool is a task that might pop up when you least expect it. I needed to rename my pool from anime35 to anime36. I was pleasantly surprised to find the process is incredibly simple and elegant, which is what I’ve come to expect from ZFS. ...

If you use ZFS as the file system, you probably already know that tank is the most common name for ZFS pools. That also applies to me, I do name most of my ZFS pools as tank as the default. There is no issue with that name, however, since ZFS’s pool name must be unique, this means I couldn’t import or have multiple ZFS pools with the name tank on a system. ...

This is just a quick note to jot down what I did to resize and expand a ZFS partition to entire disk. I never had to do this before; it tured out it was quite easy. First ensure that the autoexpand option is set on the zpool. Then, stop the VM in order to resize the disk volume. [root@phnomaural ~]# zpool set autoexpand=on immich [root@phnomaural ~]# poweroff [root@phnomaural ~]# Connection to phnomaural closed by remote host. The original size of ZFS disk was 256 GiB, and it has been increased to 512 GiB. This was done by stopping the VM running on XCP-ng, and go to the disk and change the size to 256 GiB. ...

Earlier today while performing the update on my Fedora desktop, I encountered an issue with the new kernel update. As a result, the initramfs was not generated for the new installed kernel. So, I’ll share with you how to rebuild or generate the initramfs while fixing real issue on my Fedora workstation. First, here is an output showing the source of the issue. It might not be clear of what’s going on, but that’s okay as it’s not the main focus of this blog post. ...

It’s been quite a while since I last posted something here. It’s not that I haven’t come across many issues in tech, it’s just that I haven’t had enough time to write anything. So I’m going to share how to easily clear the ZFS metadata on a disk previously used in a ZFS pool. Here is an example - I have an external drive, and it is detected as /dev/da0 when plugged into a FreeBSD server. Though I don’t remember having used it as a member of a ZFS pool called tank, the following output does show that it is the case: ...