Problem with external NFS on OpenMediaVault

[giolnl]

@ch3i
my export file on the FOG server looks like yours, some things I already tried:

• set the same options i found in the FOG server’s export to the OMV’s export and change/mess a bit with them
• use two separate exports for images and images/dev (always in OMV) with the exact options found in FOG (so something almost identical to the setup of the FOG server)

The storage configuration is the same i posted before: screenshot, where 10.21.100.29 is the OMV server

[Wayne Workman]

@giolnl said:

the FOG server looks like yours, some things I already tried:

You need an NFS Export for both the /images directory and the /images/dev directories - wherever those may be. For troubleshooting purposes, set world-writable permissions (777) on the /images directory just to see it get going without unnecessary complications.

[Sebastian Roth]

@giolnl I guess your /etc/exports on OMV should look like this:

/export/backup 10.21.0.0/16(rw,subtree_check,secure)
/export/images (rw,subtree_check,secure)
/export/images/dev (rw,subtree_check,secure)

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

Maybe even add the NFS parameters originally used by FOG (see ch3i’s post).

[Wayne Workman]

@Uncle-Frank I’d highly recommend that.

[giolnl]

@Uncle-Frank
I’ve just tested it with no success

EDIT: I noticed a new thing, all the other tests I’ve done I’ve always set the task from the web GUI and then start the client with PXE, this time I just started the client without any task pending and then tried to do a quick image and now I can see this error in the Image list in the GUI under “image size: ON SERVER”, don’t know if it can be usefull or not:

FOGFTP: Failed to connect. Host: 10.21.100.29, Error: Undefined property: FOGFTP::$link

END EDIT

/etc/exports on OMV:

# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
/export/backup 10.21.0.0/16(rw,subtree_check,secure)
/export/images (rw,subtree_check,secure)
/export/dev (rw,subtree_check,secure)

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

Same errors:

Sep 30 05:48:43 omv rpc.mountd[18040]: refused mount request from 10.21.1.20 for /images/ (/): not exported

and permission denied on the client

root@omv:~# ll -aR /export/images/
/export/images/:
total 12
drwxrwxrwx+ 3 root   users   32 Jul 30 17:10 .
drwxr-xr-x  5 root   root  4096 Sep 30 08:35 ..
-rwxrwxrwx+ 1 nobody users    0 Jul 30 17:10 .mntcheck
drwxrwsrwx+ 2 nobody users   22 Jul 30 17:10 dev

/export/images/dev:
total 8
drwxrwsrwx+ 2 nobody users 22 Jul 30 17:10 .
drwxrwxrwx+ 3 root   users 32 Jul 30 17:10 ..
-rwxrwxrwx+ 1 nobody users  0 Jul 30 17:10 .mntcheck

[Sebastian Roth]

/export/images/dev not /export/dev I reckon

[Wayne Workman]

# /export/backup 10.21.0.0/16(rw,subtree_check,secure)
#Commented out the above line just for troubleshooting purposes.
/export/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/export/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

[giolnl]

@Uncle-Frank
The fact is that OMV doesn’t le me export “directly” a subdirectory, it let me create a shared folder which point to /export/images/dev/ but then it exports it as /export/dev/ which is linked somehow to /export/images/dev/ (I don’t know how to be honest),
Anyway I made some tests with a “forced” configuration (meaning I actually bypassed the GUI of OMV) and everything worked, so the problem is in the OMV configuration, I’m still doing some tests but i think the problem is related to some ACL you can set on those shared folders and theirs subdirectories.

I’ll be back when I’ll be sure to have a working “minimal” configuraton for both FOG and OMV.

Thanks anyone for pointing me to the right direction!

[giolnl]

Guess I was wrong about the ACL, in the end what made the difference was the fact that during the “forced” tests I used “/export/images” as image path in the storage configuration instead of “/images” (because of the missing “/export” lines in /etc/exports)

Here some screenshots with the working configuration I’m actually using:

OMV Shared folder configuration

OMV Shared folder ACL configuration

OMV NFS shares

FOG Storage configuration

The actual /etc/exports file on OMV:

# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
/export/images (rw,subtree_check,secure)
/export/backup (rw,subtree_check,secure)

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

Could be that NSFv4 pseudo fs to cause the problem? Maybe by giving FOG the full path I somehow bypass it, just a random guess tho, I don’t know how NFS works apart from the basics.

[Sebastian Roth]

With /export/images/dev missing in /etc/exports is it working now??

[giolnl]

@Uncle-Frank
yes, I already noticed that during the previous tests I’ve made, I was always able to mount /export/images/dev like if it was an export even if it wasn’t configured as one in the OMV server. I guessed it somehow inherited the possibility to be exported by its parents directories, but as I said I’m far from being an expert about NFS.

[Sebastian Roth]

Should we mark this solved or is it still an issue for you?

[giolnl]

I got it working so for me it could be marked as solved, thanks!

[Wayne Workman]

@giolnl said:

I made some tests with a “forced” configuration (meaning I actually bypassed the GUI of OMV) and everything worked

Not forced, simply a manual configuration.

The OS doesn’t care what the GUI says. The OS is going to read the /etc/exports file for exports, that’s how it works.