Failed error caused by file vmfs volumes

Вебинары VMC о виртуализации:

Постер VMware vSphere PowerCLI 6.3:

Постер VMware ESXi 5.1:

Постер VMware Hands-on Labs 2015:

Постер VMware Platform Services Controller 6.0:

Постер VMware vCloud Networking:

Постер VMware NSX (референсный):

Постер VMware vCloud SDK:

Постер VMware vCloud Suite:

Постер VMware vCenter Server Appliance:

Порты и соединения VMware vSphere 6:

Порты и соединения VMware Horizon 7:

Порты и соединения VMware NSX:

Управление памятью в VMware vSphere 5:

Как работает кластер VMware High Availability:

Постер VMware vSphere 5.5 ESXTOP (обзорный):

Постер Veeam Backup & Replication v8 for VMware:

Постер Microsoft Windows Server 2012 Hyper-V R2:

Источник

Error caused by file esxi

I’m having an issue when copying a vmdk to another or same data store (NFS) . this can be from our nfs snapshot folder or even from one folder to another that makes no difference. all other files copy fine.

Is it not vmdk that is the issue but the size of files i don’t know.

We are using ESXi 5

Anyone an idea? we cannot restore any backups out of NFS snapshots due tot this issue

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

> I’m having an issue

can you be more specific ? — I hope you do not try to use cp against vmdks ?

________________________________________________
Do you need support with a VMFS recovery problem ? — send a message via skype «sanbarrow»
I do not support Workstation 16 at this time .

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

i wrote the problem in the title

error caused by file [path to vmdl] during copy of a vm from snapshot on NFS data Store

we try to copy a vmdk out of a nfs snapshot (flat files) to the same or another data store and this copy fails with error error caused by file [path to vmdk]

Copy is done in datastore browser. small files seem to work. even vmdks from 8gb copy fine. when copying 30gb the error occurs. And the errur occurs instantly so not after copying half the file.

Источник

Cannot Clone or backup a VM

We are having an issue regarding a certain VM. we can’t seem to back it up using veeam or clone it via vcenter.

error on vcenter: using ESXi 6.5

«Error caused by file /vmfs/volumes/(datastore name)/(vmdk file)»

though however, we can freely migrate it through our 3 host but we can’t clone it. hope someone can help me on this please.

Popular Topics in VMware

11 Replies

I’ve seen something like this. The problem (I saw before) was an issue with changed block tracking backups corrupting the .vmdk file. Virtually identical description; can move between hosts, VM runs fine, can’t back up or clone. First, try turning off the CBT in your .vmx config file. Shut down the VM. Right click the VM, Edit Settings>Options>General>Config. Parameters. Set CTK to False. Alternately, you can open the .vmx file in a text editor and look for «CTKdisallow=true» and make sure it’s in there. If it says false, change it.

Somehow CBT gets wonky and creates a virtual hdd error. This was an issue several years ago and I haven’t see it since and never gave it another thought.

If for some reason this doesn’t fix your issue it’s super easy to revert.

I’ve seen something like this. The problem (I saw before) was an issue with changed block tracking backups corrupting the .vmdk file. Virtually identical description; can move between hosts, VM runs fine, can’t back up or clone. First, try turning off the CBT in your .vmx config file. Shut down the VM. Right click the VM, Edit Settings>Options>General>Config. Parameters. Set CTK to False. Alternately, you can open the .vmx file in a text editor and look for «CTKdisallow=true» and make sure it’s in there. If it says false, change it.

Somehow CBT gets wonky and creates a virtual hdd error. This was an issue several years ago and I haven’t see it since and never gave it another thought.

If for some reason this doesn’t fix your issue it’s super easy to revert.

Hi Pete, Thank you on this. will surely try this after my server backup on the guest VM is done. so to prevent future issues, we relied first on a windows server backup utility just to be sure. then after we will try your suggestion. thank you in advance.

I’ve seen something like this. The problem (I saw before) was an issue with changed block tracking backups corrupting the .vmdk file. Virtually identical description; can move between hosts, VM runs fine, can’t back up or clone. First, try turning off the CBT in your .vmx config file. Shut down the VM. Right click the VM, Edit Settings>Options>General>Config. Parameters. Set CTK to False. Alternately, you can open the .vmx file in a text editor and look for «CTKdisallow=true» and make sure it’s in there. If it says false, change it.

Somehow CBT gets wonky and creates a virtual hdd error. This was an issue several years ago and I haven’t see it since and never gave it another thought.

If for some reason this doesn’t fix your issue it’s super easy to revert.

Hi Pete, Thank you on this. will surely try this after my server backup on the guest VM is done. so to prevent future issues, we relied first on a windows server backup utility just to be sure. then after we will try your suggestion. thank you in advance.

Please refrain from using Windows backup to backup a VM. its the wrong tool for the job. use Veeam B&R for VMware (Not Veeam Agent for Windows also).

I’ve seen something like this. The problem (I saw before) was an issue with changed block tracking backups corrupting the .vmdk file. Virtually identical description; can move between hosts, VM runs fine, can’t back up or clone. First, try turning off the CBT in your .vmx config file. Shut down the VM. Right click the VM, Edit Settings>Options>General>Config. Parameters. Set CTK to False. Alternately, you can open the .vmx file in a text editor and look for «CTKdisallow=true» and make sure it’s in there. If it says false, change it.

Somehow CBT gets wonky and creates a virtual hdd error. This was an issue several years ago and I haven’t see it since and never gave it another thought.

If for some reason this doesn’t fix your issue it’s super easy to revert.

Hi Pete, Thank you on this. will surely try this after my server backup on the guest VM is done. so to prevent future issues, we relied first on a windows server backup utility just to be sure. then after we will try your suggestion. thank you in advance.

Please refrain from using Windows backup to backup a VM. its the wrong tool for the job. use Veeam B&R for VMware (Not Veeam Agent for Windows also).

I agree it’s the wrong tool, but in the case when Veeam isn’t working due to a problem with a VHD not backing up or cloning using the correct tools, I’d use the native Windows backup rather than nothing

Источник

Adblock
detector

Error caused by file vmfs volumes vmdk

We have a number of rogue VMDK files that dont appear to be connected to anything, we can move, rename these files but cannot delete them, they all appear to be -flat files e.g «SRV-FS_1-flat.vmdk»

I have tried the following —

reboot of the vcentre

reboot of the backup server

reboot of the named VM

tried removing from vcentre and the host management pages

the error I get is —

Delete Datastore File

Description Delete the source file or folder from the datastore

State Failed — Error caused by file /vmfs/volumes/59c386ab-acc6bf16-6452-b499bab20938/trashfolder/SRV-VEEAMMGR-flat.vmdk

Can anyone advise how to remove these files?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

>>> . that dont appear to be connected to anything
Please don’t mind me asking, but how did you determine this?
.vmdk file are virtual disk files, which contain the user data, and it’s fairly uncommon that they become orphaned.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Many thanks for your response. I have checked each of the hosted servers and none have links to these files. these files are showing date stamps from last year.

I would have thought if the file was renamed the server(s) that had any locks on the files would have gone offline / shown some errors please correct me if I am wrong on this point.

I am looking again at this today, concentrating on the srv-adsync machine.

The one thing that might be of useful info is that we have had a rebuild of the VCENTRE server, which was a windows based to the appliance based, my thoughts are did this faulty vcentre have something still open with these servers when it failed?

the disk store these files are on is our replica store so live machines wouldn’t have been hosted on it

Источник

Error caused by file vmfs volumes vmdk

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I cannot delete a vmdk file from my datastore. The file in question (S9_1-flat.vmdk) cannot be deleted using the vSphere Client or using CLI. I’ve attached the output from my SSH session:

/vmfs/volumes/50bb5d47-5677d7b4-cb59-90b11c1479d7/S9 # ls -al

drwxr-xr-x 1 root root 3640 Aug 17 15:45 .

drwxr-xr-t 1 root root 1540 Aug 17 14:59 ..

-rw-r—r— 1 root root 27 Jul 10 09:15 S9-365b1e05.hlog

-rw——- 1 root root 17179869184 Aug 17 15:45 S9-365b1e05.vswp

-rw——- 1 root root 107374182400 Aug 18 11:56 S9-flat.vmdk

-rw——- 1 root root 8684 Aug 17 15:46 S9.nvram

-rw——- 1 root root 491 Aug 17 15:45 S9.vmdk

-rw-r—r— 1 root root 0 Mar 21 2014 S9.vmsd

-rw——- 1 root root 4172 Aug 17 15:45 S9.vmx

-rw——- 1 root root 0 Aug 17 15:45 S9.vmx.lck

-rw-r—r— 1 root root 3033 Aug 17 15:39 S9.vmxf

-rw——- 1 root root 4068 Aug 17 15:45 S9.vmx

-rwxrwxrwx 1 root root 1099511627776 Jun 29 10:07 S9_1-flat.vmdk

-rw——- 1 root root 586263035904 Aug 18 11:01 S9_2-flat.vmdk

-rw——- 1 root root 520 Aug 17 15:45 S9_2.vmdk

-rw——- 1 root root 8561355 Aug 15 19:44 vmmcores-1.gz

-rw——- 1 root root 3581220 Aug 16 07:52 vmmcores-2.gz

-rw——- 1 root root 2968111 Aug 16 07:53 vmmcores-3.gz

-rw-r—r— 1 root root 227605 Aug 17 14:54 vmware-79.log

-rw-r—r— 1 root root 227281 Aug 17 15:02 vmware-80.log

-rw-r—r— 1 root root 232708 Aug 17 15:16 vmware-81.log

-rw-r—r— 1 root root 226958 Aug 17 15:28 vmware-82.log

-rw-r—r— 1 root root 235389 Aug 17 15:35 vmware-83.log

-rw-r—r— 1 root root 230933 Aug 17 15:38 vmware-84.log

-rw-r—r— 1 root root 236001 Aug 18 09:18 vmware.log

-rw——- 1 root root 97517568 Aug 17 15:45 vmx-S9-911941125-1.vswp

/vmfs/volumes/50bb5d47-5677d7b4-cb59-90b11c1479d7/S9 # rm -f S9_1-flat.vmdk

rm: can’t remove ‘S9_1-flat.vmdk’: Invalid argument

(Note that the permissions on the file are currently set as 777 as I initially thought that this could be a permissions issue).

Источник

Виртуализация vSphere, Hyper-V, Xen и Red Hat

Более 5820 заметок о виртуализации, виртуальных машинах VMware, Microsoft и Xen, а также Kubernetes

VM Guru / News / Залоченные файлы виртуальной машины в VMware vSphere — Could not power on VM: Lock was not free.

Залоченные файлы виртуальной машины в VMware vSphere — Could not power on VM: Lock was not free. Реклама: При эксплуатации виртуальной инфраструктуры VMware vSphere иногда случается ситуация, когда виртуальную машину нельзя включить из-за того, что ее какой-нибудь из ее файлов оказывается залоченным. Происходит это при разных обстоятельствах: неудачной миграции vMotion / Storage vMotion, сбоях в сети хранения и прочих. Наиболее распространенная ошибка при этом выглядит так: Could not power on VM: Lock was not free Встречаются также такие вариации сообщений и ошибок при попытке включения виртуальной машины, которое зависает на 95%: Unable to open Swap File Unable to access a file since it is locked Unable to access a file since it is locked Unable to access Virtual machine configuration Ну а при попытке соединения с консолью ВМ получается вот такое: Error connecting to .vmx because the VMX is not started Все это симптомы одной проблемы — один из следующих файлов ВМ залочен хост-сервером VMware ESXi: При этом залочил файл не тот хост ESXi, на котором машина зарегистрирована. Поэтому решение проблемы в данном случае — переместить ВМ холодной миграций на тот хост, который залочил файл и включить ее там, после чего уже можно переносить ее куда требуется. Но как найти тот хост ESXi, который залочил файл? Об этом и рассказывается ниже. Поиск залоченного файла ВМ Хорошо если в сообщении при запуске виртуальной машины вам сообщили, какой именно из ее файлов оказался залоченным (как на картинке выше). Но так бывает не всегда. Нужно открыть лог vmware.log, который расположен в папке с виртуальной машиной, и найти там строчки вроде следующих: Failed to initialize swap file : Lock was not free Тут видно, что залочен .vswp-файл ВМ. За логом на экране можно следить командой (запустите ее и включайте ВМ): tail /vmfs/volumes/ / /vmware.log Проверка залоченности файла ВМ и идентификация владельца лока После того, как залоченный файл найден, нужно определить его владельца. Сначала попробуем команду touch, которая проверяет, может ли бы обновлен time stamp файла, т.е. можно ли его залочить, или он уже залочен. Выполняем следующую команду: # touch /vmfs/volumes/ / / Если файл уже залочен, мы получим вот такое сообщение для него: cannot touch: Device or resource busy Дальше выполняем такую команду: # vmkfstools -D /vmfs/volumes/ / / В значении «owner» мы видим MAC-адрес залочившего файл хоста VMware ESXi (выделено красным). Ну а как узнать MAC-адрес хоста ESXi — это вы должны знать. Дальше просто делаем Cold Migration виртуальной машины на залочивший файл хост ESXi и включаем ее там. Те, кто хочет дальше изучать вопрос, могут проследовать в KB 10051. Чтобы оставлять комментарии, вы должны быть зарегистрированы на сайте.

Подписаться по e-mail: Вебинары VMC о виртуализации: Постер VMware vSphere PowerCLI 6.3: Постер VMware ESXi 5.1: Постер VMware Hands-on Labs 2015: Постер VMware Platform Services Controller 6.0: Постер VMware vCloud Networking: Постер VMware NSX (референсный): Постер VMware vCloud SDK: Постер VMware vCloud Suite: Постер VMware vCenter Server Appliance: Порты и соединения VMware vSphere 6: Порты и соединения VMware Horizon 7: Порты и соединения VMware NSX: Управление памятью в VMware vSphere 5: Как работает кластер VMware High Availability: Постер VMware vSphere 5.5 ESXTOP (обзорный): Постер Veeam Backup & Replication v8 for VMware: Постер Microsoft Windows Server 2012 Hyper-V R2: Источник Error caused by file vmfs volumes vmdk I have tried to query the changed disk area(QueryChangedDiskAreas) of a VM through Managed Object Browser(mob) [ reference : How to find or validate Change Block Tracking results returned by VMware API | My Space] But for a Vm it returns FileFault error. I have already tried the steps mentioned in the following Vmware KB article [VMware KB: QueryChangedDiskAreas API call returns a FileFault error ]. But still the issue is persist. Why it is happening and how to solve this issue? Any help on this is very much appreciated. Mark as New Bookmark Subscribe Mute Subscribe to RSS Feed Permalink Print Report Inappropriate Content Does the FileFault error only occur via the MOB or also when calling QueryChangedDiskAreas through your code? Mark as New Bookmark Subscribe Mute Subscribe to RSS Feed Permalink Print Report Inappropriate Content First i have tried through my code.,It is throwing the following error «Error caused by file /vmfs/volumes/e24134fd-e433sdw2/samplevm/samplevm.vmdk» That’s why i have tried through MOB Note: The datastore which is having the problematic VM is a NFS datastore. Mark as New Bookmark Subscribe Mute Subscribe to RSS Feed Permalink Print Report Inappropriate Content Note: The datastore which is having the problematic VM is a NFS datastore. Outch, that seems to be it. KB Article Changed Block Tracking (CBT) on virtual machines states: For CBT to identify altered disk sectors since the last change ID , the following items are required: I/O operations must go through the ESX/ESXi storage stack. So NFS is supported , as is RDM in virtual compatibility mode, but not RDM in physical compatibility mode. Of course VMFS is supported, whether backed by SAN, iSCSI, or local disk. Note that they require a change ID for this to work. Further down it reads: For CBT to identify disk sectors in use with the special «*» change ID , the following items are required: The virtual disk must be located on a VMFS volume , backed by SAN, iSCSI, or local disk. RDM is not VMFS My interpretation of this is the «*» is not supported on NFS volumes. So if the disk is located on a NFS volume you will have to backup the entire disk. To check whether you problem is really related to the «*» on NFS volumes you could try to invoke QueryChangedDiskAreas via the MOB but specify a concrete changeId. If it works with the concrete Id the «*» on NFS volumes restriction is suggested to be your issue. To check whether the disk in question is located on a NFS volume I propose using property chain VirtualDisk.backing(VirtualDeviceFileBackingInfo).datastore.summary.type = vmfs | nfs | cifs | vfat Please let me know whether things are working out. Источник Adblock detector