If you don't enable the regular zfs repo, the zfs packages from the debian repo will be used. If you enable both, the packages from zfsonlinux will be used. Currently, the Debian packages are newer.
[HOWTO] Instal ZFS-Plugin & use ZFS on OMV
-
- OMV 1.0
- raulfg3
-
-
If you don't enable the regular zfs repo, the zfs packages from the debian repo will be used. If you enable both, the packages from zfsonlinux will be used. Currently, the Debian packages are newer.
Care to elaborate a bit here?
If enabling regular ZFS plugin (stable): which repo wil be used?
And if enabling just ZFS-testing, which will be used?I see, for me, a lot of people with issues and I want to be sure of which to use when I receive my new OS drive and start my upgrade to erasmus
-
Care to elaborate a bit here?
I thought I did. The omv-extras zfs repo (not testing) will enable the zfsonlinux repo. The omv-extras zfs testing repo does not enable the zfsonlinux repo. The omv-extras zfs testing repo is just for testing version of the plugin and has nothing to do with where the zfs packages come from.
I see, for me, a lot of people with issues and I want to be sure of which to use when I receive my new OS drive and start my upgrade to erasmus
It isn't like if you pick one, you are locked into that choice. Worst case, you have to uninstall the plugin and reinstall it.
If enabling regular ZFS plugin (stable): which repo wil be used?
zfsonlinux
And if enabling just ZFS-testing, which will be used?
debian
-
Great! Thank you for the clarification
-
I thinking about getting rid of the zfsonlinux repo from omv-extras. The version in the Debian repo is newer and more compatible with newer kernels. This would mean the zfs plugin could be in the regular repo. If someone wanted the zfsonlinux repo, they could manually add it in omv-extras. Thoughts?
-
How will the transition be for regular users?
Im sitting and installing OMV3 right now, should I enable zfs testing and upon reply when ZOL repo is disabled go back to ZFS stable?
-
Regular users? Not sure what that means.
The two repos would disappear. If you were zfsonlinx, updates to the newer debian packages would appear in the updates tab. That should be it. I think the two repos cause more confusion than anything and the debian packages come from zfsonlinux anyway.
-
More compatibility to new kernels and newer packages from official debian repo... At the moment it seems to be the right way. If this situation changes, you can bring back the zfsonlinux repo.
Greetings Hoppel
-
When booting:
Failed to start ZFS-mount -a during boot.
this results in all kinds of errors and loosing mounts/folders etc.
-
@bug11 Check your /etc/default/zfs file and look for the ZPOOL_IMPORT_PATH parameter. This should map how your pool is created/imported. If you want to change from one format to another you can do the following (this would use the /dev/disk/by-vdev format for a pool named tank):
Code$ zpool export tank $ zpool import -d /dev/disk/by-vdev tankThe information above is found on https://github.com/zfsonlinux/zfs/wiki/FAQ which has a lot of good information on which format to use when.
-
@ryecoaaron I think removing the zfsonlinux repo sounds like a good idea. Would hopefully make things clearer.
-
The plugin has been moved or been down for a while?
-
The plugin has been moved or been down for a while?
No. I removed the zfsonlinux repos from omv-extras in favor of the packages in the official Debian repo (which are also from zfsonlinux).
-
Hmm.. Fresh fresh installation and I can't see the plugin in the list for installation.
-
Do you have zfs-testing enabled? The system has to be 64 bit too.
-
I forgot to mention that I use OMV3. I don't see even the repo, which is the most weird from all. No update packages available.
PS. amd64 always. It is a re-installation from scratch as I had the impression that during the progress from 3.0.15 to the latest, the system gone little wild!
-
There is no zfs repos anymore. The plugin will be in the regular and testing repos. I forgot to put the plugin in those repos. Fixed now.
-
Much better now.
Only thing that I saw are three warnings:Setting up openmediavault-zfs (3.0.5) ...
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
WARNING: The function 'omv_config_add_element' is deprecated.
Processing triggers for libc-bin (2.19-18+deb8u6) ... -
Only thing that I saw are three warnings:
This is fixed on github but as the message says, they are only warnings. There was no need to release a new version just to fix this.
-
Sounds logical. I just mention it in case that wasn't known.
Sent from my bacon
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!