Is ZFS supported in Kernel 4.13-4.15?

    • OMV 4.x
    • Resolved
    • Upgrade 3.x -> 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Skaronator wrote:

      0.7.4 is now in Debian SID and 0.7.5 has been just released with some minor fixes. Coming soon on Debian SID. (Maybe end of this week, early next week)

      0.7.4 add support for 4.14 Kernel which is important when backports update the kernel to 4.14.
      I've been following progress. I just uploaded the 0.7.4 versions of all of the zfs and spl packages.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.8
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • Is ZFS supported in Kernel 4.13?

      Hello guys,

      yesterday I got the following message from my omv4 machine:

      Source Code

      1. CRON-APT RUN [/etc/cron-apt/config]: Thu Jan 4 04:00:01 CET 2018
      2. CRON-APT SLEEP: 1676, Thu Jan 4 04:27:57 CET 2018
      3. CRON-APT ACTION: 3-download
      4. CRON-APT LINE: /usr/bin/apt-get -o Acquire::http::Dl-Limit=25 dist-upgrade -d -y -o APT::Get::Show-Upgraded=true
      5. Reading package lists...
      6. Building dependency tree...
      7. Reading state information...
      8. Calculating upgrade...
      9. The following NEW packages will be installed:
      10. linux-headers-4.14.0-0.bpo.2-amd64 linux-headers-4.14.0-0.bpo.2-common
      11. linux-kbuild-4.14
      12. The following packages will be upgraded:
      13. linux-headers-amd64
      14. 1 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
      15. Need to get 9043 kB of archives.
      16. After this operation, 53.3 MB of additional disk space will be used.
      17. Get:1 http://cdn-fastly.deb.debian.org/debian stretch-backports/main amd64 linux-headers-4.14.0-0.bpo.2-common all 4.14.7-1~bpo9+1 [7858 kB]
      18. Get:2 http://cdn-fastly.deb.debian.org/debian stretch-backports/main amd64 linux-kbuild-4.14 amd64 4.14.7-1~bpo9+1 [713 kB]
      19. Get:3 http://cdn-fastly.deb.debian.org/debian stretch-backports/main amd64 linux-headers-4.14.0-0.bpo.2-amd64 amd64 4.14.7-1~bpo9+1 [466 kB]
      20. Get:4 http://cdn-fastly.deb.debian.org/debian stretch-backports/main amd64 linux-headers-amd64 amd64 4.14+88~bpo9+1 [6280 B]
      21. Fetched 9043 kB in 5min 46s (26.1 kB/s)
      22. Download complete and in download only mode
      Display All

      So there is the new 4.14 kernel available. At the moment I am at kernel 4.9:

      Source Code

      1. root@omv4:~# uname -a
      2. Linux omv4 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64 GNU/Linux

      1. Is this new 4.14 kernel compatible with zfs?
      2. What is the correct upgrade path?


      Thanks and greetings Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------

      The post was edited 1 time, last by hoppel118 ().

    • hoppel118 wrote:

      Is this new 4.14 kernel compatible with zfs?
      I upgraded my test box to the 4.14 kernel and zfs works fine. dkms should compile a new module for the new kernel.

      hoppel118 wrote:

      What is the correct upgrade path?
      Install the updates from the web interface.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.8
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • OK, it works! I did the following steps:

      1. installed the new kernel
      2. activated the omv-extras.org testing repo (@'ryecoaaron' I read in another post that you maintain the latest zfs packages in your repo)
      3. did an apt-get update && apt-get upgrade
      4. installed the new zfs packages
      Everthing works as expected. A nice side effect is that my dvb card "digitital devices max s8" works out-of-the-box since kernel 4.14. PERFECT!

      Here are some system information:

      Kernel Version:

      Source Code

      1. root@omv4:~# uname -a
      2. Linux omv4 4.14.0-0.bpo.2-amd64 #1 SMP Debian 4.14.7-1~bpo9+1 (2017-12-22) x86_64 GNU/Linux

      Openmediavault Package Versions:

      Source Code

      1. root@omv4:~# dpkg -l | grep openmediavault
      2. ii openmediavault 4.0.15-1 all openmediavault - The open network attached storage solution
      3. ii openmediavault-clamav 4.1.4-1 all OpenMediaVault ClamAV plugin
      4. ii openmediavault-docker-gui 4.0.1 all OpenMediaVault plugin for Docker
      5. ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
      6. ii openmediavault-omvextrasorg 4.1.2 all OMV-Extras.org Package Repositories for OpenMediaVault
      7. ii openmediavault-zfs 4.0 amd64 OpenMediaVault plugin for ZFS

      ZFS Package Versions:

      Source Code

      1. root@omv4:~# dpkg -l | grep libnvpair1linux
      2. ii libnvpair1linux 0.7.4-1 amd64 Solaris name-value library for Linux
      3. root@omv4:~# dpkg -l | grep libuutil1linux
      4. ii libuutil1linux 0.7.4-1 amd64 Solaris userland utility library for Linux
      5. root@omv4:~# dpkg -l | grep libzfs2linux
      6. ii libzfs2linux 0.7.4-1 amd64 OpenZFS filesystem library for Linux
      7. root@omv4:~# dpkg -l | grep libzpool2linux
      8. ii libzpool2linux 0.7.4-1 amd64 OpenZFS pool library for Linux
      9. root@omv4:~# dpkg -l | grep spl-dkms
      10. ii spl-dkms 0.7.4-1 all Solaris Porting Layer kernel modules for Linux
      11. root@omv4:~# dpkg -l | grep zfs-dkms
      12. ii zfs-dkms 0.7.4-1 all OpenZFS filesystem kernel modules for Linux
      13. root@omv4:~# dpkg -l | grep zfs-zed
      14. ii zfs-zed 0.7.4-1 amd64 OpenZFS Event Daemon
      15. root@omv4:~# dpkg -l | grep zfsutils-linux
      16. ii zfsutils-linux 0.7.4-1 amd64 command-line tools to manage OpenZFS filesystems
      Display All

      zpool status:

      Source Code

      1. root@omv4:~# zpool status
      2. pool: mediatank
      3. state: ONLINE
      4. status: Some supported features are not enabled on the pool. The pool can
      5. still be used, but some features are unavailable.
      6. action: Enable all features using 'zpool upgrade'. Once this is done,
      7. the pool may no longer be accessible by software that does not support
      8. the features. See zpool-features(5) for details.
      9. scan: resilvered 2,27T in 14h25m with 0 errors on Sun Dec 31 10:58:16 2017
      10. config:
      11. NAME STATE READ WRITE CKSUM
      12. mediatank ONLINE 0 0 0
      13. raidz2-0 ONLINE 0 0 0
      14. ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E4KYX7HZ ONLINE 0 0 0
      15. ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E3NV2D2F ONLINE 0 0 0
      16. ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E5EC1TZ9 ONLINE 0 0 0
      17. ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E6LA42K7 ONLINE 0 0 0
      18. ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E6LA4ZJ8 ONLINE 0 0 0
      19. ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E7HP68ZE ONLINE 0 0 0
      20. ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E7XKY0DJ ONLINE 0 0 0
      21. ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E7XKY1AN ONLINE 0 0 0
      22. errors: No known data errors
      Display All

      "zpool status" shows that there are some new features available. Before I do the upgrade of my pool, I will need more time for tests with omv4.

      At the moment everything seems to work as expected. Great job!

      Thank you @ryecoaaron

      Greetings Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------
    • ArmandH wrote:

      I see that most people activate the testing repo of the extras, is this needed?
      It was mandatory if you were using the 4.14 kernel. Now, it is optional.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.8
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • Hello @Blabla,

      yes, zfs is compatible to omv4.

      Source Code

      1. root@omv4:~# cat /etc/debian_version
      2. 9.3

      Source Code

      1. root@omv4:~# uname -a
      2. Linux omv4 4.14.0-0.bpo.2-amd64 #1 SMP Debian 4.14.7-1~bpo9+1 (2017-12-22) x86_64 GNU/Linux

      Source Code

      1. root@omv4:~# root@omv4:~# modinfo zfs
      2. -bash: root@omv4:~#: Kommando nicht gefunden.
      3. root@omv4:~# modinfo zfs
      4. filename: /lib/modules/4.14.0-0.bpo.2-amd64/updates/dkms/zfs.ko
      5. version: 0.7.5-1~bpo9+1
      6. license: CDDL
      7. author: OpenZFS on Linux
      8. description: ZFS
      9. srcversion: 9C78552EF2E79ADAE6389FB
      10. depends: spl,znvpair,zcommon,zunicode,zavl,icp
      11. name: zfs
      Display All

      You have the choice to upgrade your pool:

      Source Code

      1. root@omv4:~# zpool status
      2. pool: mediatank
      3. state: ONLINE
      4. status: Some supported features are not enabled on the pool. The pool can
      5. still be used, but some features are unavailable.
      6. action: Enable all features using 'zpool upgrade'. Once this is done,
      7. the pool may no longer be accessible by software that does not support
      8. the features. See zpool-features(5) for details.
      9. scan: scrub repaired 0B in 13h57m with 0 errors on Sun Jan 14 14:21:17 2018
      10. config:
      11. NAME STATE READ WRITE CKSUM
      12. mediatank ONLINE 0 0 0
      13. raidz2-0 ONLINE 0 0 0
      14. ata-WDC_WD40EFRX-68WT0N0_WD-WCCXXXXXXXXX ONLINE 0 0 0
      15. ata-WDC_WD40EFRX-68WT0N0_WD-WCCXXXXXXXXX ONLINE 0 0 0
      16. ata-WDC_WD40EFRX-68WT0N0_WD-WCCXXXXXXXXX ONLINE 0 0 0
      17. ata-WDC_WD40EFRX-68WT0N0_WD-WCCXXXXXXXXX ONLINE 0 0 0
      18. ata-WDC_WD40EFRX-68WT0N0_WD-WCCXXXXXXXXX ONLINE 0 0 0
      19. ata-WDC_WD40EFRX-68WT0N0_WD-WCCXXXXXXXXX ONLINE 0 0 0
      20. ata-WDC_WD40EFRX-68WT0N0_WD-WCCXXXXXXXXX ONLINE 0 0 0
      21. ata-WDC_WD40EFRX-68WT0N0_WD-WCCXXXXXXXXX ONLINE 0 0 0
      22. errors: No known data errors
      Display All
      Until omv4 gets stable I won't do the suggested upgrade on my pool, because I don't know if it's possible to use an upgraded pool under omv3. I don't think that I will get back to omv3 ever, but who knows... ;)

      Greetings Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------

      The post was edited 1 time, last by hoppel118 ().

    • hoppel118 wrote:

      /--/ yes, zfs is compatible to omv4


      /--/ You have the choice to upgrade your pool:

      /--/ Until omv4 gets stable I won't do the suggested upgrade on my pool, because I don't know if it's possible to use an upgraded pool under omv3. I don't think that I will get back to omv3 ever, but who knows... ;)
      Just to be clear:

      How did you do your upgrade to OMV4?
      - On the command line with the version upgrade, or did you build from scratch?

      (If you did the command line upgrade.)
      - Did you strip out plugins?
      - Remove the ZFS plugin?
      - Do you use any Dockers?

      What was your pool export - import process, if any? I don't know what the command line OMV version upgrade would do in this scenario. (During tests in a VM, I exported a pool, built a fresh "same version" OMV install, and when ZFS drives were reconnected the pool auto-imported.)

      I don't mean to question you like a lawyer, but a brief overview would be great. :)
      Good backup takes the "drama" out of computing
      ____________________________________
      OMV 3.0.99 Erasmus
      ThinkServer TS140, 12GB ECC / 32GB USB3.0
      4TB SG+4TB TS ZFS mirror/ 3TB TS

      OMV 3.0.99 Erasmus - Rsync'ed Backup
      R-PI 2 $29 / 16GB SD Card $8 / Real Time Clock $1.86
      4TB WD My Passport $119
    • Is ZFS supported in Kernel 4.13?

      doublepost...
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------

      The post was edited 1 time, last by hoppel118 ().

    • Is ZFS supported in Kernel 4.13?

      flmaxey wrote:

      Just to be clear:

      How did you do your upgrade to OMV4?
      - On the command line with the version upgrade, or did you build from scratch?

      (If you did the command line upgrade.)
      - Did you strip out plugins?
      - Remove the ZFS plugin?
      - Do you use any Dockers?

      What was your pool export - import process, if any? I don't know what the command line OMV version upgrade would do in this scenario. (During tests in a VM, I exported a pool, built a fresh "same version" OMV install, and when ZFS drives were reconnected the pool auto-imported.)

      I don't mean to question you like a lawyer, but a brief overview would be great. :)


      I installed omv4 on another ssd to have the possibility to switch between omv3 and omv4. omv4 is still beta. This is my production system at home. ;)

      There were no problems in the setup procedure or in daily use. Everything works really, really smooth since more than a month. No need to get back to omv3 until now. ;)

      I use two docker container (emby and unifi) under omv4, both work as expected with docker ce, which I also used with omv3.

      The pool didn’t autoimport, but it was only one click in the webui of the plugin.

      Greetings Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------

      The post was edited 2 times, last by hoppel118 ().

    • I upgraded one of my boxes from the command line using omv-release-upgrade and all has been working well. I don't remember if I had to go to the ZFS tab in the web UI and import them again, but I did remove the drives for the upgrade.. I expect I probably did since hoppel mentioned above that he had to... I didn't remove any plugins, I just checked the ones I used were listed in OMV extras 4.

      A fresh install of OMV 4 on a Stretch installation with the backports 4.14 kernel is also working well. Just make sure contrib is in your sources. :)
    • Add is for a new pool. Import is what you'd use to pull in an existing pool.
      Good backup takes the "drama" out of computing
      ____________________________________
      OMV 3.0.99 Erasmus
      ThinkServer TS140, 12GB ECC / 32GB USB3.0
      4TB SG+4TB TS ZFS mirror/ 3TB TS

      OMV 3.0.99 Erasmus - Rsync'ed Backup
      R-PI 2 $29 / 16GB SD Card $8 / Real Time Clock $1.86
      4TB WD My Passport $119
    • Is ZFS supported in Kernel 4.13?

      As flmaxey said, import is to see your previously created tank(s). The tank is there on your drives, it just needs, well... importing!

      It’s also good practice to export a tank if moving it to another system (including fresh install). This changes the tanks metadata and puts it into a ‘dormant’ state making sure it’s not being used by anything else.

      If you forget though and you know nothing else is using it (ie. you shut down, remove tank drives, fresh os install then replug tank drives), you can always use the -f flag via the import command to force the import. I think there is also a switch in OMV for this. It can be dangerous though if you don’t know for sure the tank isn’t being used elsewhere.

      The following kind of goes against the ease of use that OMV is designed to provide, but you can also:

      Source Code

      1. zpool import Tank


      From the terminal then go to the ZFS tab in OMV and it will pop up with the yellow banner and ask if you want to save changes. Do this and OMV will accept the tank.

      To force an import for whatever reason (please do make sure you understand why you might be doing this and that the pool is definitely not in use elsewhere) you would:

      Source Code

      1. zpool import -f Tank


      Then visit the ZFS tab in OMV. You will usually know if you need to force an import as ZFS will throw an error warning that the tank was not exported.

      I really must stress though, that unless you know what you are doing, the -f switch shouldn’t just be used haphazardly.

      I tend to do a lot of my ZFS stuff from the command line and use the plugin for a quick overview of my pools - and probably the most useful thing about the plugin is that it’s a one click ZFS setup. Shame Debian doesn’t follow in Ubuntu’s footsteps and include ZFS in their main repos. Yes I know it’s a grey area but Ubuntu seem to have managed ok so far.

      On a different ZFS note, users of parted magic and ZFS will be thrilled to know that parted magic comes with ZFS support out the box! I booted into parted magic to make an image of a fresh server install, and noticed that it had imported the tank on that box. I’m sure this is a breach of the GPL having CDDL code included with it but then so is charging for a bunch of GPL stuff you didn’t code and simply ‘arranged’ nicely. In an ideal world it would be great if all concerned at Oracle would just change the ZFS license to GPL.. but I think BTRFS has more chance of getting stable RAID 5/6 and non-sucky VM performance before we ever see the day that happens :P


      Sent from my iPhone using Tapatalk
    • Just a question: is this error during installation normal?
      Building initial module for 4.14.0-0.bpo.3-amd64
      configure: error:
      *** Please make sure the kmod spl devel <kernel> package for your
      *** distribution is installed then try again. If that fails you
      *** can specify the location of the spl objects with the
      *** '--with-spl-obj=PATH' option. Failed to find spl_config.h in
      *** any of the following:
      /usr/src/spl-0.7.5/4.14.0-0.bpo.3-amd64
      /usr/src/spl-0.7.5
      Error! Bad return status for module build on kernel: 4.14.0-0.bpo.3-amd64 (x86_64)
      Consult /var/lib/dkms/zfs/0.7.5/build/make.log for more information.
      Processing triggers for openmediavault (4.0.17-1) ...
      Restarting engine daemon ...
      Setting up linux-headers-4.14.0-0.bpo.3-common (4.14.13-1~bpo9+1) ...
      Setting up libzpool2linux (0.7.5-1~bpo9+1) ...
      Setting up linux-headers-4.14.0-0.bpo.3-amd64 (4.14.13-1~bpo9+1) ...
      /etc/kernel/header_postinst.d/dkms:
      cp: cannot stat '/var/lib/dkms/spl/0.7.5/build/spl_config.h': No such file or directory
      cp: cannot stat '/var/lib/dkms/spl/0.7.5/build/module/Module.symvers': No such file or directory
      Intel G4400 - Asrock H170M Pro4S - 8GB ram - 2x4TB WD RED in RAID1 - ZFS Mirror 2x6TB Seagate Ironwolf
      OMV 4.1.4 - Kernel 4.14 backport 3 - omvextrasorg 4.1.2
    • I've built ZFS using the GUI plugin, 5 or 6 times. Out of all those events, I think 1 or maybe 2 installs showed no errors. With one exception, even with the errors (similar to what you have above), all the installations worked.

      In the one case where the install failed, the "ZFS" icon didn't appear in OMV. (I think this failure was related to the repository being temporarily unavailable.) I tried it again, a few hours later, and the install worked.
      ________________

      In my limited experience, if you see the "ZFS" icon under Storage, the installation will work.
      Good backup takes the "drama" out of computing
      ____________________________________
      OMV 3.0.99 Erasmus
      ThinkServer TS140, 12GB ECC / 32GB USB3.0
      4TB SG+4TB TS ZFS mirror/ 3TB TS

      OMV 3.0.99 Erasmus - Rsync'ed Backup
      R-PI 2 $29 / 16GB SD Card $8 / Real Time Clock $1.86
      4TB WD My Passport $119