Storage vMotion Failed - Help!

Similar Questions

• Storage vMotion fails with the error below

  I'm trying to run a virtual machine's storage vMotion. It fails with the error below.

  This method is disabled by 'moref = 17705'

  #1 method - manually remove the entry from the VCDB.

  • Stop the Service of VC.
  • Connect to the SQL Instance.
  • Run the SQL for VCDB.
  • Select * from VPX_VM WHERE name LIKE '% VM_Name % '.
  • Note the ID of VM in column 1.
  • Validate the stale entry.

  Select * from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = "vm - ID".

  • Remove obsolete entries.

  delete from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = "vm - ID"

  • Start the VC service.
  • Try Storage vMotion.

  Method #2-si this does not work, save the *.vmx file once again which will fix the problem.

  Note: To do this, you will be required to server unavailability.

  • Power off the virtual computer.
  • VM unregistered inventory.
  • Navigate to the path of the data store and VMX re-register.
  • Start the virtual computer.
  • Try Storage vMotion.

• Storage test 55 certification vmotion, storage vmotion fails with "Could not lock file" on the virtual machine during storage vmotion

  In my view, that it is a known problem in ESXi 5.5 Update 2 release notes, someone knows a solution yet? This is an excerpt from the release notes:

  • Attempts to perform live storage vMotion of virtual machines with RDM disks can fail
    Storage vMotion of virtual machines with RDM disks can fail and virtual machines can be considered in turned off of the State. Attempts to turn on the virtual machine fails with the following error:
    
    Cannot lock the file
    
    Workaround: No.

  VMware support for the record said that the patch will update 3, it is known as an intermittent problem. Finally, it happened to me on the 9th attempt.

• Storage Vmotion failed now VM in limbo

  I was migrating a virtual computer by using the plugin SVmotion who got 90% then failed, and now I can not restart. I have the two stil of vmdk files in their original location, but also two dmotion * vmdk files. Nondurable urgent to return this virtual machine running would be highly appreciated.

  Hello, check these two articles, those who should be able to help solve the problem:

  http://www.van-Lieshout.com/2009/03/how-to-recover-from-failed-SVMotion/

  http://blog.core-it.com.au/?p=441

  If this post was useful/solved your problem, please mark the points of wire and price as seem you. Thank you!

• Storage VMotion failed - LUN "Ongoing resource of use"

  I had a VM, sitting on an oversized LUN, so I reduced the size of the LUN.  The result is a corrupt VMDK.  It's nice that I can rebuild not the end of the world.  The problem is that when I right click on the virtual machine, that it only allows me to "Migration complete" - I can't delete the virtual machine.  If I select a full Migration it will fail to 33% with the error "the virtual disk is either corrupt or not a format supported."  If I tried to remove the source LUN or destination LUN I get an error "resource is in use.  So my question is how do I get rid of this virtual machine and these LUNS so I can start again.

  I'm on ESX 3.5 U4 on CF to FAS2020. Let me know if you need more information.  Thanks for any help!

  Always disconnect shows upward in the inventory.  This part of a cluster?  Disconnect the server. Remove the host ESX to vCenter.  Then, add it in.  Sometimes, remove the server from the cluster is enough, but you may need to remove the vCenter server.

  -KjB

  VMware vExpert

• Storage vMotion with Syncrep on Equallogic San

  Hello

  We recently bought 2 San Equallogic (PS6510ES) and turned on synchronous replication between them.

  We use ESXi 5.5 and followed the best practices guide to disable TCP ack and 60 logintimeout value.

  Everything seems to work fine until we tried Storage vMotion/migration and cloning VMS on the San.

  When we did the migration of 2 volumes on the EQL SAN storage (the target volume has active syncrep), the target volume will be out-of-sync and then the storage vMotion will hang sometimes.

  The worst is when such a problem has occurred, all other volumes on the EQL constantly to respond also. All volumes will not respond until we rebooted the corresponding ESXi host (NOTE: simple shut down/power outside the host won't help.) The San EQL will only return to normal after a reboot of the ESXi host).

  If we pause / off the syncrep before Storage vMotion, the problem will not happen.

  Is this normal or not?

  In addition, whenever the problem occurred, the latency of writing the corresponding volume will be dry and we will receive alerts similar to the following:

  connection iSCSI target ' xx.xx.xx.xx:3260, iqn.2001 - 05.com.equallogic:xxxxx - test-volume ' initiator 'xx.xx.xx.xx:xxxxx, eqlinitiatorsyncrep' failed for the following reason:

  Initiator, disconnected from the target when connecting.

  Thanks in advance.

  Hi Joerg,

  What is a #SR? I opened a record of support to 24 June and still waiting for Dell to contact me.

  Ryan

• VMotion fails with «Host CPU is incompatible...» »

  After setting our vCenter 4 / environment laboratory of ESX 4 with two hosts ESX 4, I added two of our ESX 3.5 hosts in vCenter 4 managed environment. These 3.5 hosts had 10 Windows 2003 EE 64-bit Server identical virtual machines, running on them. I then used storage vMotion (migration) to move all ten VMs over a LUN share by the ESX 4 hosts and migrate them while they are now running on the ESX 4 hosts.  They came over the fine. Activated fine. Ran very well. vMotioned back between the two ESX 4 hosts fine.

  I then put off 5 of the 10 computers virtual and enhanced their virtual hardware version 4 to version 7. I have them fed up.

  I have also built several new virtual machines on the host ESX 4 from scratch using the same process and the same image that I used to create virtual machines hosted on ESX 3.5 hosts. So far so good.  Can I vMotion between all 5 virtual machines that are still at version 4 guests two ESX 4 and I can vMotion new computers virtual 7 built on ESX4 host, but if I try to vMotion of 5 virtual machines have been upgraded to version 7, I get the message below.

  Host CPU is incomaptible with the requirements of the virtual machine to CPUID level 0 x 1 register 'cex '.
  Bits of the host: 0000:0000:0000:0000:0010:0000:0001
  Required: 1000:0000:0000:000 x: x 10 xx10:0: xxx0:x 001
  Inconsistency detected for these features:
  * General incompatibilities; see section 1993 of possible solutions.

  I read the KB article referenced, but this is to overcome the problems with fast vMotioning between levels or different processor types. These two hosts ESX 4 (10-esx-mp and mp-esx-11) are identical DL580 G5. It's only the improved VMs that fail to migrate.

  I stop each host ESX 4, restarted in the BIOS and set the option of VT processor on 'disable', of booted up the box, let it come completely up, then again, rebooted the box of ebb in BIOS and by setting the option VT back on 'enable '. It's not helping.

  Someone else has seen this?

  If you have identical CPU, then check the configuration of virtual machine (in the .vmx file) to see if there is an old CPUID mask value and simply remove them.

  Then again turn on the virtual machine.

  See also:

  http://KB.VMware.com/kb/1993

  André

• Storage VMotion - a general error occurred: could not wait for the data.  Error bad0007.

  People,

  I searched through this forum and have not found an answer that works in many positions out there, I say to myself that I would ask him once again.

  Here's the context:

  We have 12 identical Dell M600 blades in 2 chassis with 16 GB of Ram, 2 x Xeon E5430, they are all connected to an Equallogic PS 5000XV iSCSI SAN on a separate iSCSI (vswitch1) with 2 cards network dedicated network and dedicated switch, console svc iscsi dedicated, dedicated VMkernel port for iscsi access. Net access (vswitch0) contains port groups VM for our various networks and a console port and vmkernel svc for VMotion with 2 separate NETWORK cards as well.

  We are running ESX 3.5 U3 and VCenter 2.5 U3 on Win2k3 R2

  VMotion works between all servers, Storage Vmotion works for most machines, HA works and the value 2 host failurs with no monitoring of vm, DRS is set to manual for now I have a few machines on the local stores that I complete my rebuilt LUN, there is no set of rules for DRS and VMware EVC is enabled for guests of the Intel. However, I'll just describe one machine to do svmotion below.

  Here's the problem:

  I'm trying to Svmotion via svmotion.pl - interactive, a Machine to Windows 2000 with a virtual disk and a virtual RDM. I am aware of the requirements for the RDM and required parameters for svmotion, independent is not selected for the RDM, and I also have svmotioned several machines linux and win2k3 with the same configuration without problem. In the interactive session, I choose to individually place the disks and I chose the virtual disk to only the virtual machine to be moved, essentially, as I saw it move vdisk virtual machine and then copy to the pointer of the RDM.

  The use of the processor in this machine is about 25% average. but I try to run migrations at the time the lowest. and The Host it itself shows only about 5.5 GB of the 16 GB of RAM used. so I think we're good on the RAM. the volume/datastore that I'm migrating from has 485 GB free and the volume/datastore I migration towards a 145 GB free. the VM virtual disk is only about 33 GB.

  I run the script the windows version of the RCLI svmotion. and when to begin the process, I get the following error at around 2 percent of the progress:

  "Since the server has encountered an error: a general error occurred: could not wait for the data."  Error bad0007. Invalid parameter. »

  After searching around, I found the following hotfixes to the U2 release notes

  • Migrate.PageInTimeoutResetOnProgress: Set the value to 1.

  • Migrate.PageInProgress: The value 30, if you get an error even after the setting of the Migrate.PageInTimeoutResetOnProgress variable.

  I've made these changes, and I still get the same error.

  When I dig in the newspaper, I see these entries in the journal of vmkwarning:

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu4:1394) WARNING: bunch: 1397: migHeap0 already at its maximumSize bunch. Cannot extend.

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu4:1394) WARNING: bunch: 1522: Heap_Align (migHeap0, 1030120338/1030120338 bytes, 4 align) failed.  calling: 0x988f61

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu4:1394) WARNING: migrate: 1243: 1235452646235015: failure: out of memory (0xbad0014) @0x98da8b

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu2:1395) WARNING: MigrateNet: 309: 1235452646235015: 5 - 0xa023818: sent only 4096 bytes of data in message 0: Broken pipe

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu6:1396) WARNING: migrate: 1243: 1235452646235015: failed: Migration protocol error (0xbad003e) @0x98da8b

  (Feb 24 00:17:32 vmkernel iq-virt-c2-b6: 82:04:13:56.794 cpu2:1395) WARNING: migrate: 6776: 1235452646235015: could not send data for 56486: Broken pipe

  At this point, I'm stuck... What is Windows RCLI? the vcenter Server? or the service console with not enough of RAM? We have already increased all our consoles service 512 MB...

  Any help would be greatly appreciated...

  Thanks in advance.

  Alvin

  The vmkernel on out of memory error, I had that before. And vmware support recommends setting 800M Max service console memory. And I did it and have no problems after that.

  See if that helps the issue.

  Mike

• problem with babylon runing on windows 8-storage initialization failed (error 10)

  problem with babylon runing on windows 8-storage initialization failed (error 10)

  Hi Shlomy,

  1. when exactly you get the error message?
  2. do you have an error message?
  3. are install you authentic version of Babylon?

  This issue would have occurred due to some third-party programs, the origin of the problem. I suggest you perform the clean boot. Clean boot helps eliminate conflicts of software that occur when you install a program or an update or when you run a program in Windows. You can also troubleshoot or determine what conflict is causing the problem by performing a clean boot.

  How to perform a clean boot in Windows
  http://support.Microsoft.com/kb/929135

  Note: Follow How to reset the computer to start as usual after a clean boot troubleshooting article KB929135 to reset the computer in normal mode.

  If the problem only occurs with babylon click here to send a request to the Babylon 8 support team.

  Post us the results after trying the steps above.

• Storage vmotion very slow

  Storage vmotions run very slowly. The virtual machine that has a 60 GB HARD drive. I tried different storage and still the same result. I have even upgraded to a network of 10 GB with the same results. I opened an evidence of support and the engineer told me vmotion will not use the link in full speed but it seems quite slow for the numbers I get. I hope I have provided enough information below for assistance. I hope that it is something I am doing wrong...

  Hosts:

  3 x ESXi host. Two are updated to version 6.0 1 and a version 5.5.

  Dell PowerEdge R610

  Xeon E5540 - 8 x 2.53GHz

  48 GB OF RAM

  10 GB for storage and vmotion traffic

  4 x 1 Gb NIC for vm traffic interconnection

  All storage is on the shared storage. The only local thing is the operating system

  VMware EVC mode for the production of Intel's Nehalem.

  Storage

  Supermicro NAS 2 to 4 x 4 RAID 10 storage pools

  Integrated 10 GB NIC

  QNAP TS - 469U - PR to 4 x 4 RAID 5 NAS

  2 x 1 GB NIC aggregated link

  Network

  All 3 hosts and NAS are connected with a Netgear dedicated 10 GB switch (low-end model).

  Using a standard vswitch

  Problem

  1 ESXi host has a computer virtual stored on storage on NAS Supermicro 1 pool. When a storage vmotion is running on a virtual machine that has a 60 GB VMDK, it takes a long time to complete. He started at 09:36, and is now 61% fine at 10:58.

  2. the network of 10 GB is where the vmotion traffic is allowed.

  3. If I use a link to 10 GB or a 1 GB link, I get the same speed.

  4. I have disabled all VM at a time given for the trial and who has not helped either.

  5. I tried a QNAP so storage vmotion, and I get the same speed.

  I use connection CAT6A cables. I have fine tuned for storage, and it seems to work better now. Seems to be linked to "writing - sync" as ESXi.

• Storage vmotion esxi 5.5 to 6.0 does not not for some vm

  In a test cluster with 2 nodes with no storage storage shared (local only), host vmotion 5.5 to 6.0 host does not work.

  before the upgrade, I moved all the vm to a host.

  Then I upgraded to 6.0 host and tried to move all the VMS to the host 6.0 updated (moving host + storage).

  20 VM, 5 have been moved to the new host.

  Everyone always get error below.

  The VM Client are all the vm version 10 (but some of them improved 8 or 9).

  ClientOS Windows 2008, 2012 r2 and linux. Some with vmx3, some with e1000.

  The machines can be moved when turned off.

  After the off-vmotion, storage vmotion from 6 to 5.5 and return of 5.5 to 6 works again.

  < code >

  Failed to copy one or more of the disks in the virtual machine. See the journal of the virtual machine for more details.

  Impossible to implement disks on the destination host computer.

  vMotion-Migration [-1408040447:1427943699552189] konnte nicht den Stream-Keepalive read: Connection closed by remote host, probably due to timeout

  Beim Warten auf Daten Fehlgeschlagen. Fehler 195887167. Connection closed by remote host, probably due to delay.

  < code >

  VM - log:

  < code >

  2015-04 - T 02, 03: 01:34.299Z | VMX | I120: VMXVmdb_SetMigrationHostLogState: transits State hostlog of immigration to migrate "at source" mid 1427943699552189

  2015-04 - T 02, 03: 01:34.307Z | VMX | I120: MigratePlatformInitMigration: file DiskOp set to /vmfs/volumes/526d0605-8317b046-f37e-0025906cd27e/test1/test1-diskOp.tmp

  2015-04 - T 02, 03: 01:34.311Z | VMX | A115: ConfigDB: parameter migration.vmxDisabled = 'TRUE '.

  2015-04 - T 02, 03: 01:34.326Z | VMX | I120: MigrateWaitForData: waiting for data.

  2015-04 - T 02, 03: 01:34.326Z | VMX | I120: MigrateSetState: transition of State 8 to 9.

  2015-04 - T 02, 03: 01:34.467Z | VMX | I120: MigrateRPC_RetrieveMessages: was informed of a new message to the user, but cannot process messages from State 4.  Leaving the message in queue.

  2015-04 - T 02, 03: 01:34.467Z | VMX | I120: MigrateSetState: transition of State 9 to 10.

  2015-04 - T 02, 03: 01:34.468Z | VMX | I120: MigrateShouldPrepareDestination: remote host does not support an explicit step to prepare migration destination.

  2015-04 - T 02, 03: 01:34.469Z | VMX | I120: MigrateBusMemPrealloc: BusMem complete pre-allocating.

  2015-04 - T 02, 03: 01:34.469Z | Worker #0 | I120: SVMotion_RemoteInitRPC: completed.

  2015-04 - T 02, 03: 01:34.471Z | Worker #0 | W110: SVMotion_DiskSetupRPC: related disc expected but not found for the file: /vmfs/volumes/526d0605-8317b046-f37e-0025906cd27e/test1/test1-ctk.vmdk

  2015-04 - T 02, 03: 01:34.471Z | Worker #0 | W110: MigrateRPCHandleRPCWork: callback RPC DiskSetup returned UN-successful State 4. RPC fault.

  2015-04 - T 02, 03: 01:34.493Z | VMX | I120: VMXVmdb_SetMigrationHostLogState: hostlog transits of State to fail to migrate 'from' 1427943699552189 environment

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: MigrateSetStateFinished: type = 2 new State = 12

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: MigrateSetState: transition of State 10 to 12.

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: Migrate: list cached migration error message:

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: [msg.migrate.waitdata.platform] failed waiting for data.  Error bad003f. Connection closed by remote host, probably due to delay.

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: migration of vMotion [vob.vmotion.stream.keepalive.read.fail] [ac130201:1427943699552189] failed to read streams keepalive: Connection closed by remote host, probably due to timeout

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: Migrate: cleaning of the migration status.

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: SVMotion_Cleanup: cleaning of XvMotion State.

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: Closing all disks in the virtual machine.

  2015-04 - T 02, 03: 01:34.504Z | VMX | I120: Migrate: Final status, who reported the force.

  2015-04 - T 02, 03: 01:34.504Z | VMX | I120: MigrateSetState: transition of the State 12-0.

  2015-04 - T 02, 03: 01:34.505Z | VMX | I120: Migrate: Final status, which reported VMDB.

  2015-04 - T 02, 03: 01:34.505Z | VMX | I120: Migrate Module switch has failed.

  2015-04 - T 02, 03: 01:34.505Z | VMX | I120: VMX_PowerOn: ModuleTable_PowerOn = 0

  2015-04 - T 02, 03: 01:34.505Z | VMX | I120: SVMotion_PowerOff: does not not Storage vMotion. Nothing to do

  2015-04 - T 02, 03: 01:34.507Z | VMX | A115: ConfigDB: parameter replay.filename = «»

  2015-04 - T 02, 03: 01:34.507Z | VMX | I120: Vix: [291569 mainDispatch.c:1188]: VMAutomationPowerOff: power off the power.

  2015-04 - T 02, 03: 01:34.507Z | VMX | W110: /vmfs/volumes/526d0605-8317b046-f37e-0025906cd27e/test1/test1.vmx: cannot remove a link symbolic/var/run/vmware/root_0/1427943694053879_291569/configFile: no such file or directory

  2015-04 - T 02, 03: 01:34.507Z | VMX | I120: WORKER: asyncOps = 4 maxActiveOps = 1 maxPending = 0 maxCompleted = 0

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Vix: [291569 mainDispatch.c:4292]: VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1873, success = 1 additionalError = 0

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Vix: [291569 mainDispatch.c:4292]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1 additionalError = 0

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Past vmx/execState/val of poweredOff

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Vix: [291569 mainDispatch.c:4292]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 0 additionalError = 0

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Vix: [291569 mainDispatch.c:4331]: error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): unknown error

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Vix: [291569 mainDispatch.c:4292]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1 additionalError = 0

  < code >

  Any idea to solve this problem? Maybe it's a bug with vsphere 6.0

  Given that some machines were functioning and vmotion later in both directions from 6.0 to 5.5 works, I think that is no configuration error.

  Hello

  It seems that there could be a bug or that guests have difficulties to negotiate the transfer of drive on a network. VMotions storage are carried out via the management network (limitation of hard due to the codification)-are you sure that management networks are not overloaded or that they operate at the desired speed? This also happens with machines that have actually disabled followed block? It seems that this could be a problem.

  In addition, you use the 'old' client or Web client? It is possible that some features in vSphere 6.0 may have been omitted in the old thick client.

  Below are the errors:

  2015-04 - T 02, 03: 01:34.468Z | VMX | I120: MigrateShouldPrepareDestination: remote host does not support an explicit step to prepare migration destination.

  2015-04 - T 02, 03: 01:34.471Z | Worker #0 | W110: SVMotion_DiskSetupRPC: related disc expected but not found for the file: /vmfs/volumes/526d0605-8317b046-f37e-0025906cd27e/test1/test1-ctk.vmdk

  Thanks for the answers in advance and good luck!

• Storage vmotion, between data warehouses when the block size is different

  Hi all

  I would like to know, is it possible to do a vmotion of storage between two data warehouses, when they have different block sizes. The case is as a former vmfs data store 3 which has been upgraded direct to vmfs5 there, but since it has been updated it maintains its own block size. While the newly created vmfs datastore 5 a block size of 1 MB.

  Thus, storage Vmotion will work in this case? It will fail OR will be with degraded performance?

  Finally, storage vmotion is possible even if you do not have a cluster DRS for storage?

  Thank you

  Yes you can!

  Check some info on the effects of block size: http://www.yellow-bricks.com/2011/02/18/blocksize-impact/

• Storage vmotion of storage facilities to storage San in ESXi 5.0

  Hello

  I have the host couple ESXi 5.0 with license free of all is vmdk are located in storage facilities. Moving all the vm for local to the SAN storage data store, but the local data store attached failed to attend several ESX host as storage shared, is there a way that allow me to use the method of storage vmotion to migrate all the vmdk to centralize SAN without interruption?

  I have a vcenter to manage whole army but only for normal administrative task. How can I set the local data store storage shared storage and able to present multiple hosts?

  Hello

  Do you have the vSphere licenses?
  If so, you can add the vCenter ESXi hosts, present SAN storage for ESXi hosts and perform Storage vMotion (migrate the data store) local storage to SAN storage.

  You will need because the function of storage vMotion (migrate) is a feature of vCenter vCenter, this option is not available in standalone ESXi.

  See the documentation here - migration of Virtual Machines with svmotion: vSphere Documentation Center

  If you can accept interruptions of service, you can use the migration cold: vSphere Documentation Center

  Thank you

  Bayu

• Storage vMotion allows automatic failover to the replicated copy?

  With vSphere replication allow "Storage vMotion" automatic failover to the copy replicated in case of a failure of the data store?

  Trying to figure out a solution where if A SAN fails, we can install SAN B to pick up without any interruption of service.

  Welcome to the community - Storage vMotion does not provide this type of functionality, you will need to get to the VMware Site Recovery Manager (SRM), but it will be some time - failure

• Storage vMotion - Shadow created VM!

  Hello

  I cancelled a task of storage for a virtual machine vMotion and now I have two virtual machines with the same name. I understand Storage vMotion creates a shadow VM as part of the migration.

  The cancellation has not been cleaned so I now a VM THAT under tension and work and a VM turned off with 0MB of data warehouses.

  Is it OK to goahead and remove this 'Shadow' VM?

  I look forward to hear from anyone with help.

  Thank you

  Peter.

  I guess, there is no problem.

  Just remove the inventory and then delete the folder.