- VMware Technology Network
- :
- Cloud & SDDC
- :
- VMware vSphere
- :
- VMware vSphere™ Discussions
- :
- Re: Vsan datastore can not replication and datasto...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Vsan datastore can not replication and datastore vmotion
hi dear
i tried vreplication and always got stuck at 99%.
than i tried move that vm to local datastore from vsan
got failed too.
this is error i got
019-05-17T10:47:41.865Z| worker-2140032| I125: MigrateSetState: Transitioning from state 2 to 3.
2019-05-17T10:47:41.866Z| worker-2140032| I125: Hostlog_AddCleanupItem: Ignoring attempt to re-add /vmfs/volumes/vsan:5291004cbefa81cd-64a90c118c7103cc/0434365c-d3ae-d6d5-acca-000e1e9e52a0/vdi2.nvram.
2019-05-17T10:47:41.875Z| worker-2140032| I125: UTIL: Change file descriptor limit from soft 4211,hard 4211 to soft 8422,hard 8422.
2019-05-17T10:47:41.875Z| worker-2140032| I125: SVMotion: Enter Phase 2
2019-05-17T10:47:41.875Z| worker-2140032| I125: SVMotionDiskGetCreateExtParams: not using a storage policy to create disk '/vmfs/volumes/5c0f7ca7-5ab513ba-9e2f-001e67f76712/vdi2/vdi2_4.vmdk'
2019-05-17T10:47:41.875Z| worker-2140032| I125: DISKLIB-LIB_CREATE : CREATE: "/vmfs/volumes/5c0f7ca7-5ab513ba-9e2f-001e67f76712/vdi2/vdi2_4.vmdk" -- vmfs capacity=167772160 (80 GB) adapter=lsilogic info=cowGran=0 allocType=1 objType= policy=''
2019-05-17T10:47:41.875Z| worker-2140032| I125: DISKLIB-LIB_CREATE : CreateObjExtParams: Object backing type 0 is invalid. Figuring out the most suitable backing type...
2019-05-17T10:47:41.875Z| worker-2140032| I125: DISKLIB-LIB_CREATE : CREATE: Creating disk backed by 'file'
2019-05-17T10:47:41.884Z| worker-2140032| I125: DISKLIB-DSCPTR: "/vmfs/volumes/5c0f7ca7-5ab513ba-9e2f-001e67f76712/vdi2/vdi2_4.vmdk" : creation successful.
2019-05-17T10:47:41.892Z| worker-2140032| I125: DISKLIB-VMFS : "/vmfs/volumes/5c0f7ca7-5ab513ba-9e2f-001e67f76712/vdi2/vdi2_4-flat.vmdk" : open successful (1) size = 85899345920, hd = 0. Type 3
2019-05-17T10:47:41.897Z| worker-2140032| I125: DISKLIB-VMFS : "/vmfs/volumes/5c0f7ca7-5ab513ba-9e2f-001e67f76712/vdi2/vdi2_4-flat.vmdk" : closed.
2019-05-17T10:47:41.908Z| worker-2140032| I125: SVMotion: Enter Phase 3
2019-05-17T10:47:41.909Z| worker-2140032| I125: DISKLIB-VMFS : "/vmfs/volumes/5c0f7ca7-5ab513ba-9e2f-001e67f76712/vdi2/vdi2_4-flat.vmdk" : open successful (33290) size = 85899345920, hd = 4011516. Type 3
2019-05-17T10:47:41.909Z| worker-2140032| I125: DISKLIB-DSCPTR: Opened [0]: "vdi2_4-flat.vmdk" (0x820a)
2019-05-17T10:47:41.909Z| worker-2140032| I125: DISKLIB-LINK : Opened '/vmfs/volumes/5c0f7ca7-5ab513ba-9e2f-001e67f76712/vdi2/vdi2_4.vmdk' (0x820a): vmfs, 167772160 sectors / 80 GB.
2019-05-17T10:47:41.909Z| worker-2140032| I125: DISKLIB-LIB : Opened "/vmfs/volumes/5c0f7ca7-5ab513ba-9e2f-001e67f76712/vdi2/vdi2_4.vmdk" (flags 0x820a, type vmfs).
2019-05-17T10:47:41.933Z| worker-2140032| I125: DDB: "longContentID" = "4f216422ff0bb1be17680ee0fc907929" (was "354121c226dffb5146952353fffffffe")
2019-05-17T10:47:41.953Z| worker-2140032| I125: DDB: "uuid" = "60 00 C2 97 4d 72 6d f8-25 e7 77 c6 e1 f3 88 54" (was "60 00 C2 9e 5c d6 d6 1e-dc 76 88 8e 81 f6 02 e2")
2019-05-17T10:47:41.959Z| worker-2140032| I125: SVMotionLocalDiskQueryInfo: Got block size 1048576 for filesystem VMFS.
2019-05-17T10:47:41.959Z| worker-2140032| I125: SVMotion: Enter Phase 4
2019-05-17T10:47:41.978Z| worker-2140032| I125: SVMotion: Enter Phase 5
2019-05-17T10:47:41.978Z| worker-2140032| I125: SVMotion: Enter Phase 6
2019-05-17T10:47:41.979Z| worker-2140032| W115: OBJLIB-VSANOBJ: VsanObjGetUPITUriList: Object vsan://0434365c-d3ae-d6d5-acca-000e1e9e52a0 does not have UPIT capability.
2019-05-17T10:47:41.981Z| vcpu-0| I125: Destroying virtual dev for scsi0:0 vscsi=8250
2019-05-17T10:47:41.981Z| vcpu-0| I125: VMMon_VSCSIStopVports: No such target on adapter
2019-05-17T10:47:42.024Z| vcpu-0| W115: VMCI: It is FSR migrate and setting migrate cid to -1589052490
2019-05-17T10:47:42.027Z| worker-2140032| I125: DISKLIB-LIB_MISC : Opening mirror node /vmfs/devices/svm/1093a6-3d35fc-svmmirror
2019-05-17T10:47:42.027Z| worker-2140032| I125: SVMotion: Enter Phase 7
2019-05-17T10:47:42.027Z| worker-2140032| I125: Checkpoint_Unstun: vm stopped for 48730 us
2019-05-17T10:47:42.027Z| vcpu-0| I125: SCSI: switching scsi0 to push completion mode
2019-05-17T10:47:42.027Z| vcpu-0| I125: Creating virtual dev for 'scsi0:0'.
2019-05-17T10:47:42.027Z| vcpu-0| I125: DumpDiskInfo: scsi0:0 createType=11, capacity = 167772160, numLinks = 1, allocationType = 2
2019-05-17T10:47:42.027Z| vcpu-0| I125: SCSIDiskESXPopulateVDevDesc: Using FS backend
2019-05-17T10:47:42.027Z| vcpu-0| I125: DISKUTIL: scsi0:0 : geometry=10443/255/63
2019-05-17T10:47:42.057Z| vcpu-0| I125: SCSIFilterESXAttachCBRCInt: CBRC not enabled or opened without filters,skipping CBRC filter attach.
2019-05-17T10:47:42.057Z| vcpu-0| I125: SCSIFilterSBDAttachCBRC: device scsi0:0 is not SBD. Skipping CBRC attach SBD way.
2019-05-17T10:47:42.058Z| vcpu-0| I125: VMXNET3 user: Ethernet0 Driver Info: version = 7724565 gosBits = 2 gosType = 2, gosVer = 40960, gosMisc = 212
2019-05-17T10:47:42.058Z| vcpu-0| W115: OBJLIB-VSANOBJ: VsanObjGetUPITUriList: Object vsan://0434365c-d3ae-d6d5-acca-000e1e9e52a0 does not have UPIT capability.
2019-05-17T10:47:42.058Z| worker-2140032| I125: SVMotion: Enter Phase 8
2019-05-17T10:47:42.058Z| worker-2140032| I125: Disk/File copy started for /vmfs/volumes/vsan:5291004cbefa81cd-64a90c118c7103cc/0434365c-d3ae-d6d5-acca-000e1e9e52a0/vdi2_4.vmdk.
2019-05-17T10:47:42.059Z| vthread-2340169| I125: VTHREAD 590542583552 "vthread-2340169" wid 2340169
2019-05-17T11:00:29.411Z| vmx| W115: Mirror: scsi0:0: Failed to copy disk: Checksum mismatch
2019-05-17T11:00:29.411Z| worker-2140032| W115: SVMotionMirroredModeThreadDiskCopy: Found internal error when woken up on diskCopySemaphore. Aborting storage vmotion.
2019-05-17T11:00:29.411Z| worker-2140032| W115: SVMotionCopyThread: disk copy failed. Canceling Storage vMotion.
2019-05-17T11:00:29.411Z| worker-2140032| I125: SVMotionCopyThread: Waiting for SVMotion Bitmap thread to complete before issuing a stun during migration failure cleanup.
2019-05-17T11:00:29.413Z| worker-2140032| W115: OBJLIB-VSANOBJ: VsanObjGetUPITUriList: Object vsan://0434365c-d3ae-d6d5-acca-000e1e9e52a0 does not have UPIT capability.
2019-05-17T11:00:29.413Z| worker-2140032| I125: SVMotion: FailureCleanup thread completes.
2019-05-17T11:00:29.413Z| vmx| I125: SVMotion: Worker thread performing SVMotionCopyThreadDone exited.
2019-05-17T11:00:29.424Z| vmx| I125: MigrateSetStateFinished: type=1 new state=6
2019-05-17T11:00:29.424Z| vmx| I125: MigrateSetState: Transitioning from state 3 to 6.
2019-05-17T11:00:29.424Z| vmx| A100: ConfigDB: Setting config.readOnly = "FALSE"
2019-05-17T11:00:29.424Z| vmx| I125: Migrate_SetFailureMsgList: switching to new log file.
2019-05-17T11:00:29.424Z| vmx| I125: FILE: FileCreateDirectoryEx: Failed to create /tmp. Error = 17
2019-05-17T11:00:29.424Z| vmx| I125: FILE: FileCreateDirectoryEx: Failed to create /tmp/vmware-root. Error = 17
2019-05-17T11:00:29.424Z| vmx| I125: Migrate_SetFailureMsgList: Now in new log file.
2019-05-17T11:00:29.424Z| vmx| I125: Migrate: Caching migration error message list:
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As I told you here, for detailed log analysis if you're not going to explain your situation, open an SR. This also represents essentially a triple post, so please stop posting the same thing multiple times.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
sorry for my triple post.
i just digging all problem to resolve my trouble.