keerthyt
Contributor
Contributor

QueryDiskChangedAreas and QueryAllocatedBlocks fails with FileFault : ESXMapperGetPhysicalMapping: Failed to get physical mapping: 190004 Inappropriate ioctl for device

On a ESXi 5.5 we are trying to take snapshot and read the changes while CBT is enabled on VM. The API fails to give the information and throws a FileFault. Following are the error lines that I see in vmware log:

DISKLIB-CTK   : Auto blocksize for size 230686720 is 128.

DISKLIB-CTK   : Auto blocksize for size 377487360 is 256.

DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 1505332471.

DISKLIB-CBT   : Successfuly created cbt node 59b98cf7-cbt.

DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/59b98cf7-cbt

OBJLIB-FILEBE : FileBEIoctl: ioctl operation failed on '/vmfs/devices/cbt/59b98cf7-cbt' : Inappropriate ioctl for device (1638402)

ESXMapperGetPhysicalMapping: Failed to get physical mapping: 190004 Inappropriate ioctl for device

DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 1406045430.

DISK: Change tracking for disk scsi0:0 is now enabled.

DISKLIB-CBT   : Successfuly created cbt node 53ce8cf6-cbt.

DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/53ce8cf6-cbt

OBJLIB-FILEBE : FileBEIoctl: ioctl operation failed on '/vmfs/devices/cbt/53ce8cf6-cbt' : Inappropriate ioctl for device (1638402)

ESXMapperGetPhysicalMapping: Failed to get physical mapping: 190004 Inappropriate ioctl for device

0 Kudos
5 Replies
continuum
Immortal
Immortal

Good case:

only one name-cbt.vmdk is damaged.
Disable cbt-block-tracking for that VM.
Stop backup-jobs for that VM.
Delete job.
Delete all cbt.vmdk of that VM.

Start VM again.
Create new job and create a full backup on first run.
Worst case:
this is just a symptom of a serious corruption of your datastore.

But you would have noticed that ....

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
keerthyt
Contributor
Contributor

Thank you for your response. Will try out and reply back.

Firstly looks like both the disks have the issue, not only one. Following is the log with failure for both the disks:

DISKLIB-CTK   : Auto blocksize for size 230686720 is 128.

DISKLIB-CTK   : Auto blocksize for size 377487360 is 256.

DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 1505332471.

DISKLIB-CBT   : Successfuly created cbt node 59b98cf7-cbt.

DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/59b98cf7-cbt

OBJLIB-FILEBE : FileBEIoctl: ioctl operation failed on '/vmfs/devices/cbt/59b98cf7-cbt' : Inappropriate ioctl for device (1638402)

ESXMapperGetPhysicalMapping: Failed to get physical mapping: 190004 Inappropriate ioctl for device

DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 1406045430.

DISK: Change tracking for disk scsi0:0 is now enabled.

DISKLIB-CBT   : Successfuly created cbt node 53ce8cf6-cbt.

DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/53ce8cf6-cbt

OBJLIB-FILEBE : FileBEIoctl: ioctl operation failed on '/vmfs/devices/cbt/53ce8cf6-cbt' : Inappropriate ioctl for device (1638402)

ESXMapperGetPhysicalMapping: Failed to get physical mapping: 190004 Inappropriate ioctl for device

DISK: Change tracking for disk scsi0:1 is now enabled.

But it wouldn't be a datastore corruption as I see no other issues though we are seeing multiple VMs facing the same issue on this ESXi host.

0 Kudos
keerthyt
Contributor
Contributor

We tried the suggested steps and yet falling in to the same path. Not sure how to proceed with the issue.

Please help.

0 Kudos
continuum
Immortal
Immortal

Your last post was half a century ago.

Give us an update ...

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
keerthyt
Contributor
Contributor

As suggested we followed the steps as described below:

Disabled the replication on this VM and performed the following:

1. Turnoff the VM.

2. Disable CBT on the VM.

3. Make sure to delete all the snapshots.

4. Delete all the ctk.vmdk in the VM folder of the datastore.

5. Turn on the VM.

6. Set CBT back on the VM.

Now enabled replication on this VM and seeing still the same ioctl failures:

DISKLIB-CTK   : Auto blocksize for size 104857600 is 128.

DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 1260528137.

DISKLIB-CBT   : Successfuly created cbt node 4b222209-cbt.

DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/4b222209-cbt

OBJLIB-FILEBE : FileBEIoctl: ioctl operation failed on '/vmfs/devices/cbt/4b222209-cbt' : Inappropriate ioctl for device (1638402)

ESXMapperGetPhysicalMapping: Failed to get physical mapping: 190004 Inappropriate ioctl for device

DISK: Change tracking for disk scsi0:0 is now enabled.

DISKLIB-CBT   : Shutting down change tracking for untracked fid 1260528137.

DISKLIB-CBT   : Successfully disconnected CBT node.

DISKLIB-CTK   : Auto blocksize for size 104857600 is 128.

DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 1914774026.

DISKLIB-CBT   : Successfuly created cbt node 7221220a-cbt.

DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/7221220a-cbt

OBJLIB-FILEBE : FileBEIoctl: ioctl operation failed on '/vmfs/devices/cbt/7221220a-cbt' : Inappropriate ioctl for device (1638402)

ESXMapperGetPhysicalMapping: Failed to get physical mapping: 190004 Inappropriate ioctl for device

DISK: Change tracking for disk scsi0:1 is now enabled.

DISKLIB-CBT   : Shutting down change tracking for untracked fid 1914774026.

DISKLIB-CBT   : Successfully disconnected CBT node.

Any help is appreciated!

0 Kudos