Problem mounting NFS

Similar Questions

• Mounting NFS host

  Well, I can mount a NFS data store by using something like the following with the rest of the script of the filling of the variables

  New-Nfs Datastore - VMHost $NEWHost - name $Sharename - way $remotePath - NfsHost $remoteHost | Out-Null

  In a script and it works without problem. However, this will work only for a simple NFS share on all servers.

  My question is this, and I expect to be pointed in the right direction if possible.

  I have several data centers, lets say Test01, Test02, and Test03. Within these centres I have physical hosts as follows, Test01esx01, Test01esx02, Test02esx01, Test02esx02 and so on.

  Within each of these data centers, I have a virtual machine that has an NFS share and named as follows, Test01NFS, Test02NFS and so on.

  For each of these data centers I want to set up the corresponding NFS share to the correct datacenter. If Test01NFS can be mounted on all servers Test01esx and then Test02NFS can be mounted on all servers Test02esx and so on. Any direction would be greatly appreciated.

  To avoid possible problems with quotes and substitution, I slightly changed the script.

  This version produces the same mistakes?

  Get-Datacenter | where {$_.Name -notmatch 'nottest*'} | foreach {
      $DC = $_    $DC | Get-VMHost | %{
  
          foreach ($DC.Name in $DC)
          {
              $NewName = $DC.Name
              $Site = $NewName.substring(0,6)
  
              $SiteNFS = $Site + "NFS"
  
              Write "DataCenter: $Site"            Write "Mounting NFS $SiteNFS"            if (!(Get-DataStore $SiteNFS -ErrorAction SilentlyContinue)) {
                  if((Get-WmiObject -Class Win32_PingStatus -Filter "Address='$SiteNFS'").StatusCode -eq 0){
                      New-Datastore -Nfs -VMHost $_ -Name $SiteNFS -Path /nfs -NfsHost $SiteNFS -ErrorAction SilentlyContinue | Out-Null                }
              }
          }
      }
  
  }
  

• problem with nfs run

  I have computer laptop hp 2000-2110, but when I run nfs running on it, the game runs slow what to do

  Hi saurabh0007,

  Welcome to the HPCommunity, I hope you enjoy your experience! To help you get the most out of the Forums of HP, I would like to draw your attention to the Guide of the Forums HP first time here? Learn how to publish and more.

  I saw your post about the problem with NFS running: run. Unless you have changed the processor and added little RAM your system isn't the minimum system requirements for the game. The game needs 4 GB of RAM and you only have 2 GB, and the processor should be 3.0 Ghz but yours has only 2.4 GHz, I have included links below for specifications of your laptop and the NFS: Run required.

  HP 2000-2110tu product specifications

  Need for Speed: minimum required Run

  Thank you

• Permisions required for mounting NFS on ESXi host

  Hi team,

  In our java application uses) use API VMWARE to mount the NFS datastore on the ESXi host. But to do this, we need the ESXI root permissions. Because having credentials root door reached the safety of the system, we would like to create a user with the required permissions will be sufficient to add the mounting NFS on ESXi host.

  But do not know how to see the permissions required for the Assembly of the NFS on ESXi host. Pointers would be useful.

  Thanks in advance,

  Anjana

  Hello

  Storage permissions lies in the roles of Group of data store.

  You should have a default profile role of storage in your vCenter.

  Cheque image:

  

  Hope this helps

• The addition of NFS to data - going. zmvolume failed a./mount-nfs-store.pl

  I have 1.5 of the workspace

  I am trying to add NFSv3 part in it. The NFS server is Windows 2008.

  I used the instructions in the document. Whats happening is on the line 'mount-a' at the mount-nfs - store.pl script its change the owner and group of zimbra to 4294967294 and therefore give the

  Error has occurred: directory does not exist or is not writable

  zmvolume failed on line de./mount-nfs-store.pl 67

  As soon as I remove the property and the group back to zimbra.

  Don't know what's happening here ideas?

  I also cant chown to zimbra thereupon 4294967294 unless and until I remove the disc first.

  Thank you

  If anyone need an answer... Make sure you give anonymous enable and give the file for anonymous logon rights

  INFO: How to enable the anonymous logon in NFS and in Windows Server 2003 or in Windows Storage Server 2003 (NAS)

• Cannot mount NFS Debian to esxi 5.1 - Please help

  I've tried everything. I'm extremely frustrated on the way this beginner step...

  Idea was the installation, a debian for nfs box and use sharing nfs as a data store in esxi.

  debian installation, Setup nfs-kernel-server

  tried to get through vshpere

  I get the following message is displayed:

  Call "HostDatastoreSystem.CreateNasDatastore" of object "ha-datastoresystem" on ESXi '192.168.1.95' failed.
  192.168.1.97:/esxi has no mounting NFS: the mount request was refused by the NFS server. Verify that the export exists and that the customer is allowed to ride.

  Ive looked everywhere and found very little on this subject... I think that its pretty beginner so no one's going in depth on how to do it step by step... I think that sharing is good and the permissions are good but I don't know how to check via the coast host or client...

  any help would be appreciated... I tried a lot of online how tos with no luck.

  Jon

  What is the absolute path to /esxi?

  You said above "my root" and I assumed to mean that esxi is a directory directly under /, but is that correct? Looks like maybe not.

• Unable to mount NFS 4.1 datastore on ESXi 6

  Good afternoon

  I m running the tests and now I have built a 6 CentOS with NFS 4.1 as a NAS.

  Some lines of logs of CentOS:

  
  

  RPC.statd [1623]: Version 1.2.3 starting

  SM-notify [1624]: Version 1.2.3 starting

  kernel: RPC: registered named UNIX socket transport module.

  kernel: RPC: registered udp transport module.

  kernel: RPC: registered tcp transport module.

  kernel: RPC: registered tcp backchannel NFSv4.1 transport module.

  kernel: installation knfsd (copyright (C) 1996 [email protected]).

  RPC.mountd [1720]: Version 1.2.3 starting

  kernel: NFSD: using/var/lib/nfs/v4recovery as the recovery of the NFSv4 State directory

  kernel: NFSD: from grace period of 90 seconds

  If I mount it from a Linux machine, it works fine:

  # mount.nfs4 < nfs_fqdn > :/ / Media

  # mount

  ....

  < nfs_fqdn > :/ on/Media type nfs4 (rw, addr = 192.168.X.X, clientaddr = 192.168.X.Y)

  Now, if I try to mount a 6 ESXi host, I get the following message:

  
  

  An error occurred during the configuration of the host.

  Operation failed, the diagnostic report: error of Sysinfo on return operation State: timeout. See the VMkernel detailed error information log

  
  

  A few lines of vmkernel.log:

  NFS41: NFS41_VSIMountSet:402: mount server: < server_hostname >, port: 2049, path: /nfs, label: NFSv4, security: 1 user:, options: < none >

  StorageApdHandler: 982: APD handle created with lock [StorageApd - 0 x 430694551140]

  WARNING: NFS41: NFS41ExidNFSProcess:2022: server does not support the Protocol NFS 4.1

  WARNING: NFS41: NFS41ExidNFSProcess:2022: server does not support the Protocol NFS 4.1

  WARNING: NFS41: NFS41FSWaitForCluster:3433: can't wait for the cluster will be placed: Timeout

  WARNING: NFS41: NFS41_FSMount:4412: NFS41FSDoMount failed: timeout

  StorageApdHandler: 1066: release ODA manage 0 x 430694551140

  StorageApdHandler: 1150: APD Handle released!

  WARNING: NFS41: NFS41_VSIMountSet:410: NFS41_FSMount failed: timeout

  Did someone ever set up a Linux machine as a NFS v4.1 for vSphere endpoint before?

  Thank you very much

  Well, the problem was exactly as described:

  WARNING: NFS41: NFS41ExidNFSProcess:2022: server does not support the Protocol NFS 4.1

  WARNING: NFS41: NFS41ExidNFSProcess:2022: server does not support the Protocol NFS 4.1

  
  

  My Linux kernel box´s was not managing NFS 4.1, 4.0 only.

  Solution has been updated with the distribution level.

  Thanks for the attention.

• 6.1 Notifications plugin file vROPS - hand mounting NFS vROPS device

  Hi all

  I wonder if someone could point me in the right direction please?

  We are currently set up outbound notifications plugin to create logs for all alerts using a NFS share that is mounted in the unit of vrops. We want to add a NFS share that we host a SCOM server which can then pick up each of the. Alerts LOG files we use SCOM as our main event management suite.

  We are facing challenges and fall at the first hurdle, however. We created a folder already that we then tried to use the mount standard t < servername/IPAdd > nfs: / / tmp/test nfsshare displays on the device of vROPS of collector main newspaper but it just hangs and does nothing. have you tried many different chains of command for it, but we get back the same thing...

  We tested the part from another machine and it's fine so I don't think a permissions problem.

  Anyone who has tried this successfully?

  Concerning

  Richard

  Managed to solve now using nolock o in the commnd mount and using Chmod to make sure that vRops could write this direcroty

  Magic!

• Cannot mount NFS via client - can however on the host.

  Hello

  I have problems with a NFS volume to ESX 4.1 as a data store.

  I can mount the NFS volume on the host directly from the command line.

  I wasn't able to do it on the command-line for awhile, then I realized that the Firewall setting was there.

  Once I change the Firewall setting, I could get directly on the host computer.

  But when I try the client - configuration-> data-> add datastore store I get

  Call "HostDatastoreSystem.CreateNasDatastore" of object "ha-datastoresystem" on ESX '10.23.43.54' failed.

  I also tried to stop and start the nfs and portmap services.

  Thank you!

  Jay

  Hi Jay,.

  From the command line, you use "move up" or "esxcfg-nas"? Try to use the other and take a look on the vmkernel log (/ var/log/vmkernel).

  Concerning

  Franck

• Mounting NFS a fall during a LAN free backup connection vRanger

  It is a sporadic problem.  Here is the output of the vmkernel logs.  I am concerned by the volume shows why does not.  Now, with this work, I had 3 other guests as well backup and they don't drop their connection.  Makes me far from the unit DataDomain we support up to.  We have changed our vSwitch configuration and isolated the vmkernel for nfs traffic.  We moved the natachasery to a switch of concert dedicated with all ports configured to Auto.  Any suggestions?

  Mar 20 18:35:32 lkldesx4svr vmkernel: 8:01:39:16.328 cpu6:1215) StorageMonitor: 196: vmhba0:0:15:0 status = 24/0 0 x 0 0 x 0 0 x 0

  Mar 20 18:35:58 lkldesx4svr vmkernel: 8:01:39:42.193 cpu7:1032) WARNING: NFS: 257: mount: Server (Backup_ESX_DDR) (10.1.42.10) 10.1.42.10 Volume: (/ backup, lakeland, vrangerpro, nfs) does not

  Mar 20 18:36:01 lkldesx4svr vmkernel: 8:01:39:44.481 cpu7:1037) BC: 2672: didn't flower 8 buffers of size 131072 each object b00f 36 1 63f29ef0 1 1 c53e0000 558 8e03df46 a95e2cb0 c 0 0 0 0 0: no connection

  Mar 20 18:36:01 lkldesx4svr vmkernel: 8:01:39:44.481 cpu7:1037) BC: 2672: didn't flower 2 buffers size 131072 each object b00f 36 1 63f29ef0 1 1 c53e0000 558 8e03df46 a95e2cb0 c 0 0 0 0 0: no connection

  Mar 20 18:36:02 lkldesx4svr vmkernel: 8:01:39:46.100 cpu0:1024) WARNING: NFS: 281: mount: Server (Backup_ESX_DDR) (10.1.42.10) 10.1.42.10 Volume: (/ backup, lakeland, vrangerpro, nfs) OK

  Mar 20 18:36:50 lkldesx4svr vmkernel: 8:01:40:33.501 cpu4:1083) DevFS: 2222: could not find the device: 24208-EXCHSVR_1-000001 - delta.vmdk

  Mar 20 18:36:50 lkldesx4svr vmkernel: 8:01:40:33.503 cpu4:1083) DevFS: 2222: could not find the device: 15720 b-EXCHSVR-000001 - delta.vmdk

  Mar 20 18:36:50 lkldesx4svr vmkernel: 8:01:40:33.505 cpu4:1083) DevFS: 2222: could not find the device: 1121-EXCHSVR_C-000001 - delta.vmdk

  Mar 20 18:36:50 lkldesx4svr vmkernel: 8:01:40:34.204 cpu7:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:0 (handle 8406)

  Mar 20 18:36:50 lkldesx4svr vmkernel: 8:01:40:34.204 cpu7:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:1 (handle 8407)

  Mar 20 18:36:50 lkldesx4svr vmkernel: 8:01:40:34.204 cpu7:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:2 (handle 8408)

  Mar 20 18:36:50 lkldesx4svr vmkernel: 8:01:40:34.206 cpu5:1106) World: vm 1248:900: from world vmware-vmx with 44 flags

  Mar 20 18:36:52 lkldesx4svr vmkernel: 8:01:40:36.076 cpu4:1083) DevFS: 2222: could not find the device: e9221-EXCHSVR_1-000002 - delta.vmdk

  Mar 20 18:36:52 lkldesx4svr vmkernel: 8:01:40:36.101 cpu6:1083) DevFS: 2222: could not find the device: c7225-EXCHSVR-000002 - delta.vmdk

  Mar 20 18:36:52 lkldesx4svr vmkernel: 8:01:40:36.103 cpu6:1083) DevFS: 2222: could not find the device: 3229-EXCHSVR_C-000002 - delta.vmdk

  Mar 20 18:36:52 lkldesx4svr vmkernel: 8:01:40:36.216 cpu4:1083) DevFS: 2222: could not find the device: 5222e-EXCHSVR_C-000002 - delta.vmdk

  Mar 20 18:36:53 lkldesx4svr vmkernel: 8:01:40:36.515 cpu3:1027) StorageMonitor: 196: vmhba0:0:15:0 status = 24/0 0 x 0 0 x 0 0 x 0

  Mar 20 18:36:53 lkldesx4svr vmkernel: 8:01:40:36.538 cpu3:1136) StorageMonitor: 196: vmhba0:0:15:0 status = 24/0 0 x 0 0 x 0 0 x 0

  Mar 20 18:36:53 lkldesx4svr vmkernel: 8:01:40:36.633 cpu6:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:0 (handle 8409)

  Mar 20 18:36:53 lkldesx4svr vmkernel: 8:01:40:36.634 cpu6:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:1 (handle 8410)

  Mar 20 18:36:53 lkldesx4svr vmkernel: 8:01:40:36.634 cpu6:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:2 (handle 8411)

  Mar 20 18:36:53 lkldesx4svr vmkernel: 8:01:40:36.635 cpu5:1106) World: vm 1249:900: from world vmware-vmx with 44 flags

  Mar 20 18:36:53 lkldesx4svr vmkernel: 8:01:40:37.116 cpu7:1083) DevFS: 2222: could not find the device: 55230-EXCHSVR_1-000002 - delta.vmdk

  Mar 20 18:36:53 lkldesx4svr vmkernel: 8:01:40:37.119 cpu7:1083) DevFS: 2222: could not find the device: 3234-EXCHSVR-000002 - delta.vmdk

  Mar 20 18:36:53 lkldesx4svr vmkernel: 8:01:40:37.120 cpu7:1083) DevFS: 2222: could not find the device: 1f239-EXCHSVR_C-000002 - delta.vmdk

  Mar 20 18:36:53 lkldesx4svr vmkernel: 8:01:40:37.225 cpu5:1083) DevFS: 2222: could not find the device: 3 d 240-EXCHSVR-000002 - delta.vmdk

  Mar 20 18:36:54 lkldesx4svr vmkernel: 8:01:40:37.585 cpu6:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:0 (handle 8412)

  Mar 20 18:36:54 lkldesx4svr vmkernel: 8:01:40:37.585 cpu6:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:1 (handle 8413)

  Mar 20 18:36:54 lkldesx4svr vmkernel: 8:01:40:37.585 cpu6:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:2 (handle 8414)

  Mar 20 18:36:54 lkldesx4svr vmkernel: 8:01:40:37.587 cpu5:1106) World: vm 1250:900: from world vmware-vmx with 44 flags

  Mar 20 18:37:01 lkldesx4svr vmkernel: 8:01:40:44.800 cpu4:1083) DevFS: 2222: could not find the device: 3 a 242-EXCHSVR_1-000002 - delta.vmdk

  Mar 20 18:37:01 lkldesx4svr vmkernel: 8:01:40:44.801 cpu4:1083) DevFS: 2222: could not find the device: 6247-EXCHSVR-000002 - delta.vmdk

  Mar 20 18:37:01 lkldesx4svr vmkernel: 8:01:40:44.802 cpu4:1083) DevFS: 2222: could not find the device: 3224 a-EXCHSVR_C-000002 - delta.vmdk

  Mar 20 18:37:01 lkldesx4svr vmkernel: 8:01:40:44.914 cpu0:1083) DevFS: 2222: could not find the device: 4724e-EXCHSVR_1-000002 - delta.vmdk

  Mar 20 18:37:01 lkldesx4svr vmkernel: 8:01:40:45.094 cpu0:1083) DevFS: 2222: could not find the device: 20254-EXCHSVR_C-000002 - delta.vmdk

  Mar 20 18:37:01 lkldesx4svr vmkernel: 8:01:40:45.130 cpu0:1083) DevFS: 2222: could not find the device: 6256-EXCHSVR-000002 - delta.vmdk

  Mar 20 18:37:01 lkldesx4svr vmkernel: 8:01:40:45.172 cpu2:1083) DevFS: 2222: could not find the device: EXCHSVR_1-8258-000002 - delta.vmdk

  Mar 20 18:37:02 lkldesx4svr vmkernel: 8:01:40:45.443 cpu0:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:0 (handle 8415)

  Mar 20 18:37:02 lkldesx4svr vmkernel: 8:01:40:45.443 cpu0:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:1 (handle 8416)

  Mar 20 18:37:02 lkldesx4svr vmkernel: 8:01:40:45.443 cpu0:1083) VSCSI: 4060: creation of virtual device for world 1084 vscsi0:2 (handle 8417)

  Mar 20 18:37:53 lkldesx4svr vmkernel: 8:01:41:36.717 cpu2:1119) StorageMonitor: 196: vmhba0:0:15:0 status = 24/0 0 x 0 0 x 0 0 x 0

  Mar 20 18:37:55 lkldesx4svr vmkernel: 8:01:41:38.563 cpu5:1214) VSCSI: 4060: creation of virtual device for world 1215 vscsi0:0 (handle 8418)

  Mar 20 18:37:55 lkldesx4svr vmkernel: 8:01:41:38.565 cpu5:1214) VSCSI: 4060: creation of virtual device for world 1215 vscsi0:1 (handle 8419)

  Mar 20 18:37:55 lkldesx4svr vmkernel: 8:01:41:38.565 cpu5:1214) VSCSI: 4060: creation of virtual device for world 1215 vscsi0:2 (handle 8420)

  Mar 20 18:37:55 lkldesx4svr vmkernel: 8:01:41:38.568 cpu5:1214) VSCSI: 4060: creation of virtual device for world 1215 vscsi0:3 (handle 8421)

  Mar 20 18:37:55 lkldesx4svr vmkernel: 8:01:41:38.569 cpu5:1214) VSCSI: 4060: creation of virtual device for world 1215 vscsi0:4 (handle 8422)

  Mar 20 18:37:55 lkldesx4svr vmkernel: 8:01:41:38.570 cpu5:1214) VSCSI: 4060: creation of virtual device for world 1215 vscsi0:5 (handle 8423)

  Mar 20 18:37:55 lkldesx4svr vmkernel: 8:01:41:38.570 cpu5:1214) VSCSI: 4060: creation of virtual device for world 1215 vscsi0:6 (handle 8424)

  Mar 20 18:37:55 lkldesx4svr vmkernel: 8:01:41:38.570 cpu5:1214) VSCSI: 4060: creation of virtual device for world 1215 vscsi0:8 (handle 8425)

  Mar 20 18:38:13 lkldesx4svr vmkernel: 8:01:41:56.771 cpu7:1216) StorageMonitor: 196: vmhba0:0:15:0 status = 24/0 0 x 0 0 x 0 0 x 0

  Mar 20 18:38:33 lkldesx4svr vmkernel: 8:01:42:16.847 cpu7:1216) StorageMonitor: 196: vmhba0:0:15:0 status = 24/0 0 x 0 0 x 0 0 x 0

  Mar 20 18:39:08 lkldesx4svr vmkernel: 8:01:42:52.293 cpu5:1216) StorageMonitor: 196: vmhba0:0:15:0 status = 24/0 0 x 0 0 x 0 0 x 0

  Kind regards...

  Jamie

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

  Remember, if it isn't one thing, it's your mother...

  Have you looked at your memory usage and utilization of the network while the backups have occurred?  How much memory is on your service console?  Run the "free-m" during a backup, or run it periodically and see if you have memory problems when a disconnection occurs.  In addition, run esxtop and watch your cpu and high regular during a backup to see how much stress the service console has during this period.

  -KjB

  VMware vExpert

• Microsoft xbox 360 controller for windows problem with NFS

  Hi, I brought yesterday Microsoft xbox 360 controller for windows. I installed and the end driver. The problem is that when I play NFS Most Wanted & NFS Carbon, cars automatically starts left thin when I accelerate? Why is - this problem to occur, and what is the solution?

  I also changed the default controllers controls and set left lean & thin right to left analog stick left/right as PRIMARY & I updated lean left & lean right D - pad left/right as SECONDARY controls.

  Hi Zxcvbnma,

  ·         Is the specific issue with only Need for Speed or does happen with other games as well?

  If the problem is specific only with Need for Speed, you can try to uninstall the game and reinstall the game and check if it works fine without any problems.

  I also suggest that you uninstall Xbox 360 controller drivers and reinstall the drivers that could help you solve the problem.

  Check the settings of the game. You can also connect the controller to the other computer and use it and check if the problem still persists.

  Thank you, and in what concerns:
  Swathi B - Microsoft technical support.

  Visit our Microsoft answers feedback Forum and let us know what you think.

• problem with NFS MOST WANTED... car does not work well

  Hey... I installed NFS MOST wanted on my laptop a long time ago... and 2 days ago it was working properly, but now during acceleration cars, its noise is too loud, and it does not work well or normal...

  Nobody understand my problem... plz suggest me...

  Try a system restore to when it worked:
  http://Windows.Microsoft.com/en-us/Windows7/products/features/system-restore

  Check the reliability monitor to see what changed between where he worked and where you have noticed the problem:
  http://Windows.Microsoft.com/en-us/Windows7/how-to-use-reliability-monitor

  In particular, if there is no driver updates, try to back off:
  http://Windows.Microsoft.com/en-us/Windows7/restore-a-driver-to-its-previous-version

• Can't mount NFS share - operation failed, diagnostics report: failed to get the path console for volume

  I'm trying to mount a NFS on ESXI 6 volume, but continue to operate in the error.  Googling everything nothing helped, so I'm here. Error:

  Call "HostDatastoreSystem.CreateNasDatastore" of object "ha-datastoresystem" on ESXi '192.168.xx.xx' failed.

  Operation failed, the diagnostic report: failed to get the path of the console for the volume, the name of the sample.

  The NFS share is located on a synology nas. I checked the permissions and configuration. Everything seems correct based on the various boards and KB articles.

  Ideas?

  Thank you.

  Find the esx.conf file in/etc/vmware.

  If you could also share a copy with me...

  Try to mount the NFS VMware KB: Volume fails with the error: could not resolve the host name

  Check the link as well below.

  http://www.Bussink.ch/?p=1640

• No mounted NFS-vVol-store of data-&gt; how to mount again or get rid of it?

  Hello

  I configured with vSphere 6.0 and NetApp-Sim 8.3, NetApp VSC 6.0 and NetApp VASA 6.0 a vVol environment. I created a Datastore NFS-vVol-called 'vvolnfs1 '. Then I tried to destroy the NFS-vVol-DS again via the context menu of the NetApp-VASA--.provider nter in the Web Client:

  

  Actually, it fails with an error device busy, because I had not deleted the hidden vSphere-HA-directory.

  After that, I tried to disassemble the data store with the "remove Datastore...". ' - enter - it worked, WOW! VVol-DS has disappeared from the Web Client.

  But when I tried to recreate, I discovered that vVol-DS was just hidden. I couldn't use the same name again. I have a vVol-store data not mounted and cannot get rid of it. In the esxi console, it seems, but without the ability (and I get an error with df - h):

  [root@esxi-9: ~] df h

  180556:VVOLLIB: VVolLibConvertSoapFault:1705: customer. VvolLibDoRetryCheckAndUpdateError failed with an error

  180556:VVOLLIB: VVolLibConvertVvolStorageFault:1266: INVALID_ARGUMENT for lack of storage (9): invalid container

  Size of filesystem used available use % mounted on

  [...]

  vvol 0.0 B B B/vmfs/volumes/vvolnfs1 0% 0.0 0.0

  [...]

  [root@esxi-9: ~]

  In esxli, I can see the vVol, but marked as non-accessible:

  [root@esxi-9: ~] list of storagecontainer esxcli storage vvol

  vvolnfs1

  StorageContainer name: vvolnfs1

  UUID: vvol:35a62a5ffee3445d - b 8, 85000000989874

  Table: unavailable

  Size (MB): 0

  Free (MB): 0

  Accessible: false

  Default policy:

  [...]

  [root@esxi-9: ~]

  Can I "mount" this vVol-DS again? Where can I get rid of him? Just delete the FlexVol appropriate in the NetApp-Sim?

  Any help is appreciated!

  Best regards

  Christian

  Hi all, I found the answer to my question: I had to use the 'standard' datastore procedure - add - it appeared the missing NFS vvol-DS and I could readd it. Cheers, Christian

• ESXi5 - problems with NFS and the data copy store

  Hello world

  I recently moved into a solution fully virtualized for my network, 3 x 5 ESXi servers running on our GigE network.

  First of all, I use all free software from VMware, so vCentre etc is out of the question.

  I have major problems when you try to copy files between:

  • NAS (NFS) to ESXi 5 host
  • ESXi host to the NAS (NFS) 5
  • And using VMware converter between ESXi 5 hosts converter Standalone

  The problem is that whenever I'm transfer between hosts I am struck with the horrible network performance. Even if I use GigE adapters and switches between my hosts I will receive no more than 12 Mbps speed of transfer real (100 Mbit/s connect?).

  On the flipside, if I use virtual guests on the same exact host I can happily transfer data between my NAS (NFS) servers with speeds between 60-150MBps ~ (1000 Mbps).

  Examples:

  Speed of 10 Mbps of transfer of ESXi_1 copy OF NFS data store share ~

  Server2008 (comments, located on ESXi_1) copy OF NFS 75MBps transfer rate ~.

  Server2011 SBS (comments, located on ESXi_2) copy OF Windows share 2008 (ESXi_1) transfer speed 120MBps. ~

  ESXi_2 copy OF NFS data store share transfer rate 5MBps ~.

  Attached (wtf.png) example:

  I copy a file that is located on our NFS share first, it's a 3 GB file to the copy within guest OS (2008), it is indicated in blue - top speed of 80MBps

  I copy the same exact NFS share for the host (datastore1), this is indicated in red - top speed of 7.5Mbps

  The third transfer/s (green) is between the customers of windows on different hosts, transfer a 6 GB file as well as a copy of the 360 MB file - transfers two happily send to GigE speeds with a peak around 40MBps

  I can reflect these results across the three servers without modification. Copies between you will be able to run well enough (not exactly 100% use of GigE) but at the moment where I try to do something to the data store it will just choke at all about a 100 Mbps connection speed.

  The final image (wot.png) confuses me beyond belief. I would try to explain what is happening here:

  • This image shows two times the same exact file transfers, except even machine PHYSICS
  • The first (red) transfer between the ESXi_2 host server and the NFS share using the browser data store and direct download - its top speed is around 8MBps
  • The second (green) transfer between a guest server 2008 running on ESXi_2, download the same file exactly at the exact location using vSphere Client. I mean the same EXACT file; It connects to the NFS drive by the data store ESXi_2 (NFS share).

  Why on earth can my comments directly download a file on a data store connected to NFS GigE clocked and yet the same exact host cannot go anywhere near corresponding to these speeds?

  As indicated in the title, the problem seems to happen whenever I use ESXi datastore browser on the host computer using vSphere Client or between browser datastore ESXi to/from an NFS share.

  No one knows what might happen?

  Is there some sort of restriction on the transfer of files between a host and shared NFS ESXi 5? Whence this bottleneck?

  Thanks in advance for all the help/ideas that guys can throw my way.

  P.S. Sorry for the wall of text, I really wanted to give as much information. as possible.

  What type of storage you have locally on the host computer?

  I have seen this problem with write-through controllers: http://wahlnetwork.com/2011/07/20/solving-slow-write-speeds-when-using-local-storage-on-a-vsphere-host/