Mount FTP via curlftpfs

crisp2u · 24. März 2019

Hi Guys,

Any idea how I can manually add a mounting point for a remote FTP using curlftpfs ?

I'm planning to use a remote FTP for backup and I decided to use curlftpfs to mount it. I tested mounting it via the fstab but being a manual entry is not recognized by OMV.
Since the remotemount plugin does not support curlftpfs at this moment I decided to try to add the new entry manually in the config.xml
I think because the fuse type is not supported I end up with errors like
Could not fetch a matching mount point from the provided fsname
or
Couldn't extract an UUID from the provided path
which seem to come from the mergefs implementation (mergerfs.inc)
I tried all the combinations with no luck.
The intended line in fstab is

curlftpfs#ftp.server.com/folder /mnt/ftp fuse rw,relatime,user_id=0,group_id=0,allow_other 0 0

Bellow are some of my variations of the config.xml entry)

XML

<mntent>
        <uuid>4f4a020d-5f7a-4380-9b9d-185b9c18aab9</uuid>
        <fsname>curlftpfs#ftp.server.com/folder/</fsname>
        <dir>/mnt/ftp</dir>
        <type>fuse</type>
        <opts>_netdev,x-systemd.automount,allow_other,ssl_control</opts>
        <freq>0</freq>
        <passno>0</passno>
        <hidden>0</hidden>
      </mntent>


      <mntent>
        <uuid>4f4a020d-5f7a-4380-9b9d-185b9c18aab9</uuid>
        <fsname>curlftpfs#ftp.server.com/folder/</fsname>
        <dir>/mnt/ftp</dir>
        <type>fuse</type>
        <opts>_netdev,x-systemd.automount,allow_other,ssl_control</opts>
        <freq>0</freq>
        <passno>0</passno>
        <hidden>0</hidden>
      </mntent>




      <mntent>
        <uuid>4f4a020d-5f7a-4380-9b9d-185b9c18aab9</uuid>
        <fsname>curlftpfs#ftp.server.com/folder/</fsname>
        <dir>/srv/ftp</dir>
        <type>fuse</type>
        <opts>_netdev,x-systemd.automount,allow_other,ssl_control,fsname=ftp</opts>
        <freq>0</freq>
        <passno>0</passno>
        <hidden>0</hidden>
      </mntent>




      <mntent>
        <uuid>4f4a020d-5f7a-4380-9b9d-185b9c18aab9</uuid>
        <fsname>curlftpfs#ftp.server.com/folder/</fsname>
        <dir>/srv/ftp</dir>
        <type>fuse</type>
        <opts>_netdev,x-systemd.automount,allow_other,ssl_control,fsname=ftp:/srv/ftp</opts>
        <freq>0</freq>
        <passno>0</passno>
        <hidden>0</hidden>
      </mntent>

Alles anzeigen

gderf · 24. März 2019

You don't need to make an entry in config.xml to add a line to fstab. Just add it to fstab yourself outside of the [openmediavault] section.

crisp2u · 24. März 2019

I know that, but then I can't see that entry in filesystems in OMV and use it

tkaiser · 24. März 2019

Zitat von crisp2u

I'm planning to use a remote FTP for backup

Somewhere on the Internet? Without a VPN?

crisp2u · 25. März 2019

Yes, kind of, my ISP provides also a storage service and also has the option of connecting via FTP and FTPS.

Not sure how a VPN will change the way I connect to it.

Set aside the security concerns, I was hoping to some pointers if this is even possible, I'm quite stubborn and spend a few hours on this, usually I don't know when to quit.

noxcivi · 26. Mai 2021

This thread is still high ranking for the search of curlftpfs & openmediavault. I found a (quirky) solution to the problem and I thought it'd be good to share it.

To get OMV to creating a working entry in fstab I made use of the remotemount-plugin and omv-salt. Like crisp2u posted in their opening post, we want a line like:

curlftpfs#ftp://server.local/share/ /srv/$ftpshareUUID fuse _netdev,(rw/ro),uid=$ID,allow_other,ssl,no_verify_hostname,no_verify_peer,user=/root/.ftpshare_credentials 0 0

Never should the credentials for the ftp-share be put directly into the options! Better: a file only accessable by root:

Code: /root/.ftpshare_credentials

username:password

HowTo: Get omv-salt deploy run fstab to create the entry.

1. Modify 4 files of the remotemount-plugin to make it accept fuse

Code: /srv/salt/omv/deploy/fstab/90remotemount.sls

{% set config = salt['omv_conf.get']('conf.service.remotemount') %}
[...]
{% set mount = True %}
{% set options = [] %}
{% set options = mnt.options.split(',') %}
{%- if mnt.mounttype == 'cifs' %}
[...]
{%- elif mnt.mounttype == 'fuse' %}
{% set share = 'curlftpfs#' + mnt.server + mnt.sharename %}
{% set fstype = mnt.mounttype %}
{%- endif %}

create_remotemount_mountpoint_{{ mnt.uuid }}:
[...]

Alles anzeigen

Code: /usr/share/openmediavault/datamodels/rpc.remotemount.json

[...]
"mounttype": {
                "type": "string",
                "enum": ["cifs","ftpfs","nfs","fuse.glusterfs","9p","davfs","fuse"],
                "required": true
            },
[...]

Code: datamodels/conf.service.remotemount.json + datamodels/conf.service.remotemount.mount.json

[...]
"mounttype": {
            "description": "The type of remote mount",
            "type": "string",
            "enum": ["cifs","nfs","davfs"]
        },
[...]

2. Edit the OMV config file

Code: /etc/openmediavault/config.xml

[...]
    <fstab>
     <mntent>
        <uuid>$mntentrefID</uuid>
        <fsname>$ftpshareUUID</fsname>
        <dir>/srv/$ftpshareUUID</dir>
        <type>fuse</type>
        <opts></opts>
        <freq>0</freq>
        <passno>0</passno>
        <hidden>1</hidden>
      </mntent>
    </fstab>
[...]
    <remotemount>
      <mount>
        <uuid>$ftpshareUUID</uuid>
        <name>ftpshare</name>
        <mntentref>$mntentrefID</mntentref>
        <mounttype>fuse</mounttype>
        <server>ftp://server.local/</server>
        <sharename>share/</sharename>
        <nfs4>0</nfs4>
        <options>_netdev,ro,uid=1000,allow_other,ssl,no_verify_hostname,no_verify_peer,user=/root/.ftpshare_credentials</options>
      </mount>
    </remotemount>
[...]

Alles anzeigen

Now, omv-salt deploy run fstab will do its job and add the share to omv's database. After a monit restart omv-engined it should appear in the web interface in "File Systems" and "Remote Mount".

From this point on, I could leave the shell. Creation of "Shared Folders" for the ftpshare was possible within the omv web interface.

The solution is anything but perfect. The changes to remotemount's files need to be merged everytime the plugin gets updated and the solution might stop working at all if incompatible changes are made to OMV's core components.

For my no_internet_pure_local-NAS this is easily managed, as it cannot update itself. For others this might be a no-no.

Jetzt mitmachen!