Troubleshooting a NFS data store

Similar Questions

• Unable to read / write in the NFS data store

  Hi all
  I'm having a problem with a NFS datastore in Vcenter. I have an NFS share on a Win2k3 server which I am able to mount. However... I can't write him even though the permissions appear to be correct.  This server is connected to an array of training Vault EVA Storage with 2 TB of storage.
  Looks like he's not more as when I try to mount ad content, it shows as 0.00 B ability... and I know that there are files in the NFS data store. Same Host, I can mount my other NFS datastore successfully since a 2008 Server, just do not know which cannot be configured correctly here.

  Help, please... been at this for 2 days banging my head on my desk!

  Screenshots are attached. If there are log files that I could post that would help, please let me know and I'll join them as well.
  Thank you!

  Woot! It worked. I changed the local article, but then authorized security strategy anonymous access with the 2 GID and UID - 2. Once this is done, it is now properly show in Vcenter and allow me to read and write in the data store. Before that I got the value 0.0 even with security policy, change that did not work. So I hope that this issue helps someone in the future, and they do not have a hair pulling experience like I did.

  WHAT A PAIN!

  in any case, thank you all for your time.

• Impossible to mount any NFS data store: unable to resolve host name '< obsolete Server > '.

  Hello

  On a particular ESXi server, whenever I try to mount any NFS data store, I get this error message:

  Call "HostDatastoreSystem.CreateNasDatastore" of object "ha-datastoresystem" on ESXi '172.22.216.64' failed.
  Operation failed, the diagnostic report: unable to resolve host name 'cosmo '.

  Always mention hostname 'cosmo', no matter what server I'm actually trying to mount. 172.22.216.64 is the exact address of the ESXi server.

  'cosmo' was the former name of a desktop linux machine, several months ago has re-installed and renamed in the process. So 'cosmo' is no more and it's just expected that 'cosmo' cannot be resolved. However, the error message mentioning 'cosmo' occurs regardless of what server I try to mount a NFS datastore of. I can't find any references to 'cosmo' in the ESXi server configuration in the vSphere client (although I don't know exactly where to look). I remember that at one point, a NFS datastore was mounted temporarily to 'cosmo' to host the ISO debug files. But no more.

  I tried this same sharing of an another ESXi (running the same version of ESXi) mounted in the same subnet (works great), and I also tried to mount a new NFS share on a server where the ESXi already had another NFS data store mounted from the same server (the data store already mounted works fine (, but attempts to connect to a new data store on the same failed server mentioning the independent 'cosmo' server as mentioned above). I tried to restart the ESXi server, but the problem persists after restarting.

  I'm under vSphere client 5.0.0 Build 455964 and ESXi 5.0.0 - 469512-standard with the free license. Because of the free license (I think), I don't have SSH access on the server. (Is that right?)

  How to work around the error message mentioning the obsolete server 'cosmo '? The only thing I can think of right now is to move all data from the local data store to a store of data already mounted, reinstall the ESXi server and give all the data. I'm hoping for a simpler solution! :-)

  Peter

  Can you confirm if this solution works for you?

• Is Microsoft Failover Cluster ESXi 4.1 Shared Disk of NFS data store, it supported?

  Is Microsoft Failover Cluster ESXi 4.1 Shared Disk of NFS data store, it supported?

  We have a request from MS Failover Cluster configuration on Windows 2008 R2 2 guests with a storage shared for a web application. However, there is no VMFS storage of data or the ability of the CF to presending RDM. So, I created the disks shared on a NFS datastore using option "Setup for Failover Clustering and Microsoft Cluster Service" and have added the cluster disk and tested successful failover.

  But the MS cluster validation control cancelled storage and I want to know if that configuration is not taken because of supported.

  A notice would be useful.

  We are also working on setting up a cluster of ESXi for iSCSI storage, which can be leveraed for this purpose.

  Shyam-

  Its not supported.

  4.1, your only options supported are:

  • CF storage with pRDMs
  • iSCSI storage with initiators guest.

• HA will only work if I share NFS data store in the cluster

  Hi all

  Please help me with my question below?

  HA work if I share NFS data store in the cluster? Even if if works is it advisable?

  Thank you

  Lucette

  Yes, but a VM restarts on a host within the same cluster VMware only.

• ESX4.1 - cannot connect to a NFS data store

  Hello

  I just installed the ESX4.1 for the test and tried to connect it to a NFS data store but it didn t work.

  After I get all the parameters in the add storage wizard and click Finish it displays the following message:

  -

  ---

  An error occurred during the configuration of the host

  Call 'HostDatastoreSystem.CreateNasDatastore' of object "datastoreSystem-9 'on vCenter Server 'WINSVR-TESTE1' has failed."

  -

  ---

  Please note that I have configured this same NFS on an ESX4.0 and it worked fine.

  Does anyone have any suggestions?

  Thank you

  Marcos

  Make sure that the vmkernel port is configured correctly. Is there something in the vmkernel log file?

  Maybe http://kb.vmware.com/kb/1005948 can help (even if 4.1 is not in the list)

  André

• ESXi connection to the Windows SFU NFS data store

  We plan to install 3 servers ESXi with virtual machines hosted on local.  A backup script align the images and move the *.vmx and *.vmdk to a NFS data store located in separate facilities which are connected via fiber.  All connections are links of 1 G.  The NFS data store will be hosted on w2k3 with SFU (Microsoft Services for Unix).

  The NFS data store will be a target for cloning and will be located in a building separated for "geographical separation."  I tested with Veema FastSCP (the public beta)... it's ok (30Mbytes/sec).  I assume that the clone process will take about 5 hours - but we can tolerate the performance hit after opening hours.

  Question:  Is there a "traps" to know by linking each ESXi server in the same directory NFS exported using SFU?  Perhaps more to the point... no problem with ESXi and Windows SFU?

  Before anyone asks... we do this on a 'super-thin budget' (that is to say... $ 0) using existing hardware, otherwise I would have ESX Enterprise and SAN storage!

  Some discussions to look at on the performance.

  http://communities.VMware.com/message/1133601#1133601

  http://communities.VMware.com/message/944761

  http://communities.VMware.com/message/997508

• Mapping in NFS data store fails in PowerShell

  I'm trying to access a data store NFS on my server ESXi of Powershell. I am able to access the VMFS data stores, but not my NFS datastore. I use this command:

  new-psdrive-location (get-data store Backup) - name dsBackup - psprovider VimDatastore-root ' '

  When I type cd dsBackup: I get this error:

  Get-Location: no player named ' \Datastore\ [email protected] \Datastore-172.XXX.XXX.XXX:\VM\' was found for the specified provider. Online: 1 char: 3 + cd & lt; & lt; & lt; & lt; dsBackup: Set-Location: cannot find path ' dsBackup:------' because it does not exist. Line: 1 char: 3 + cd & lt; & lt; & lt; & lt; dsBackup:

  I use the same command when you access warehouses of VMFS data without problems. I am able to browse, read and write in the VI Client NFS data store.

  Everyone knows this behavior? Any help would be much appreciated.

  Just tried with an ESXi 3.5 build 130755 store data as well.

  Works well.

  Note that I used VITK 1.5 build 142961 for this last test.

  Have you tried with VITK 1.5?

• VM shows this in the NFS data store after passed to the vmfs data store

  Hello

  (1) create a virtual machine using NFS datastore

  (2) had created a few snapshots

  (3) to migrate this virtual machine from the data to the local VMfs store

  (4) all the files are moved to the defined vmfs datastore

  (5) storage > > nfs_datastore > > objects > > VM > > vm is present

  (6) but when did change the setting of this VM, vm is present on the data store local vmfs

  The .vmsn file contains binary data text, so you better not change it manually. The purpose of these files is to be able to return to his instant partner. Depending on the configuration of virtual machines in time you created the snapshot, the virtual machine may require access to the old data store to access the files and folders in there when you return to this snapshot.

  André

• Cannot write to a NFS data store

  Hello

  I built a test environment to test ESXi 5.5 u1 to work. I am able to mount the database, browse the data store, but cannot write to it. I mounted on a different host of production and can't read/write very well.

  This happens on both servers in this test configuration. I must add, they used to be the ESX 3.5 hosts and had no problem with NFS data warehouses. I used the same NIC cards to create similar vSwitches. Trunking VLAN on our physical switches has not changed.  The two test servers have access to reading/writing/root for NFS mounting in our SAN (same as before IPs and it worked).

  Any suggestion would be appreciated.

  Thank you

  Well I guess you've got most of the standard things cleared here.

  I fall on this blog:

  http://emcsan.WordPress.com/2011/09/01/VMware-cant-write-to-a-Celerra-RW-NFS-mounted-datastore/

  Which seems to point to a few additional authorization with the EMC Clariion problems that must be addressed to make NFS work in later versions.  This gives a whril on your new hosts and let us know.

• How to add a second ESXi02 host to an existing NFS data store used by ESXi01?

  I am trying to configure vMotion between ESXi01 and ESXi02 in a nested running in VMWare workstation VMWare 55 9.  Everything works great so far.  I want ESXi02 to share the NFS datastore that uses ESXi01.

  Thank you

  If the web client help go to the storage, right-click the data store tab, go to all actions of vcenter and choose Add host.

• Best practices for a NFS data store

  I need to create a data store on a NAS and connect to some servers ESXi 5.0 as a NFS datastore.

  It will be used to host virtual machines less used.

  What are the best practices to create and connect a datastore NFS or networking and storage view bridges in order to get the best possible performance and decrease is not the overall performance of the network?

  Concerning

  Marius

  Create a new subnet of layer 2 for your NFS data warehouses and set it up on his own vSwitch with two uplinks in an active configuration / eve of reunification. Uplink should be variously patches in two distinct physical switches and the subnet must have the disabled bridge so that NFS traffic is not routable in other parts of your network. NFS export can be restricted to the IP address of storage host IP (address of the VM kernel port you created for NFS in the first step), or any address on that subnet. This configuration isolates traffic NFS for performance, ensures the security and redundancy. You should also consult your whitepapers of storage vendors for any specific recommendation of the seller.

  Data warehouses can be made available for the guests you wish and you can use Iometer to compare PAHO are / s and flow rate to see if it meets your expectations and requirements.

• Add several NFS data stores to multiple ESX hosts

  I am trying to write a script that will set up several NFS exports to multiple ESX hosts. Here is the script I use, it will add an NFS export to an esx host list.

  $esx = (get-Content servers.txt)

  {}
  $Host_Name = (Read-Host "enter the server (ex: storage-san)")
  $Path = (Read-Host "enter the path (ex: / ds_name/flight/flight)")
  $Name = (Read-Host "Enter the name of the data store")

  {foreach ($server in $esx)
  $Error.Clear)
  Get-VMHost $server | New-Nfs Datastore - NfsHost $Host_Name-path $Path - name $Name | Out-Null
  If ($error.count - gt 0) {$error | out-file ($server, 'c:\powershell scripts\logs\' + '.txt')}
  }

  $add_more = Read-Host "want to show you another data store?
  }
  While ($add_more - eq 'Yes' - or $add_more - eq "y")

  This script actually works OK but I can't just she kick sending and walk. If I have 10 stores of data to add, I have to wait for the current to the end, and then type the information for the second, etc..

  I was hoping just to type all the information from the beginning and the shot of the script to the wide and let him go. Here is what I added, you can see where I'm going with this?

  $esx = (get-Content servers.txt)

  $num_mounts = (Read-Host "Do you have multiple media")
  If ($num_mounts - eq 'Yes' - or $num_mounts - eq "y")
  {
  $mounts = @(Read-Host "supports différents combien avez_vous")

  #prompt me for all the different right monte upwards before and then executed by the actual task of Mount...
  }

  Any ideas?

  Try something like this

  $servers = @()
  $paths = @()
  $datastores = @()
  
  $answer = Read-Host "Enter another NFS mount ?" while($mount -eq "y"){
      $servers += Read-Host "Enter the NFS host"    $paths += Read-Host "Enter the path"    $datastores += Read-Host "Datastore name ?"    $answer = Read-Host "Enter another NFS mount ?"}
  
  $Error.Clear()
  
  Get-Content servers.txt | %{
      $esx = Get-VMHost -Name $_    $countNFS = $servers.Count
      if($countNFS -ne 0){
          0..($countNFS - 1) | %{
              New-Datastore -Nfs -NfsHost $servers[$_] -Path $paths[$_] -Name $datastores[$_] | Out-Null            if($Error.count -gt 0){
                  $Error | out-file ('c:\powershell scripts\logs\' + $server + '.txt')
                  $Error.Clear()
              }
          }
      }
  }
  

  The script reads all the data in the tables.

  Then it loops through all ESX hosts from the servers.txt file, and for each host, it will create all the NFS data storages.

• ESXi 4.1 cannot add NFS data store on a Netgear READYnas 1100 (please help)

  I have a Netgear ReadyNAS 1100 NAS

  When I put an NFS share, so I can add a store of data on my ESXi 4.1, I

  use the following instructions in their site: http://www.readynas.com/?p=3030

  Each

  time I try to join the NFS share via the GUI, I get the following

  message: "operation failed, diagnostics report: unable to complete.

  Operation of sysinfo.  Please see the log file VMkernel for more details. »

  I have

  have also tried the SSH console using the command: esxcfg-nas

  -a/share/mynfs s o 10.0.0.10 mynfs and I get the error:

  "Connection to the NAS volume: mynfs.

  Unable to connect to the NAS volume mynfs: unable to complete the operation of Sysinfo. Please see the log file VMkernel for more details. »

  details of the journal of the kernel are:

  August 19-14:37:36 pass: cannot read the header on stream TCP (local = 127.0.0.1:60962, even = 127.0.0.1:0): N7Vmacore15S ystemExceptionE (connection reset by peer)

  August 19 at 14:37:47 pass: PersistAllDvsInfo called

  August 19-14:37:51 pass: airfare to CIMOM version 1.0, root user

  Aug

  19 14:37:59 pass: [2010-08-19 14:37:59.311 2AAA3B90 info "TaskManager"

  opID = 993 D 2353-0000037 C] task created: haTask-ha-host - vim.host.DatastoreSystem.creat eNasDatastore-1124

  August 19 at 14:37:59 pass: 2010-08-19 14:37:59.312 FFFB0B90 info opID = 993 D 2353-0000037 C ' Hostsvc::DatastoreSystem' creating test data store

  August 19 at 14:37:59 pass: AddNasVolume called

  Aug

  19 14:37:59 pass: [2010-08-19 14:37:59.312 talkative FFFB0B90

  "FSVolumeProvider", opID = 993 D 2353-0000037 C] LookupVmfs: could not find VMFS

  volume id & lt; unset & gt; path, & lt; unset & gt; or name test

  August 19

  14:37:59 pass: [2010-08-19 14:37:59.312 talkative FFFB0B90

  "FSVolumeProvider", opID = 993 D 2353-0000037 C] LookupNasByName: could not find

  NasVolume volume test n soul

  August 19 at 14:37:59

  VMkernel: 0:23:10:59.338 cpu0:5299) NFS: 149: command: (Mont) server:

  (10.250.50.93) IP: (10.250.50.93) path: (/ esx) Label: (test) Options:

  (Non                   e)

  August 19 at 14:38:29 vmkernel: 0:23:11:29.669

  CPU2:5299) WARNING: NFS: 946: MOUNT RPCfailed with State CPP 13 (CPP has been

  interrupted due to timeout) try to serve mount r

  (10.250.50.93) path (/ esx)

  August 19 at 14:38:29 vmkernel: 0:23:11:29.669 cpu2:5299) NFS: 160: mounting NFS 10.250.50.93:/esx failed: unable to connect to the NFS server

  August 19 at 14:38:29 vobd: 19 August 14:38:29.727: 83489529043us: http://esx.problem.vmfs.nfs.mount.connect.failed failed to get to the 10.250.50.93 Server mount point /esx. E rror: unable to connect to the NFS server.

  Aug

  19 14:38:29 pass: [2010-08-19 14:38:29.727 FFFB0B90 error

  "FSVolumeProvider", opID = 993 D 2353-0000037 C] mount VmkCtl or ProcessNas

  has failed: operation completeSysinfo impossible.  Please see the VMkernel

  log file for more details.

  August 19 at 14:38:29 pass: [2010-08-19

  14:38:29.727 2AA15B90 'ha-eventmgr' info] event 79: impossible to climb to

  the 10.250.50.93 Server mount point /esx. C cannot

  me onnecter to the NFS server

  August 19 at 14:38:29 pass: [2010-08-19 14:38:29.740

  FFFB0B90 info "App" opID = 993 D 2353-0000037 C] AdapterServer caught

  exception: 2a6fb460

  August 19 at 14:38:29 pass: [2010-08-19 14:38:29.740

  FFFB0B90 info "TaskManager" opID = 993 D 2353-0000037 C] task completed:

  haTask-ha-host - vim.host.DatastoreSystem.cre ateNasDatastore-1124 Status error

  Aug

  19 14:38:29 pass: [2010-08-19 14:38:29.740 info FFFB0B90 "Vmomi"

  opID = 993 D 2353-0000037 C] Activation N5Vmomi10ActivationE:0x2a761010 : invoke made on vim.host.DatastoreSystem:ha - datastoresystem

  August 19 at 14:38:29 pass: Arg spec:

  August 19 at 14:38:29 pass: {(vim.host.NasVolume.Specification)

  August 19 at 14:38:29 pass: dynamicType = & lt; unset & gt;

  August 19 at 14:38:29 pass: remoteHost = "10.250.50.93."

  August 19 at 14:38:29 pass: remotePath = "/ esx"

  August 19 at 14:38:29 pass: localPath = "test."

  August 19 at 14:38:29 pass: mode = "readWrite"

  August 19 at 14:38:29 pass: type = "nfs."

  August 19 at 14:38:29 pass: userName = & lt; unset & gt;

  August 19 at 14:38:29 pass: password = & lt; unset & gt;

  August 19 at 14:38:29 spend :}

  August 19 at 14:38:29 pass: throw vim.fault.PlatformConfigFault

  August 19 at 14:38:29 pass: result:

  August 19 at 14:38:29 pass: {(vim.fault.PlatformConfigFault)

  August 19 at 14:38:29 pass: dynamicType = & lt; unset & gt;

  August 19 at 14:38:29 pass: faultCause = (vmodl. NULL in MethodFault),

  August 19 at 14:38:29 pass: faultMessage = (vmodl. [LocalizableMessage)

  August 19 at 14:38:29 pass: (vmodl. LocalizableMessage) {}

  August 19 at 14:38:29 pass: dynamicType = & lt; unset & gt;

  August 19 at 14:38:29 pass: key = "com.vmware.esx.hostctl.default"

  August 19 at 14:38:29 pass: arg = (vmodl. [KeyAnyValue)

  August 19 at 14:38:29 pass: (vmodl. KeyAnyValue) {}

  August 19 at 14:38:29 pass: dynamicType = & lt; unset & gt;

  August 19 at 14:38:29 pass: key = "reason."

  Aug

  19 14:38:29 pass: value = "could not complete the Sysinfo".

  operation.  Please see the log file VMkernel for more details. «,

  August 19 at 14:38:29 spend :}

  [August 19 at 14:38:29 pass:].

  August 19 at 14:38:29 pass: message = & lt; unset & gt;

  August 19 at 14:38:29 spend :}

  [August 19 at 14:38:29 pass:].

  August 19 at 14:38:29 pass: text = ","

  August 19 at 14:38:29 pass: msg = «»

  August 19 at 14:38:29 spend :}

  Check your DNS on the NFS Datastore server settings.  I had a timeout problem bad w / my NFS server.  We define for OPENDNS temporarily and NFS store popped up immediately.

  Joe

• Windows 2008 Server NFS - permission denied when accessing the NFS data store

  Hello

  I'm trying to configure a Windows 2008 Server to store virtual machines on an NFS share.

  When I add the data store to my host, I have no Brown Read-only and the data store is added successfully.

  When I browse the data store, as soon as I try to delete a file or create a folder, I have an error message: "cannot delete" or "cannot complete the file was created.

  It seems to be a problem of rights NFS, but impossible to find what the problem is.

  In the/var/log/vmkernel, I see:

  Mar 23 17:43:07 vmw-esx1 vmkernel: 1:02:37:20.635 cpu4:4109) NFSLock: 2677: can't get the lock on the file new document texte.txt 0x4100070384d0 on circe (10.254.0.19): Permission denied

  Don't you have a howto use NFS with Windows 2008 to help me?  I found one for Windows 2003, but think are too different.

  Or another idea?

  See document attached with the NFS share parameters.

  Philippe

  You must configure the user name mapping in Services for UNIX/NFS and map the root user.  Detailed instructions here: http://www.sohoadvisers.com/tutorials/vmware-esxi/connect-esxi-to-windows-nfs.  I was able to implement some hosts to use my Windows NFS export, but it was a bit unreliable.  This is a configuration not supported with VMware...

  Josh

  If you have found this or other useful information, please consider awarding points to 'Correct' or 'useful '.

  Visit http://vmtoday.com for news, views and virtualization how - to of

  Follow me on Twitter - @joshuatownsend