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

Hi,

I'm in the process of setting up a new OMV, but I'm having some trouble with ZFS.

I have followed the tutorial in this thread, but when I want to install the omv-zfs plugin, I receive this error:

>>> *************** Error ***************
Failed to execute command 'export LANG=C; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --force-yes --fix-missing --allow-unauthenticated --reinstall install openmediavault-zfs 2>&1': Reading package lists...


Building dependency tree...


Reading state information...


The following NEW packages will be installed:
  openmediavault-zfs
0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
Need to get 54.5 kB of archives.
After this operation, 317 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  openmediavault-zfs
Authentication warning overridden.
Get:1 http://packages.omv-extras.org/debian/ stoneburner-zfs/main openmediavault-zfs amd64 0.6.4 [54.5 kB]
Fetched 54.5 kB in 0s (212 kB/s)
Selecting previously unselected package openmediavault-zfs.
(Reading database ...
42693 files and directories currently installed.)
Unpacking openmediavault-zfs (from .../openmediavault-zfs_0.6.4_amd64.deb) ...
Processing triggers for openmediavault ...
Restarting engine daemon ...
Setting up openmediavault-zfs (0.6.4) ...
Initialize configuration
update-rc.d: using dependency based boot sequencing
insserv: There is a loop between service umountfs and zfs-import if stopped
insserv:  loop involving service zfs-import at depth 4
insserv:  loop involving service zvol at depth 3
insserv: There is a loop between service umountfs and zfs-import if stopped
insserv:  loop involving service umountfs at depth 3
insserv:  loop involving service umountnfs at depth 2
insserv:  loop involving service networking at depth 5
insserv:  loop involving service umountroot at depth 8
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing openmediavault-zfs (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for openmediavault ...
Restarting engine daemon ...
Errors were encountered while processing:
 openmediavault-zfs
Creating index of upgradeable packages ...
Creating index of openmediavault plugins ...
E
:
Sub-process /usr/bin/dpkg returned an error code (1)


<<< *************************************

Any ideas what could be the problem?

Could you try with the "testing" version of the plugin available in the ZFS testing repo? Please report back if it works...

That was the one I used for the installation (as instructed in the tutorial).

Ok, could you just verify that the version of the plugin you tried to install is 2.1.0?

Edit: When reading the log I see you tried to install 0.6.4...

0.6.4 is the only one in the plugins list. How can i select 2.1.0?

Could you try and remove both ZFS repos from the OMVextras page, then save. Next update the list of plugins and make sure that there are no ZFS plugin to choose. Finally re-enable the ZFS repos again and update the list of plugins. Not sure if this will help, but I have version 2.1.0 available here.

Disabled both ZFS and ZFS Testing, and the ZFS plugin disappeared from the list. Re-enabled ZFS and ZFS testing, 0.6.4 is back on the list after refresh.

Never mind, solved it.

Hi,

I am trying to access and share a freenas Zfs pool in omv using the zfs plugin.

I have imported the pool on the omv server and it is mounted.

I can see the pool in the File Systems tab, it shows the correct size and that it is mounted, but not referenced.

When I go to the ZFS tab I get a loading message followed by a communication failure error.

Any help would be appreciated.

Cheers

Can you enable the console view in your browser (probably by pressing F12) and post the messages printed there when you try to access the ZFS page?

Thank you for your reply.

There does not appear to be any messages in the console when I select the ZFS option.

Could you run the following command as root in CLI: zfs list -H -t all -o name,type and post the result here (unless it contains some sensitive data). I'm not sure what's wrong but it might be that there is a loop that doesn't terminate properly (for some unknown reason).

The results below

root@openmediavault:/etc/nginx/sites-available# zfs list -H -t all -o name,type
BackupPool filesystem
BackupPool/Backups filesystem
root@openmediavault:/etc/nginx/sites-available#

If I ftp to the server I can see the BackupPool directory in the root, all directories and files appear to be correct in sub-directories.

Could it be that there are 2 zfs in the list an I only have 1?

I've uploaded a new version to the stable repo (2.1.0). Could you try to update the plugin and reload the page to see if it helps. Looking at your output above I can't really see anything strange.

Hello Forum,

I bought a HP ProLiant MicroServer Gen8, Celeron G1610T, 4GB RAM with two 2GB HDs and a MicroSDCard for the OS. I followed the instructions for installing OMV and the ZFS extension. Now I want to create an RAID 1 encrypted Volumen with ZFS. I want to give the decryption password evertime the server starts. Currently I'm creating my first ZFS mirror RAID. Can someone give me a hint, how I can set the encryption in place?

Thanks

Peter

Maybe LUKS can be used for encryption? There is a plugin available LUKS disk encryption plugin and hopefully you can get some help/ideas from that thread.

Thank you for your share!

I would spend a little bit of time reading about encryption on ZFS. ZFS works best when it knows about the files and the physical medium on which they're stored. As soon as you add another layer, be it an encrypted container, or something else, ZFS loses a lot of it's benefits. I'm not sure if it makes it worse than a traditional file system so please do some research.

You can gain some of the benefits of encryption and retain all of the benefits of ZFS by using a file-based encryption overlay like encfs or ecryptfs. I believe the former has some weaknesses so the latter is what you'll probably want. Rather than encrypting the full disk, or a container of some kind, these encrypt individual files transparently. When you look at your filesystem normally, you'll see encrypted files and file names. When you then mount that mounted filesystem elsewhere with one of those tools, providing the passphrase, you'll see the unencrypted content. Unfortunately, file metadata is not encrypted, so ownership information, file sizes, access times, etc. are preserved while file data and file names are not. Additionally, both of these maintain the behavior of sparse files, so attackers can tell when and where contiguous blocks of zeros exist in encrypted files.