Let’s all agree with this fact: ZFS is foreign to Linux. It is not native. You can’t expect that ZFS on Linux will run smoothly as FreeBSD or Solaris. Having using ZFS on Linux since 2013 (and ZFS on FreeBSD since 2009), I’ve noticed that ZFS does not like Linux (well, at least RHEL 7). Here are some few examples:<\/p>\n
\r\n--> Finished Dependency Resolution\r\nError: Package: hypervvssd-0-0.29.20160216git.el7.x86_64 (base)\r\n Requires: kernel >= 3.10.0-384.el7\r\n Installed: kernel-3.10.0-327.el7.x86_64 (@anaconda)\r\n kernel = 3.10.0-327.el7\r\n Installed: kernel-3.10.0-327.22.2.el7.x86_64 (@updates)\r\n kernel = 3.10.0-327.22.2.el7\r\nError: Package: hypervfcopyd-0-0.29.20160216git.el7.x86_64 (base)\r\n Requires: kernel >= 3.10.0-384.el7\r\n Installed: kernel-3.10.0-327.el7.x86_64 (@anaconda)\r\n kernel = 3.10.0-327.el7\r\n Installed: kernel-3.10.0-327.22.2.el7.x86_64 (@updates)\r\n kernel = 3.10.0-327.22.2.el7\r\nError: Package: hypervkvpd-0-0.29.20160216git.el7.x86_64 (base)\r\n Requires: kernel >= 3.10.0-384.el7\r\n Installed: kernel-3.10.0-327.el7.x86_64 (@anaconda)\r\n kernel = 3.10.0-327.el7\r\n Installed: kernel-3.10.0-327.22.2.el7.x86_64 (@updates)\r\n kernel = 3.10.0-327.22.2.el7\r\n You could try using --skip-broken to work around the problem\r\n You could try running: rpm -Va --nofiles --nodigest\r\n<\/pre>\n<\/li>\n
\r\nLoading new spl-0.6.5.9 DKMS files...\r\nBuilding for 4.11.2-1.el7.elrepo.x86_64\r\nBuilding initial module for 4.11.2-1.el7.elrepo.x86_64\r\nconfigure: error: unknown\r\nError! Bad return status for module build on kernel: 4.11.2-1.el7.elrepo.x86_64 (x86_64)\r\nConsult \/var\/lib\/dkms\/spl\/0.6.5.9\/build\/make.log for more information.\r\n\r\n<\/pre>\n<\/li>\n<\/ul>\nRunning ZFS on Linux is like putting a giraffe in the wild in Alaska. It is just not the right thing to do. Unfortunately, there are so many things that only available on Linux so we have to live with it. Just like FUSE (Filesystem in Userspace), many people feel hesitated to run their file systems on the userspace instead of kernel level, but hey, see how many people are happy with GlusterFS, a distributed file system that live on FUSE! Personally I just think it is not a right thing to do, especially in an enterprise environment. Running a production file system at the userspace level, seriously?<\/p>\n
Anyway, if you are running into trouble after upgrading your Linux kernel (and you almost had a heart attack when you think your data may be lost), you have two choices:<\/p>\n
\n
- Simply boot to the previous working kernel if you need to get your data back in quick. However, keep in mind that this will create two problems:\n
\n
- Since you already update the system with the new kernel and the new packages, your new packages probably will not work with the old kernel, and that may give you extra headache.<\/li>\n
- Unless you manually overwrite the kernel boot order (boot loader config), otherwise you may get into the same trouble in the next boot.<\/li>\n<\/ul>\n<\/li>\n
- If you want a more “permanent” fix, you will need to rebuild the dkms ZFS and SPL modules. See below for the instructions. Keep in mind that you will have the same problem again when the kernel receives a new update.<\/li>\n<\/ol>\n
You’ve tried to load the ZFS and realize that it is no longer available:<\/p>\n
\r\n#sudo zpool import\r\nThe ZFS modules are not loaded.\r\nTry running '\/sbin\/modprobe zfs' as root to load them.\r\n\r\n#sudo \/sbin\/modprobe zfs\r\nmodprobe: FATAL: Module zfs not found.\r\n<\/pre>\nYou may want to check the dkms status. Write down the version number. In my case, it is 0.6.5.9<\/strong><\/p>\n
\r\n#sudo dkms status\r\nspl, 0.6.5.9, 3.10.0-327.28.3.el7.x86_64, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!)\r\nspl, 0.6.5.9, 3.10.0-514.2.2.el7.x86_64, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!)\r\nzfs, 0.6.5.9, 3.10.0-327.28.3.el7.x86_64, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!)\r\n<\/pre>\nBefore running the following commands, make sure that you know what you are doing.<\/p>\n
\r\n\r\n#Make sure that you reboot to the kernel you want to fix.\r\n#Find out what is the current kernel\r\nuname -a\r\nLinux 3.10.0-514.2.2.el7.x86_64 #1 SMP Tue Dec 6 23:06:41 UTC 2016 x86_64 x86_64 x86_64 GNU\/Linux\r\n\r\n#In my example, it is:\r\n3.10.0-514.2.2.el7.x86_64\r\n\r\n#Now, let's get into the fun part. We will remove them and reinstall them.\r\n#Don't forget to match your version, in my base, my version is: 0.6.5.9\r\nsudo dkms remove zfs\/0.6.5.9 --all\r\nsudo dkms remove spl\/0.6.5.9 --all\r\nsudo dkms --force install spl\/0.6.5.9\r\nsudo dkms --force install zfs\/0.6.5.9\r\n\r\n#or you can run these commands in one line, so that you don't need to wait:\r\nsudo dkms remove zfs\/0.6.5.9 --all; sudo dkms remove spl\/0.6.5.9 --all; sudo dkms --force install spl\/0.6.5.9; sudo dkms --force install zfs\/0.6.5.9;\r\n<\/pre>\nAnd we will verify the result.<\/p>\n
\r\n#sudo dkms status\r\nspl, 0.6.5.9, 3.10.0-514.2.2.el7.x86_64, x86_64: installed\r\nzfs, 0.6.5.9, 3.10.0-514.2.2.el7.x86_64, x86_64: installed\r\n<\/pre>\nFinally we can start the ZFS again.<\/p>\n
\r\nsudo \/sbin\/modprobe zfs\r\n<\/pre>\nYour ZFS pool should back. You can verify it by rebooting your machine. Notice that Linux may not automatically mount the ZFS volumes. You may want to mount it manually or via cron job.<\/p>\n
Here is how to mount the ZFS volumes manually.<\/p>\n
\r\nsudo zpool import -a\r\n<\/pre>\nYou may want to remove all of the old kernels too.<\/p>\n
\r\nsudo package-cleanup --oldkernels --count=1 -y\r\n<\/pre>\n<\/p>\n","protected":false},"excerpt":{"rendered":"