Try updated version of the plugin here. It will automatically do the necessary items you outlined above.
I was about to ask for help with this, but you were to fast again
Try updated version of the plugin here. It will automatically do the necessary items you outlined above.
I was about to ask for help with this, but you were to fast again
So, did the latest plugin update work for you?
I was about to ask for help with this, but you were to fast again
subzero and I have been discussing it over threema.
Well, now you only have to allow mount with noatime.
Speaking of mounting options... Should zfs be mounted noexec like the other filesystems?
NO!
.
.
.
I hate those linux things. Like programs executing in other groups than Administrators or Users.
I want to put my dropbox/owncloud there and be able to execute my scripts.
But my disks are waking-sleeping-waking all day long. I found that important enough to take a look. I hope no disk breaks. I removed my power savings from the ZFS array, as it's true that a disk in a stripped array it's not supposed to independently sleep. But Snapraid is another thing.
Well, it should at least be the default option then. All of the other OMV filesystems are noexec.
Sergio, I know you don't like it but it is a security feature You hate those "linux things" but OMV is Linux If a malicious binary is put on a shared folder from over the network, it could be executed. This is why shared folders can't be on the OS partition and why data drives are mounted noexec.
So, I've installed the openmediavault-omvextrasorg_latest_all.deb, selected ZFS under the secondary tab, upgraded through the update manager and uploaded the openmediavault-zfs_0.6.3.4_amd64.deb to install the plugin but I don't see the ZFS option under "Storage". It should show up under "Storage" right?
Thanks!
Edit: Never mind, installed another plugin, ZFS finally showed!
Alles anzeigenOk. This problem just appeared now, the mounting of ZFS datasets and pools is happening way way too late in the boot sequence (is the last one executed actually), affecting other services that depend on access to those shares inside those datasets (media browser plugin).
Perform the following changes at your own risk, this will enable zfs mounts at runlevel S (single user) mode, that's usually where all fs are mounted.
nano /etc/insserv.conf, at this line
$local_fs +mountall +mountall-bootclean +mountoverflowtmp +umountfs add zfs to the end like this
$local_fs +mountall +mountall-bootclean +mountoverflowtmp +umountfs zfs
then nano /etc/init.d/zfs-mount, lines
Change them to
Activate boot reordering with
insserv -v -d zfs-mount
This problem comes from the debian-zfs package which is not provided by OMV, please forward a request for change at the corresponding website. The plugin is only intended for managing pools, fs and zvol's
Reference: http://wiki.complete.org/Conve…Activating_init.d_changes
I reverted the changes and updated insserv - however ZFS still gets mounted in time like with the fix !?
Can I apply the new ZFS plugin without danger, or will it likely brake something?
I agree noexec should be default and maybe a check box, with a warning, to do otherwise.
Can I apply the new ZFS plugin without danger, or will it likely brake something?
The plugin change changes very little - it just adds override file and resets start levels. So, you should be fine.
Can I apply the new ZFS plugin without danger, or will it likely brake something?
For proper reordering you need to force the remove from rcS then update defaults
insserv -r -f zfs-mount and then update-rc.d zfs-mount defaults, verify that the links now appear at rc#
ls -la /etc/rc[2345].d/ | grep zfs-mount
After that you can download the plugin, and install it, this will modify zfs-mount to be now at rcS with an override
Alles anzeigenFor proper reordering you need to force the remove from rcS then update defaults
insserv -r -f zfs-mount and then update-rc.d zfs-mount defaults, verify that the links now appear at rc#
ls -la /etc/rc[2345].d/ | grep zfs-mount
After that you can download the plugin, and install it, this will modify zfs-mount to be now at rcS with an override
Outup okay ?:
root@Openmediavault:/# insserv -r -f zfs-mount
root@Openmediavault:/# update-rc.d zfs-mount defaults
update-rc.d: using dependency based boot sequencing
root@Openmediavault:/# ls -la /etc/rc[2345].d/ | grep zfs-mount
lrwxrwxrwx 1 root root 19 Dez 2 19:44 S01zfs-mount -> ../init.d/zfs-mount
lrwxrwxrwx 1 root root 19 Dez 2 19:44 S01zfs-mount -> ../init.d/zfs-mount
lrwxrwxrwx 1 root root 19 Dez 2 19:44 S01zfs-mount -> ../init.d/zfs-mount
lrwxrwxrwx 1 root root 19 Dez 2 19:44 S01zfs-mount -> ../init.d/zfs-mount
Outup okay ?:
Looks fine for me, reboot now and you should have a delayed zfs-mount. Install the plugin update then reboot and you should have an early zfs mount (it will not get recorded by bootlog though, cause bootlogd starts 2-3 steps after)
Tested and the new plugin version seems to work fine. Now how do we make sure that the users can't make mistakes while installing this (installing omvextras and checking the ZFS checkbox on the secondary page) and also why the plugin isn't displayed in the browser for some users after installation?
I think a lot of the install issues will go away once the plugin is in the repo. The biggest problem seems to be with the kernel headers. They are installed when you check the zfs box. If someone installs the backports kernel after checking the zfs box, the proper headers won't be installed. The only way around that would be to install the headers when installing the backports kernel. I don't have a problem with that but may need to test a few things - mainly installing 3.16 kernel headers while using the 3.2 kernel.
Hello all
I've made several try to install this plugin
I've do a Fresh Install with openmediavault_1.0.20_amd64.iso
wget http://archive.zfsonlinux.org/debian/pool/main/z/zfsonlinux/zfsonlinux_3%7Ewheezy_all.deb
dpkg -i zfsonlinux_3~wheezy_all.deb
apt-get update
apt-get install linux-image-amd64 spl-dkms
apt-get install zfs-dkms debian-zfs
But at this stage, no ZFS menu.
A user report It's OK after a plugin install.
After install of the snapraid plugin, ZFS menu finally showed.
I think there is a problem with the reload/refresh of the menu content ?
Yes, there seems to be some problem with menu refresh after installing the plugin. However the steps you have performed are not the right ones... Please refer to instructions earlier in this thread for guidance. With your current setup you will not have working zfs-omv filesystem integration etc.
Edit: After some consideration it might only be necessary for you to update omv to latest version to get everything working as expected.
I've do a Fresh Install with openmediavault_1.0.20_amd64.iso
I see no step in upgrading OMV, the FS backend for ZFS in that version is not supported, i guess you missed posting the step, but you did it right?
Those are unnecessary steps, specially manually downloading debs, and removing repos like that.
The problem is with the headers and building the modules
I see no step in upgrading OMV, the FS backend for ZFS in that version is not supported, i guess you missed posting the step, but you did it right?
You're right, between OMV install & ZFS, I've installed VMWare Tool (I'm on ESXI 5.5)
To compil vmware tool I've do some upgrade and install
So My OMV version is 1.4
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!