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....
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....
I’m a fan of ZFS filesystem. It’s so good that I also use ZFS on most my Linux machines, though it’s painful at time when the ZFS kernel modules fail to compile. Why I like it so much comparing to other file system such as XFS, EXT4, BTRFS? ZFS allows me to quickly do snapshots and efficiently send snapshots over the network, and my nas runs FreeBSD which support ZFS natively....
ZFS is one of my favorite file systems. I use it at home on my nas server (running FreeBSD) as well as my Fedora 32 desktop. Today, I’m going to show you (and my future self) how to replace a (faulty) disk in a Zpool. The server I’ll be working on is nas2 and the pool is tank. List the status of the current pool. Password: root@nas2:~ # zpool status tank pool: tank state: DEGRADED status: One or more devices could not be opened....
I’m still running Fedora 31 on my main desktop though Fedora 32 beta has been out for a while. The only reason that stops me from jumping to F32 now is because ZFS 0.8.3 is not compatible with the kernel 5.6.* on F32. Rumor has it, ZFS 0.8.4 will support kernel 5.6. Tonight, while doing the system update with sudo dnf update -y on F31 desktop, I noticed that the kernel for F31 is now kernel-5....
Up until today, I have been running Fedora 29 with the kernel 4.9. The current version of the kernel on Fedora 29 is 5.0. However, I had to stick with the 4.20 version for a very long while due to a thing I did a short while back. So what is that thing? Well, at one point ZFS (stable) no stopped working with the new kernel on Fedora 29. At then, I had a choice to either keep running older version of the kernel or trying out the new version of ZFS (testing)....
When Fedora release kernel 4.20.*, the ZFS 0.7.12 could no longer compiled. Accoriding to the ZFS release page at Github zfs-0.7.12 is only compartible iwth kernels 2.6.32 - 4.19. At first I was going to just wait for the 0.8.0 release, and continue to use kernel 4.19. However, Fedora keeps releasing the updates of kernel 4.20. As of this writing, the current version of the kernel on Fedora 29 is 4....
FreeBSD 12.0-RELEASE was released today, and that means it’s time to upgrade 2 of FreeBSD 11.2 machines to this latest version. One of my FreeBSD boxes is a desktop used at work, and the upgrade went well without any issues. In this post, I’m going to document how the upgrade is done on my nas server at home. First ensure that the FreeBSD is up to date: root@nas:~ # freebsd-update fetch src component not installed, skipped Looking up update....
FreeBSD 11.2-RELEASE was released a few days ago. This means it’s time to upgrade the FreeBSD running on my nas. For the most part, this was all what I did: After it’s been upgraded, I also need to update the Zpool. Let’s upgrade the zpool as suggested: Next is to update the boot code. If for whatever reason you’re following this step to update zpool (zroot) on your FreeBSD, make sure you know what is your boot disk is....