[HOWTO] Instal ZFS-Plugin & use ZFS on OMV

Well This post is intendent to show how to start to work with ZFS & ZFS Plugin in OMV, Is usefull for beginers & Users that come from BSD ( FreeNAs & Nas4Free) World to understand certain diferrences between ZFS and ZFS on Linux.

1- Import your existing Pool ( use option in ZFS menu) ; remember that latest FreeNAS pools (9.3 and up) can't be imported due a Feature Flag not still implemented on ZFS for Linux (9.2 and down can be imported without problem), So please revise what feature Flags have your pool beforo to try to import on OMV
2 - Create a new Pool.

If you want to create a pool your disk must be clean, to be sure use wipe from menu:

Source Code

echo "options zfs zfs_arc_max=3221225472" >> /etc/modprobe.d/zfs.conf

echo "options zfs zfs_arc_min=3221225472" >> /etc/modprobe.d/zfs.conf

I use values that experience recommended on BSD= Nas4Free if you search for a good tunning tool called ZFSKerntune and analize, you can see that only fixes zfs_arc_max and zfs_arc_min to desirables values.

"Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.Upload Logfile via WebGUI/CLI
#openmediavault on freenode IRC | German & English | GMT+1
Absolutely no Support via PM!

I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.

Source Code

status: One or more devices could not be used because the label is missing

or invalid. There are insufficient replicas for the pool to continue

functioning.

action: Destroy and re-create the pool from

a backup source.

see: http://zfsonlinux.org/msg/ZFS-8000-5E

scan: none requested

config:

NAME STATE READ WRITE CKSUM

Media UNAVAIL 0 0 0 insufficient replicas

raidz1-0 UNAVAIL 0 0 0 insufficient replicas

sdd ONLINE 0 0 0

sde UNAVAIL 0 0 0

sdf UNAVAIL 0 0 0

Display All

It appears that this is because the drives were originally: sdd, sde, and sdf. They now appear to have been reassigned sdb, sdc, and and sdd.

This could be a failing on my part, I expect I should have selected 'By ID' not 'By Path' but the "Specifies which device alias should be used. Don't change unless needed." made me leave it alone... surely it should always be by ID and this should be the default? Anyway, fixed with:

Source Code

zpool export Media

then imported the pool again.

By importing the pool again, it appears that the drives have now been imported by ID:

Source Code

/mnt/Media # zpool status Media

pool: Media

state: ONLINE

scan: none requested

config:

NAME STATE READ WRITE CKSUM

Media ONLINE 0 0 0

raidz1-0 ONLINE 0 0 0

ata-ST4000DM000-1F2168_XXXXXXX ONLINE 0 0 0

ata-ST4000DM000-1F2168_XXXXXXX ONLINE 0 0 0

ata-ST4000DM000-1F2168_XXXXXXX ONLINE 0 0 0

Display All

Thus preventing this from occuring again.

Is it possible to have the default option for 'Device alias' changed to 'By ID'? - especially if the user is warned not to touch it.