Problem with remote mount plugin

slanbuas · 1. Januar 2018

Hello,

New OMV user here, wondering if the remote mount plugin should be working on OMV4 ?

While the NFS mount is working (I can create files on the share using /srv/{ID} ) once the share is added, I always get the following error : "Could not fetch a matching mount point from the provided fsname: '/srv/{ID}" and filesystem is empty. People seems to have the same problem on 3.0 (github issue).

I'm also realizing that I didn't install a 'stable' version (took the latest iso from sourceforge, maybe it should be noted in there if v4 is still alpha).

Any idea ?

Code

ii  openmediavault                   4.0.15-1                       all          openmediavault - The open network attached storage solution
ii  openmediavault-keyring           1.0                            all          GnuPG archive keys of the OpenMediaVault archive
ii  openmediavault-minidlna          3.3.11                         all          OpenMediaVault miniDLNA (DLNA server) plugin
ii  openmediavault-omvextrasorg      4.1.2                          all          OMV-Extras.org Package Repositories for OpenMediaVault
ii  openmediavault-remotemount       4.0                            all          Remote mount plugin for OpenMediaVault.
ii  openmediavault-snapraid          3.7.3                          all          snapraid plugin for OpenMediaVault.
ii  openmediavault-symlinks          3.1.3                          all          OpenMediaVault symlinks plugin
ii  openmediavault-unionfilesystems  4.0                            all          Union filesystems plugin for OpenMediaVault.

Code

Stack trace:
#0 /usr/share/php/openmediavault/system/filesystem/backend/remoteabstract.inc(139): OMV\System\Filesystem\Backend\RemoteAbstract::fetchMountPointFromFstabByFsnameAndType('/srv/354b40b6-5...', 'nfs')
#1 /usr/share/php/openmediavault/system/filesystem/filesystem.inc(805): OMV\System\Filesystem\Backend\RemoteAbstract->getImpl('/srv/354b40b6-5...')
#2 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(67): OMV\System\Filesystem\Filesystem::getFilesystems()
#3 [internal function]: OMVRpcServiceFileSystemMgmt->enumerateFilesystems(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('enumerateFilesy...', Array, Array)
#6 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('FileSystemMgmt', 'enumerateFilesy...', Array, Array, 1)
#7 {main}

ryecoaaron · 1. Januar 2018

The only difference between the 3.x and 4.x versions of the remote mount plugin is the use of php7 in 4.x.

The plugin is working for me. Most of the time, the problem is permissions and/or a wrong setting. Does the share name have a space in it? Can you post a screenshot of the remotemount settings?

slanbuas · 1. Januar 2018

There is no space in the share name. Here is the configuration :

10.0.0.x is an internal network between the VM and the host.

Is line 4 normal?

Code

root@omv:/srv/354b40b6-5622-483c-95da-5e73901ff52a# mount | grep test


10.0.0.1:/rpool/test on /srv/354b40b6-5622-483c-95da-5e73901ff52a type nfs4 (rw,relatime,vers=4.2,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=14,retrans=2,sec=sys,clientaddr=10.0.0.2,local_lock=none,addr=10.0.0.1)
/dev/vda1 on /sharedfolders/rpool-test type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)

Code

root@omv:/srv/354b40b6-5622-483c-95da-5e73901ff52a# pwd
/srv/354b40b6-5622-483c-95da-5e73901ff52a
root@omv:/srv/354b40b6-5622-483c-95da-5e73901ff52a# touch foo
root@omv:/srv/354b40b6-5622-483c-95da-5e73901ff52a# ls -la
total 5
drwxrwxr-x 2 root root    3 Jan  1 15:26 .
drwxr-xr-x 7 root root 4096 Jan  1 10:48 ..
-rw-rw-rw- 1 root root    0 Jan  1 15:26 foo

I can confirm that the mount is good, since 'foo' is visible from the nfs server

ryecoaaron · 2. Januar 2018

Zitat von slanbuas

Is line 4 normal?

Yes on OMV 4.x.

That looks ok to me. Where are you getting the fsname error?

slanbuas · 2. Januar 2018

I only get the error when accessing Storage / File system. After the errors the other filesystems are no longer visibles.

Otherwise, the only other error I can see is in the syslog and doesn't seem related:

Jan 1 20:48:47 omv monit[668]: 'omv' mem usage of 2147250208768.0% matches resource limit [mem usage>90.0%]

Jetzt mitmachen!