ESXi 6 NFS Datastore APD

We would not use Windows NFS to start with!

Once the NFS server is back online, normal NFS NAS it will automatically re-connect, as NFS polls.

NFS on Windows is available ? you have checked by connecting to it, with another server/device/workstation/client ?

can you unmount it , and re-mount it from an ESXi host ?

if you issue a refresh/re-scan, what does the log state ?

I cannot unmount and already tried a rescan not luck... Vmware says my only option is a reboot which I think is  B.S answser

host logs ?

what is the error ?

Yes it is the ESXi host logs.. When I right click on the datastore everything is grayed out and I do not have the option to unmounted ....

And yes the NFS share is online and accessible...

do you get any errors in the logs ? why it cannot mount ?

OK I think I am on to something.. I have comfirmed that a reboot does bring the NFS share back online.

I was able to unmounts the NFS datastore then set it up again via Add Storage and it worked..

How can I script the unmounts of this datastore on all host then remount it.

HOw when I tried to manually unmounts the datastore from other host it states it cannont because the device is in use

Some VM are set to boot to specific ISO also I am not able to unmount the host log file since this is listed on each VM...

So it looks Like I will need to removed the mapping from all host and VM then try this... When 40 host and 120 Vm this is going to take a while

Here is what I am seeing in the VM kernel log for the NFS share the host the ESXi log files..

2016-10-03T23:11:49.337Z cpu29:9043435 opID=91b4f7c0)WARNING: NFS: 2208: Failed to get attributes (No connection)
2016-10-03T23:11:49.337Z cpu29:9043435 opID=91b4f7c0)NFS: 2264: Failed to get object 40 28b45cbd fa14778d 2a 10000 2a 10000 34d4aa4c 320b50 c0432038c5c48b5f 0 0 0 :No connection

ah, well datastore's in use, is anothe issue, isos, or Heartbeat datastores, VMware HA, but you also stated that this is your LOG mount.

and that cannot be changed without a reboot!

Don't think you've got much choice, because this is your LOG datastore.

But NFS should re-connect, but then this is Windoze!

If a VM has a datastore mounted it will not be able to be removed I presume. I tried change the log location on three host restarting the management services and still no go...

I feel like I am so close here

Restarting management agents is not going to cure the log location.

It only takes effect after a restart.

If a VM has a datatore mounted it's  busy!

and to be honest with you if you have to start kill (ing) all the services on a host which has production VMs in place, I would no longer be confident in it's production status!

Ugh... I was able to address my ISO mount location but the log location is my last hurdle. I do not recall have to reboot the host to setup the remote log location so why now???

on a test host running our dev VM's I try to stop and start the syslog service and now not able to.. how would I force kill it an restart it

Well I called VMware support and they did find one way to get around this issue for me without having to reboot all of my host. It was to kill the PID of the syslog service.

This whole issue have been an eye opener 1) I showed we how weak I am in Powercli since I had to connect to each host kill this process the reconnect the NFS share. 2) I have rebooted my NFS server before but it has never been down for as long as it was before so I need to research the NFS heartbeat keep alive settings..

In short I still have so much for to learn.... :o)