Beiträge von m.hajoo

Hi subzero79,

thank you for your answer.

First,
yes, smb works correctly from explorer; with windows10 clients and Linux Client (Mint).

Zitat von subzero79

Use the terminal command line to mount nfs.

what does it mean,
on client or Server (OMV5) ?

I added this Line in /etc/exports on OMV5 = Server

/srv/dev-disk-by-label-DATA/NFS 192.168.254.0/24(rw,root_squash,no_subtree_check,sync,fsid=0)

cause Ubuntu wiki says

<pseudo-dateisystem> <rechneradresse>(<optionen>,fsid=0)

then

root@debian:/# service nfs-kernel-server reload

Perhaps important to know,

Media is a directory

NFS is a link for Media

 showmount -e on OMV5

root@debian:/# showmount -e
Export list for debian.BROADWAY:
/export                           (everyone)
/srv/dev-disk-by-label-DATA/Media 192.168.254.0/24
/export/Media                     192.168.254.0/24
/export/NFS                       192.168.254.0/24
root@debian:/#

afterwards on Linux Client (LinuxMint)

showmount -e 192.168.254.202 192.168.254.202=OMV5

markus@lmde4:~$ showmount -e 192.168.254.202
Export list for 192.168.254.202:
/export                           (everyone)
/srv/dev-disk-by-label-DATA/Media 192.168.254.0/24
/export/Media                     192.168.254.0/24
/export/NFS                       192.168.254.0/24
markus@lmde4:~$

on command line Linux Client (LinuxMint)

sudo mount -t nfs -o nfsvers=4 192.168.254.202:/export/NFS /mnt/NFS-Test/

vist the mount points on Client

cd /mnt

markus@lmde4:/mnt$ ls -l
insgesamt 8
drwxr-xr-x  2 root root  4096 Mär 31 14:01 Media
drwxrwsrwx+ 8 root users 4096 Mär 31 18:21 NFS-Test
markus@lmde4:/mnt$

Access in explorer for the mountet export NFS works with the correct permissons.

Same with the share Media.

Works correctly.

But,

... the entries in /etc/fstab don't work.

# UNCONFIGURED FSTAB FOR BASE SYSTEM
proc    /proc    proc    defaults    0    0
# /dev/sda2
UUID=03371ac1-b0f9-4cbd-9ecf-689eec54974d /  ext4 defaults 0 1
# /dev/sda1
UUID=cefbc7e7-d0fc-45d4-9d4e-8f97f1868498 none   swap sw 0 0

192.168.254.202:/export/NFS /mnt/NFS-Test/ nfs -o nfsvers=4,rwoft,bg,intr,users 0 0
192.168.254.202:/srv/dev-disk-by-label-DATA/NFS /mnt/NFS-Test/ nfs -o nfsvers=4,rwoft,bg,intr,users 0 0

Share is not connected.

manually on command line

sudo mount -t nfs -o nfsvers=4 192.168.254.202:/export/NFS /mnt/NFS-Test/

works

On the other client, (Debian-9-turnkey-mediaserver_15.1-1)

nothing works.

neither commands in terminal, nor the command in webmin.

Everytime the same Message:

Fehler beim Speichern des Mounts : NFS-Fehler - mount.nfs4: access denied by server while mounting 192.168.254.202:/mnt/NFS 

Don´t know what to do.

I´ve changed the parameters, Shares, etc.

Nothing works.

Thank you for help

Hello everybody,

Corona makes it possible and I take care of my IT landscape again.

I broke my ESXI with OMV4 and zfs.

Instead, a proxmox-pve with zfs and various VMs is running here.

So far so good.

I installed Debian10.3 in a VM and installed OMV5.

SMB / CIFS shares work.

What I can't do is set up NFS shares for a MediaServer.

Here's how I did it:

- I set up NFS shares via OMV WebUI.

- these are shown in '/ etc / exports'.

.root@debian:/export# ls -l.
total 8
drwxrwsrwx+ 7 root users 4096 Mar 30 20:24 Media
drwxrwsrwx+ 7 root users 4096 Mar 30 20:24 NFS

- ein showmount -e localhost bringt

Export list for localhost:
/export/Media *
/export       (everyone)
/export/NFS   192.168.254.0/24

On this client (for testing)

- showmount -e 192.168.254.202 (192.168.254.202 = OMV5) brings:

The releases are visible.

A connection to the NFS shares is not possible:

on the other client (here with Webmin)

the NFS shares are also visible

Failed to save mount: NFS error  - mount.nfs: access denied by server while mounting 192.168.254.202:/export/NFS 
Failed to save mount: NFS error  - mount.nfs: access denied by server while mounting 192.168.254.202:/export/Media
Failed to save mount: NFS error  - mount.nfs: access denied by server while mounting 192.168.254.202:/export
Failed to save mount: NFS error  - mount.nfs: access denied by server while mounting 192.168.254.202:/NFS
Failed to save mount: NFS error  - mount.nfs: access denied by server while mounting 192.168.254.202:/Media 

however, a connection is not possible here either.

on OMV

root@debian:/export# omv-salt deploy run nfs
debian.BROADWAY:
----------
          ID: configure_default_nfs-kernel-server
    Function: file.managed
        Name: /etc/default/nfs-kernel-server
      Result: True
     Comment: File /etc/default/nfs-kernel-server is in the correct state
     Started: 02:16:09.845273
    Duration: 21.159 ms
     Changes:
----------
          ID: configure_nfsd_exports
    Function: file.managed
        Name: /etc/exports
      Result: True
     Comment: File /etc/exports is in the correct state
     Started: 02:16:09.866536
    Duration: 27.352 ms
     Changes:
----------
          ID: start_rpc_statd_service
    Function: service.running
        Name: rpc-statd
      Result: True
     Comment: The service rpc-statd is already running
     Started: 02:16:09.899521
    Duration: 24.517 ms
     Changes:
----------
          ID: start_nfs_kernel_server_service
    Function: service.running
        Name: nfs-kernel-server
      Result: True
     Comment: The service nfs-kernel-server is already running
     Started: 02:16:09.924913
    Duration: 19.634 ms
     Changes:

Summary for debian.BROADWAY
------------
Succeeded: 4
Failed:    0
------------
Total states run:     4
Total run time:  92.662 ms
root@debian:/export#

root@debian:/export# omv-confdbadm read --prettify conf.service.nfs
{
    "enable": true,
    "shares": {
        "share": [
            {
                "client": "192.168.254.0/24",
                "comment": "NFS-Share",
                "extraoptions": "subtree_check,insecure",
                "mntentref": "6770599c-46f0-40a0-b1ca-810ef7715c90",
                "options": "rw",
                "sharedfolderref": "00dabb98-0a12-474a-b851-145fbb02e381",
                "uuid": "b55b9b18-2316-4b39-9c1e-c56b1d3a1500"
            },
            {
                "client": "",
                "comment": "",
                "extraoptions": "subtree_check,insecure",
                "mntentref": "9c0ae057-0ea7-4f71-8c10-307485cf4f84",
                "options": "rw",
                "sharedfolderref": "04ea4ee9-1e9a-412c-a48f-e4d0122d81b4",
                "uuid": "68b4522e-acce-40f6-8030-9e69219d299f"
            }
        ]
    }
}
root@debian:/export#

/etc/export:

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
/export/NFS 192.168.254.0/24(fsid=1,rw,subtree_check,insecure)
/export/Media (fsid=2,rw,subtree_check,insecure)

# NFSv4 - pseudo filesystem root
/export 192.168.254.0/24(ro,fsid=0,root_squash,no_subtree_check,hide)
/export (ro,fsid=0,root_squash,no_subtree_check,hide)

have no idea why I cannot connect via NFS.

It worked smoothly on my previous system with OMV3 and later OMV4.

So I connected the ESXI to the Raidz2 from OMV,

the plates were passed from ESXI through passtrough to OMV.

Would be nice if someone here could help me with my problem.

PS . my native language is German,

.... text above ... thank you google

Hello everyone who´s interested in this problem, ....

... but it seems to me that the problem is solved.

I didn´t restart the vitual omv-machine since november.
Today I updated omv from version 2.1.19 to 2.1.23.
Afterwards i restartet the system a few times, ...
... and /export/Images is not empty after reboot
the nfs-share is working well.

I can see it on the console of the vm on my ESXi.
When the vitualmachine of omv is rebooting,
the other vm´s
stored on the mapped nfs-folder of ovm,
are "coming back" .

Sorry that I cannot localize the problem, but I´m glad that it will work now.

Kind regards,
and a happy new year
to everyone here by openmediavault

m.hajoo

hello ikogan,
hello nicjo814,

thank you for your answers and your suggestions.

I´m not at home these days, so I can´t check it out on my system.

When I´m back I´ll test as soon as possible the promises you made.
Then I´ll info you, if something has changed.

Thanks,
m.hajoo

ich habe hier im Forum weiter gesucht und auch getestet,
hat aber bisher leider keine Änderungen gebracht.

Zitat von subzero79

Thread/10397-NFS-was-working-but-not-with-stone-burner

Please post

 mount | grep export

 pool_01 on /export/Images type zfs (rw,relatime,xattr,noacl) 

Zitat

 exportfs -v 

 /export/Images 192.168.254.201(rw,wdelay,root_squash)
 /export 192.168.254.201(ro,wdelay,root_squash,no_subtree_check,fsid=0) 

Zitat

 cat /etc/debian_version 

 7.9 

Das erscheint mir in meinem Fall unnötig,

Zitat von subzero79

run omv-mkconf fstab then mount -a check again in your clients the export mount

da  mount | grep export
 pool_01 on /export/Images type zfs (rw,relatime,xattr,noacl) 

Zitat von /etc/fstab

Code

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=d0eba2d1-86e8-4993-ac59-73e2a3032654 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=1784b276-1b21-44b3-8a87-5b6a01f7e958 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
# >>> [openmediavault]
/pool_01/Images /export/Images none bind 0 0
# <<< [openmediavault]

Alles anzeigen

Hallo zusammen,

dies sind meine ersten Schritte mit OMV.
Soweit habe ich mein gewünschtes Szenario installiert und konfiguriert bekommen (OMV + ZFS).

Mit der NFS-Freigabe die auf ein Verzeichnis im Pool des ZFS verweist, habe ich die gleichen Problem wie ... "7smugglers"

Nach dem Erstellen der Freigabe "Images" kann ich mit meinem ESXi auf die Freigabe "/export/Images" zugreifen und diese als Datastore einrichten.

Nach einem Reboot der VM OMV ist die Freigabe im Web-Gui vorhanden, auch der NFS-Dienst ist aktiviert und läuft.
Die NFS-Freigabe allerdings ist für den ESXi nicht mehr erreichbar.
Kontrolliert man im OMV das Exportverzeichnis mittels der Kommandzeile, ist das Verzeichnis /export/Images ebenfalls vorhanden, der Inhalt allerdings leer.

Erst nach einem Löschen und erneutem Erstellen der Freigabe kann auf diese wieder zugegriffen werden.

Mir stellt sich nun die Frage,
habe ich etwas falsch/nicht konfiguriert,
verstehe ich die Zusammenhänge nicht richtig,
oder ist dies hier ein generelles Fehlverhalten von OMV.

PS.
im Syslog habe ich folgendes gefunden...

Zitat

Nov 29 17:17:07 openmediavault rrdcached[3146]: starting shutdown
Nov 29 17:17:07 openmediavault avahi-daemon[3426]: avahi-daemon 0.6.31 exiting.
Nov 29 17:17:08 openmediavault zed[3610]: Exiting
Nov 29 17:17:08 openmediavault rpc.mountd[4515]: Caught signal 15, un-registering and exiting.

Nov 29 17:17:08 openmediavault kernel: [ 752.374333] [b]nfsd: last server has exited, flushing export cache[/b]

Nov 29 17:17:08 openmediavault rrdcached[3146]: clean shutdown; all RRDs flushed
Nov 29 17:17:08 openmediavault rrdcached[3146]: removing journals

Alles anzeigen

... falls hier wirklich beim reboot der export cache gelöscht wurde,
wäre der Fehler ja bei OMV zu suchen.

Hat jemand eine Idee wo man hier ansetzen kann?

Hintergrund:
Die NFS-Freigabe vom OMV ist für mich essentiell, da mein ESXi hier seine weiteren VMs hosten soll.

Danke vorab für Eure Anregungen und Tipps.

Gruß,
m.hajoo