Yeah I also thought that the issue has been solved and that the update via GUI is safe again
[HOWTO] Instal ZFS-Plugin & use ZFS on OMV
-
- OMV 1.0
- raulfg3
-
-
So are they alright to update to?
-
It "should" be ok to upgrade simply via the update manager in OMV now. I haven't had the chance to test it myself yet though... My dev machine will most likely not be online for another day or so I'm afraid, so if someone else could test it would be very appreciated
-
-
I will test it later on if my OMV virtualbox still works, ATM I am really reluctant to test it on my production machine because of the hiccups the last month (my wife would kill me if all recordings would be offline)
-
First post should indicates if ZFS plugin is compatible with OpenMediaVault 2.x ("Stone Burner").
I am running OMV v1 ("Kralizec") and willing to update to v2 but I would like to know what issues I will face before upgrading...
-
I updated via GUI and it works
-
-
I updated via GUI and it works
After the update, what version of Debian and zfsonlinux are installed?
-
After the update, what version of Debian and zfsonlinux are installed?
How can I query the versions?
-
OMV 1.x and 2.x are both debian wheezy. So, zfs will be the same version.
For Debian version, cat /etc/debian_version
For zfs version, dpkg -l | grep zfs -
-
First post should indicates if ZFS plugin is compatible with OpenMediaVault 2.x ("Stone Burner").
I'm not sure how active the OP, @raulfg3, is in the forums nowadays so the info is a bit outdated...I am running OMV v1 ("Kralizec") and willing to update to v2 but I would like to know what issues I will face before upgrading...
Usually you need to ensure that the plugins are updated to work with the latest version of OMV, since from time to time new versions of ExtJS (framework upon which OMV is built) will actually change in such a way that a plugin can stop working. -
I updated via GUI and it works
Did you just use the "update manager"? And no errors reported?
That would be good
-
They also finally decided to place mount at S level. So you should consider removing the override.
Should this be done in the preinst script perhaps if there is an upgrade? Or do you have some other solution on how to remove it?
-
-
@ryecoaaron should know. I am pretty sure he did it in postinst. But IIRC zol implemented the same solution. So maybe is just enough with removing that part in postinst.
-
I would just remove the code in postinst. Sounds ZoL checks for it and adds it if necessary.
-
My concern is the existing override file that's going to be present on all systems that have had the plugin installed at some time. This could potentially cause issues in the future if ZoL decides to make further changes to the insserv scripts, or am I wrong?
-
-
Have the post or pre inst file remove the file then?
-
I'll add it to the preinst script in the coming days.
-
The (testing version) plugin is updated now to version 0.6.4.4 which removes the override file.
-
-
Updated version seems to be working very well for me here. Thanks
-
Great! Thanks for reporting back.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!