OMV 6 with ZFS: Good idea?

  • I have some experience with OMV 4 and 5.

    Now I want to install a completely new NAS mith OMV6, using ZFS-1 (RAID 5).


    Now I have some questions:


    -is 8GB RAM enough with a Intel I7 CPU?

    -can I start with just one ore two hdds and ZFS (without RAID) and later change to ZFS-1 without loosing data


    Thanks a lot for helping.

    3x OMV-NAS systems with ASUS H87I-PLUS, 1x MSI-Barebone

    • Official Post

    s 8GB RAM enough with a Intel I7 CPU?

    yes


    can I start with just one ore two hdds and ZFS (without RAID) and later change to ZFS-1 without loosing data

    no


    using ZFS-1 (RAID 5).

    Any reason why you need raid?

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.5 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    Just for not loosing my data if one disk fails in the RAID.

    And what if ransomware hit your system? raid isn't backup. You would be better off to backup one drive to another.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.5 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Am I correct that ZFS without RAID pools hdds and in case of a hardware failure only the files of this defective hdd are lost?

    With ZFS-Z1 this won't happen because one hdd can fail without loosing data.

    3x OMV-NAS systems with ASUS H87I-PLUS, 1x MSI-Barebone

    • Official Post

    Am I correct that ZFS without RAID pools hdds and in case of a hardware failure only the files of this defective hdd are lost?

    If you only want to group disks it is easier to use mergerfs and you will have the same thing without so many complications.

    With ZFS-Z1 this won't happen because one hdd can fail without loosing data.

    Yes, that's true.

  • Thanks chente.

    So what are the advantages/pro's of ZFS for home-use over the other more convenient filesystems OMV offers?

    Are there any to take in account?

    3x OMV-NAS systems with ASUS H87I-PLUS, 1x MSI-Barebone

    • Official Post

    So what are the advantages/pro's of ZFS for home-use over the other more convenient filesystems OMV offers?

    Are there any to take in account?

    In my opinion any kind of Raid is not necessary for a standard home system.

    If the information is valuable and is going to be stored for a long time, perhaps avoiding bitrot could be the only reason. For that you can use ZFS, BTRFS or snapraid.

  • In my opinion any kind of Raid is not necessary for a standard home system.

    If the information is valuable and is going to be stored for a long time, perhaps avoiding bitrot could be the only reason. For that you can use ZFS, BTRFS or snapraid.

    So ZFS, BTRFS or SnapRaid without RAID will avoid bitrot?

    Very interesting perspective and without RAID not all hdds need to spin up (?).

    3x OMV-NAS systems with ASUS H87I-PLUS, 1x MSI-Barebone

    • Official Post

    So ZFS, BTRFS or SnapRaid without RAID will avoid bitrot?

    When did I say that?

    You need parity to avoid bitrot, therefore you need some kind of Raid.

  • Back again to mergerfs: When I want to have just one share spaning over for example 3 hdds then I should use mergerfs.

    Am I right that if one of these 3 hdds fails just the files from this one hdd are lost/missing in the share but access to the remaining files/hdds is possible without problems?


    If I later change my mind and want a RAID-5 there ist no solution to add an additional disk and keep the data of my 3-hdd-share?

    3x OMV-NAS systems with ASUS H87I-PLUS, 1x MSI-Barebone

    • Official Post

    Back again to mergerfs: When I want to have just one share spaning over for example 3 hdds then I should use mergerfs.

    What do you mean? With three disks you can do a Raid5 in any Raid system.

    Am I right that if one of these 3 hdds fails just the files from this one hdd are lost/missing in the share but access to the remaining files/hdds is possible without problems?

    That's how it is. Here is the information you need about mergerfs. https://wiki.omv-extras.org/do…mv6:omv6_plugins:mergerfs

    If I later change my mind and want a RAID-5 there ist no solution to add an additional disk and keep the data of my 3-hdd-share?

    That is not possible with mdadm, nor with ZFS, nor with BTRFS. It would be possible with SnapRaid.

  • I configured OMV 6.3.12 with mergerfs successfully but got a lot of "connection Lost" errors.

    Is this a well known behaviour of OMV 6 or what else could be the problem?
    Never had any problems in my 1GB-home-Network.

    The hdds are from a older NAS-system.

    A USB3-Stick is used for OMV6.

    3x OMV-NAS systems with ASUS H87I-PLUS, 1x MSI-Barebone

    • Official Post

    but got a lot of "connection Lost" errors.

    Is this a well known behaviour of OMV 6 or what else could be the problem?

    Problem #1 Solutions to common problems

  • When creating mergerfs I get:


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color mergerfs 2>&1' with exit code '1': debian:

    ----------

    ID: configure_pool_dir

    Function: file.directory

    Name: /srv/mergerfs

    Result: True

    Comment: The directory /srv/mergerfs is in the correct state

    Started: 12:14:06.401157

    Duration: 3.953 ms

    Changes:

    ----------

    ID: remove_mergerfs_mount_files_/etc/systemd/system

    Function: module.run

    Result: True

    Comment: file.find: ['/etc/systemd/system/srv-mergerfs-MERGER\\x2d01.mount']

    Started: 12:14:06.405531

    Duration: 2.032 ms

    Changes:

    ----------

    file.find:

    - /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount

    ----------

    ID: systemd_remove_dead_symlinks

    Function: cmd.run

    Name: find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete

    Result: True

    Comment: Command "find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete" run

    Started: 12:14:06.407967

    Duration: 4.288 ms

    Changes:

    ----------

    pid:

    6299

    retcode:

    0

    stderr:

    stdout:

    /etc/systemd/system/multi-user.target.wants/srv-mergerfs-MERGER\x2d01.mount

    ----------

    ID: configure_mergerfs_MERGER-01

    Function: file.managed

    Name: /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount

    Result: True

    Comment: File /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount updated

    Started: 12:14:06.412440

    Duration: 37.136 ms

    Changes:

    ----------

    diff:

    New file

    mode:

    0644

    ----------

    ID: systemd-reload_MERGER-01

    Function: cmd.run

    Name: systemctl daemon-reload

    Result: True

    Comment: Command "systemctl daemon-reload" run

    Started: 12:14:06.449722

    Duration: 163.649 ms

    Changes:

    ----------

    pid:

    6306

    retcode:

    0

    stderr:

    stdout:

    ----------

    ID: enable_MERGER-01_mergerfs

    Function: service.enabled

    Name: srv-mergerfs-MERGER\x2d01.mount

    Result: True

    Comment: Service srv-mergerfs-MERGER\x2d01.mount has been enabled, and is in the desired state

    Started: 12:14:06.632960

    Duration: 327.67 ms

    Changes:

    ----------

    srv-mergerfs-MERGER\x2d01.mount:

    True

    ----------

    ID: restart_MERGER-01_mergerfs

    Function: cmd.run

    Name: systemctl restart srv-mergerfs-MERGER\x2d01.mount

    Result: False

    Comment: Command "systemctl restart srv-mergerfs-MERGER\x2d01.mount" run

    Started: 12:14:06.960897

    Duration: 7.615 ms

    Changes:

    ----------

    pid:

    6356

    retcode:

    5

    stderr:

    Failed to restart srv-mergerfs-MERGERx2d01.mount: Unit srv-mergerfs-MERGERx2d01.mount not found.

    stdout:


    Summary for debian

    ------------

    Succeeded: 6 (changed=6)

    Failed: 1

    ------------

    Total states run: 7

    Total run time: 546.343 ms


    OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color mergerfs 2>&1' with exit code '1': debian:

    ----------

    ID: configure_pool_dir

    Function: file.directory

    Name: /srv/mergerfs

    Result: True

    Comment: The directory /srv/mergerfs is in the correct state

    Started: 12:14:06.401157

    Duration: 3.953 ms

    Changes:

    ----------

    ID: remove_mergerfs_mount_files_/etc/systemd/system

    Function: module.run

    Result: True

    Comment: file.find: ['/etc/systemd/system/srv-mergerfs-MERGER\\x2d01.mount']

    Started: 12:14:06.405531

    Duration: 2.032 ms

    Changes:

    ----------

    file.find:

    - /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount

    ----------

    ID: systemd_remove_dead_symlinks

    Function: cmd.run

    Name: find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete

    Result: True

    Comment: Command "find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete" run

    Started: 12:14:06.407967

    Duration: 4.288 ms

    Changes:

    ----------

    pid:

    6299

    retcode:

    0

    stderr:

    stdout:

    /etc/systemd/system/multi-user.target.wants/srv-mergerfs-MERGER\x2d01.mount

    ----------

    ID: configure_mergerfs_MERGER-01

    Function: file.managed

    Name: /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount

    Result: True

    Comment: File /etc/systemd/system/srv-mergerfs-MERGER\x2d01.mount updated

    Started: 12:14:06.412440

    Duration: 37.136 ms

    Changes:

    ----------

    diff:

    New file

    mode:

    0644

    ----------

    ID: systemd-reload_MERGER-01

    Function: cmd.run

    Name: systemctl daemon-reload

    Result: True

    Comment: Command "systemctl daemon-reload" run

    Started: 12:14:06.449722

    Duration: 163.649 ms

    Changes:

    ----------

    pid:

    6306

    retcode:

    0

    stderr:

    stdout:

    ----------

    ID: enable_MERGER-01_mergerfs

    Function: service.enabled

    Name: srv-mergerfs-MERGER\x2d01.mount

    Result: True

    Comment: Service srv-mergerfs-MERGER\x2d01.mount has been enabled, and is in the desired state

    Started: 12:14:06.632960

    Duration: 327.67 ms

    Changes:

    ----------

    srv-mergerfs-MERGER\x2d01.mount:

    True

    ----------

    ID: restart_MERGER-01_mergerfs

    Function: cmd.run

    Name: systemctl restart srv-mergerfs-MERGER\x2d01.mount

    Result: False

    Comment: Command "systemctl restart srv-mergerfs-MERGER\x2d01.mount" run

    Started: 12:14:06.960897

    Duration: 7.615 ms

    Changes:

    ----------

    pid:

    6356

    retcode:

    5

    stderr:

    Failed to restart srv-mergerfs-MERGERx2d01.mount: Unit srv-mergerfs-MERGERx2d01.mount not found.

    stdout:


    Summary for debian

    ------------

    Succeeded: 6 (changed=6)

    Failed: 1

    ------------

    Total states run: 7

    Total run time: 546.343 ms in /usr/share/php/openmediavault/system/process.inc:197

    Stack trace:

    #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()

    #1 /usr/share/openmediavault/engined/rpc/config.inc(170): OMV\Engine\Module\ServiceAbstract->deploy()

    #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)

    #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)

    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatushx...', '/tmp/bgoutputaH...')

    #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))

    #7 /usr/share/openmediavault/engined/rpc/config.inc(192): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)

    #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)

    #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)

    #11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)

    #12 {main}

    3x OMV-NAS systems with ASUS H87I-PLUS, 1x MSI-Barebone

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!