Multiple NFS mounts from ESXi

[wjscott]

Environement: QNAP TS459 Pro, using both interfaces to connect to Gigabit Switch, with ESXi 3.5 Update 3 clients.

First Problem...I have created two shares on QNAP...one called "nfs", one called "distro". The idea to place ISO's into "distro" and VM's into "nfs". On ESX side, I have created two datastores...qnap1_nfs and qnap1_distro...at one point it was working as expected. I added a third share called "backups", and on ESXI, a corresponding datastore called qnap1_backups. Once I did this, all the datatores now open the same network share. In other works...no matter which datastore you open on ESXi, it opens the same "backups" share...so i can no longer access "distro" or "nfs". So I deleted the "backups" share...now all the datastores open the "distro" share. Looks to me like QNAP is not correctly creating the /etc/exports file.

I'm using QNAP TS-459 Pro. There is one minor firmware update I have not installed, because its no longer available on the QNAP site for download. (Say's wait until Monday...geesh guys...many of us work more than M-F).

If i delelete the "backups" share, and recreate the qnap1_nfs datastore, it works. As soon as i add the backups share, its broke again. I do not have this issue with my other NFS servers. Has anybody else seen this issue?

Second problem...My QNAP is on a private non-routable network. There is no internet and no DNS on this network. I can not NFS mount from ESXi unless I ssh into the qnap, and add the ESXi hostand ip to the /etc/hosts file. However, upon reboot, the hosts file got restored to the default and i lost my changes. I can not figure out how to make the changes in the GUI...Suggestions???

[schumaku]

Hi,

Looks to me like QNAP is not correctly creating the /etc/exports file.

Really? We run a bunch of nfs shares, no such issue in sight - mounted on various U**x systems, but not from ESXi systems. Please check if the shares point to the appropriate directory in /etc/smb.conf and if this matches:

[~] # cat /etc/smb.conf | grep path
path = /share/MD0_DATA/share11
path = /share/MD0_DATA/share12
...
[~] # cat /etc/exports
"/share/MD0_DATA/share11 *(rw,async,no_root_squash,fsid=13)
"/share/MD0_DATA/share12" *(rw,async,no_root_squash,fsid=14)
...

Second problem...My QNAP is on a private non-routable network. There is no internet and no DNS on this network. I can not NFS mount from ESXi unless I ssh into the qnap, and add the ESXi hostand ip to the /etc/hosts file. ...[/quote] Ok, I'm a lazy admin but prefer to have a manageable and monitored systems, so we ensure some well controlled and restricted access into (Web admin, SNMP) and from the storage networks (DNS, SNMP traps, smtp, e.g. for notification). If this is out of scope, check http://wiki.qnap.com/wiki/Autorun.sh and drop in the required lines to /etc/hosts

-Kurt.

[SebastianHarnau]

Same Problem here. Using 809RP with vSphere4 cluster and 5 NFS-Shares the first share showed contents of one of the shares i created later...
I deleted the new NFS-shares and now it works and VMs can access their storages...

I hope this issue can be fixed via firmware update soon.