Posts by sbocquet

    Hi,


    Just to let you know that I have successfully update my ZFS pool from kernel 4.14/ZFS 0.7.6 to kernel 4.16/ZFS 0.7.9


    1st => Update ZFS from 0.7.6 to 0.7.9., than reboot the NAS. The pool cannot be mounted (as expected) but don't panic ;)
    2nd => Update from kernel 4.14 to kernel 4.16, than reboot the NAS. The pool is mounted and healthy.


    Thanks all for your advices.

    A lot of the zfs plugin problems are due to the kernel and zfs versions. Moving to Ubuntu would definitely fix that. Even if zfs was a core feature (not going to happen), it would still have to be maintained. If OMV 5.x is designed around btrfs, I think it will be easier to make zfs "happy".

    I don't want to be rude, but please, save us from BTRFS ;)


    Honestly, I don't mind using one or the other, I'm not a church preacher. I just want something that works and secures my datas; but in 2018, BTRFS development is near death ;)...
    If Oracle (and I don't like them too ;) ) use ZFS in Solaris, believe me, it's because it's rock solid, unlike BTRFS. ZoL is probably not as solid as ZFS on Solaris, but clearly, it is far ahead.


    https://www.ixsystems.com/blog/open-zfs-vs-btrfs/
    http://blog.fosketts.net/2017/07/10/zfs-best-filesystem-now/


    We will see...

    What do you mean by native?

    I know Debian cannot have ZFS directly after finished the install (and so OMV), but ZFS is a must have when you come to NAS storage.


    Maybe the Ubuntu way (and don't get me wrong, I really prefer Debian) should be consider as ZFS should be a basic feature out of the box for a NAS.
    I clearly don't speak for myself as I work all day on computers, but let's think of basic users.


    On the other hand, the ZFS plugin is doing some really good work for that... but when problems comes, and they come, you have to know what your doing. Plus you have to update/maintain the plugin...

    I only use Debian as server (work and home) and Windows/Mint LMDE as Workstation (home), and I just can be agree with you... OMV need ZFS as a 'native' storage solution.


    I work all days on Solaris 11 with native ZFS storage, and I cannot go back to RAID/ext 4 without feeling 'in danger'.
    File checksum is a must have, and so the snapshots... They solve some of my problem before it happens !

    I don't know…


    For me, I'm with a 4.14 kernel from the backports repo, which installed me certbot v0.23 as I suppose, which is running with python 3.x
    At the moment, this should work as it seems that I have the necessary packages to… but there is a mystery that I have to understand before my cert expired… :(

    OK... I found the problem with the letsencrypt forum...


    So, as always, it was so simple that I haven't though of it (RTFM !).


    My port 80 was only opened to my internal network in the firewall, and certbot need a file to be seen globally in order to renew the certificat.
    So I opened the port 80, renew my cert and closed it after.


    I have just asked if this can be done through HTTPS, else I will do the same in 90 days...

    Hi there ;)


    So, I was wondering if I can go with the ZFS update to v0.7.9 with my 4.14 kernel as I can see the ZFS package are available ?
    I have the linux-headers installed for that kernel.



    Do you see any risk ?
    If that doesn't work, can I rollback if I keep my current conf available at boot ?


    Thx


    P.S : Don't you think we could add a specific zone in the forum for all the ZFS stuff, like for RAID or in the Configuration section ? This could be a good improvment no ?

    I don't know…


    For me, I'm with a 4.14 kernel from the backports repo, which installed me certbot v0.23 as I suppose, which is running with python 3.x
    At the moment, this should work as it seems that I have the necessary packages to… but there is a mystery that I have to understand before my cert expired… :(

    Yes, it seems to be the same except that you're running python 2.7...


    and me python 3.0

    I was thinking it was ;)


    Code
    root@home-server:/etc/apt/sources.list.d# apt-cache policy certbot
    certbot:
      Installé : 0.23.0-1~bpo9+1
      Candidat : 0.23.0-1~bpo9+1
     Table de version :
     *** 0.23.0-1~bpo9+1 100
            100 /var/lib/dpkg/status
         0.10.2-1 500
            500 http://ftp.fr.debian.org/debian stretch/main amd64 Packages

    I pinned the newer certbot package with omv-extras (if backports is enabled - you can disable backports in omv-extras) to allow creation of wild card certs. But installing python 3 is not an upgrade. It is installed side-by-side with python 2. So, it won't hurt to install it. I guess I will have to look at the plugin's dependencies though.


    Unfortunatly, I can't see it… with or without backports enabled


    Code
    root@home-server:/etc/apt/sources.list.d# cat omv-extras-org.list
    # This is file is generated.
    # OMV-Extras repos
    #
    # OMV-Extras.org
    deb https://dl.bintray.com/openmediavault-plugin-developers/arrakis stretch main


    Hi all,


    My certificat is working fine at the moment and was created with the plugin. But it is about to expire and I just noticed that the automatic renew process is failing :(


    So I tried to renew it by hand.



    I can see that in the log file:

    Here is the Python version

    Code
    root@home-server:/etc/cron.d# python -V
    Python 2.7.13

    Don't know what to do. Any help would be greatly appreciated.


    Thx



    EDIT:
    After a few research, I found that my certbot package was updated with the one from stretch-backports (v0.23) which need python 3 !
    I don't think that upgraded python to v3.x is a good solution, so I simply want to downgrade the certbot package to the one in the stretch repository (v 0.10).



    I'm a little nervous to "update" all those package ??? Is it safe or am I going to break everything in OMV ?

    No, just created the pool with the plugin the first time I use it.


    Here is the log :


    Seems to have work ;)

    Already done… and nothing. Strange??? Maybe the property added to the pool/fs isn't enough?


    I'm thinking of removing the plugin as I want to update to kernel 4.16 and ZFS 0.7.9 too… I don't think it will remove ZFS DKMS but the fact is that I probably have to delete samba shares. And what about share folders ? Are they going to be deleted too ?

    Just tried to set the property manually… but no effect. Do I need to reboot or something ?


    Code
    root@home-server:/etc/openmediavault# zfs set omvzfsplugin:uuid=864e8b70-edf9-48fb-a2fc-7fe7dbab1c2f StoragePool
    
    
    root@home-server:/etc/openmediavault# zfs get -s local all StoragePool
    NAME         PROPERTY              VALUE                                 SOURCE
    StoragePool  atime                 off                                   local
    StoragePool  omvzfsplugin:uuid     864e8b70-edf9-48fb-a2fc-7fe7dbab1c2f  local

    I can't test because the 4.14 kernel headers aren't available anymore. I would backup your system before trying this:
    Remove the 4.14 kernel headers
    Install 4.16 kernel and zfs 0.7.9 at same time. It should skip compiling the zfs module for the 4.14 kernel since the headers aren't there.
    Reboot using the 4.16 kernel
    Remove the 4.14 kernel

    Will be happy to try but how can I get the ZFS 0.7.9 packages ?
    The only version I have is the 0.7.6 with stretch-backport

    EDIT: Found in OMV-extra Testing ;)