Same "problem" here ...
- Install omv-extras
- Install openmediavault-apttool plugin from Plugins tab.
- Add new repo in omv-extras repo tab using the settings in the attached pic.
Little correction: openmediavault-apttool ist part of the omv-extras testing repository.
On OMV 2.x, you have to use the ID from a public key server. On OMV 3.x, you could enter the url. Since I don't know what the ID is, you only need to add it once with:
wget -qO - "https://dl-ssl.google.com/linux/linux_signing_key.pub" -4 | apt-key add -
In OMV 3.x I have to enter the following (for your example)?!
Thank you! Now the GUI works fine again!
I use the unionfilesystem too.
I made today a reinstall:Code
It doesn't help. Does version 3.1.11 of openmediavault-unionfilesystems realy be in the repository (as mentioned)?
After this Update the "File systems" and the "Union Filesystems" aswell as the "Shared Folders" Tabs dont load anymore. They just say "loading..." until my seasion times out...I tried reseting the UI and restarting the server, both didnt change anything.
The same as here.
You changed two things if I'm reading it right. Setting the use_ino flag and changing the kernel? Are you sure it was use_ino and not the kernel change?
- The first solution is: Using she standard-Kernel (the bpo-Kernel didn't work).
- The second (your) solution is: Using bpo-Kernel and the MergerFS-flag use_ino. So I could now change back to the bpo-Kernel.
Why OMV3.x doesn't use the use_ino as default?
Is it a different version of NFS? I've heard from some people that they had issues with NFSv4 but not v3.
Nope - both was NFSv3. Here a check from my Ubuntu 16.04CodeQuote
Few things to try:
* use the 'use_ino' option for mergerfs
I will test this.
use_ino: causes mergerfs to supply file/directory inodes rather than libfuse. While not a default it is generally recommended it be enabled so that hard linked files share the same inode value.
O.K. - it's recommended to enable. - Proposal: May be you should do this as standard in OMV3.x?!
I had have the fsid option, but it didn't help.
It works also in kodi 17 android (firetv stick), but yes seems like there is no go on this with kodi 16
But why? What is the difference between OMV2.x and OMV3.x?
Debian: wheezy --> jessie - may be there is the problem?
In both OMV-versions I used the bpo-Kernel.
Therefore I "simulate" OMV2.x by using the Standard-Kernel on OMV3.x: SUCCESS!
With Kernel 3.16.0-4-amd64 there was no Problem!
My conclusion: That's more a Debian-Problem (BUG?!), than an OMV issue. Could you verify / agree with this?
I can't connect Android-Kodi(16.1)-Clients (Lollipop and Marshmallow) via NFS to OMV3.x. My NFS-optiones:
I have no problems with this Clients:
- Ubuntu 16.04
- OSMC (Debian with Kodi 16.1 - Pi2)
- LibreElec (Kodi 17.x - odroid C2)
I asked in differnt forens:
and tried different things, but no help was found.
The shares are on snaipraid with MergerFS.
The effect is:
The share is visible, but the content isn't visible.
Under OMV2.x it worked perfect - no problems.
Therefore I ask you as expert:
Does anyone use an Android-Kodi und can connet via NFS to a OMV3.x Server?
I saw just your new edit from today for nfs:
Pooling filesystems (AUFS, MHDFS and MergerFS)
Since this type filesystems don't have a uuid, you need to add fsid=1 or fsid=anynumber
to the nfs extra options, make sure the number is not 0 and unique in
case you're exporting multiple pools. You also need to add the crossmnt option for mergerfs.
openmediavault 3.0 now generates a unique fsid per exported folder by default so you don't need to add it manually.
My new NFS-option line is now: subtree_check,insecure,crossmnt,all_squash,anonuid=1000,anongid=1000
The result is the same:
The share for Android-Kodi(16.1) is visible, but the content isn't visible.