That was it! .mntcheck was missing from /images/dev. Thank you!

All I can go on is it says Mounted NFS Volume - Done as it boots up.

I tried running the mount command in the shell as you suggested, it worked fine and I was able to view the contents of the /images/dev directory and open a file and delete a file from the client.

I dropped the fog db and reinstalled and the DefaultMember configuration looks exactly the same as before, and same errors - It mounts the NFS volume, then says it isn’t mounted.

I tried to put it back to how it was but if you can tell I touched it obviously did something wrong - what should it look like?

I was mistaken, it is creating entries in journalctl when the client connects to the server

Jul 17 11:39:46 localhost rpc.mountd[2506]: authenticated mount request from 10.0.0.141:939 for /images/dev (/images/dev)
Jul 17 11:39:29 localhost in.tftpd[29884]: tftp: client does not accept options
Jul 17 11:39:29 localhost xinetd[994]: START: tftp pid=29883 from=10.0.0.141

Of course, see below:
[ATTACH=full]1174[/ATTACH]

[url=“/_imported_xf_attachments/1/1174_fogstoragenode.png?:”]fogstoragenode.png[/url]

Contents of /etc/exports

/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure,fsid=1,)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure,fsid=2,)
/mnt/isos *(rw,no_root_squash)

The 3rd export isn’t for Fog. All 3 of the exports work just fine for anything other than the Fog clients - I tried an OptiPlex 345 and a ESXi 5.1 Virtual machine for the Fog image and both of them failed exactly the same way.

CentOS 6.5 system connecting to the NFS export -

[root@localhost /]# mount 10.0.0.36:/images /mnt/images
[root@localhost /]# cd /mnt/images
[root@localhost images]# ls
dev lost+found

A log entry is created in journalctl when I connect this way, and a log entry is also created if I try to connect to a directory that isn’t exported. There are no log entries at all when Fog tries to connect and the directory is properly exported, but if I remove the export I get an error that the directory isn’t exported.

I’ve used Fog before, but this is the first time I’ve tried the new version. It’s much prettier, I like it so far.

I’m having a very hard time getting any image to upload to the server. It looks like it’s going to work, then it fails out.

The host operating system is CentOS 7, and I can mount the NFS export just fine from the computer and read and write data to it, and a log is stored in journalctl of the event. When Fog mounts the volume, it doesn’t store -anything- in the log (As though it made no access attempt) and it fails out even though it says it mounted.

I tried breaking it a bit by removing the export, and that failed as you would expect and put an entry in journalctl, but when it’s set properly it’s like something is getting missed.

[ATTACH=full]1172[/ATTACH]

[url=“/_imported_xf_attachments/1/1172_Untitled.png?:”]Untitled.png[/url]

I quick Google search for “Throttle Linux network connection” came up with this result - even if Fog can’t throttle, if you can slow down the speed of the server’s NIC it should accomplish the same result. You also might ask whoever the network is outsourced to if some form of QoS can be setup (so it can run at full speed unless someone else needs it).
[url]http://superuser.com/questions/66574/how-to-throttle-bandwidth-on-a-linux-network-interface[/url]

Actually it was pretty straightforward to get working on FC17 -

1. Follow instructions found in other posts for Fedora Core 16 (Remove php-gettext from the install file, fix the NFS-server start so it won’t break the install process)
2. Replace &$tmp with $tmp
3. Start the NFS-server / enable the nfs-server

I just successfully re-imaged a computer