Qemu-img 5.2.91 can't open vmdk, Failed to lock byte 100: Input/output error, but qemu-img 2.5 work

Question

openstack:~/qemu-6.0.0-rc1/build$ qemu-img --version
qemu-img version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.51), Copyright (c) 2004-2008 Fabrice Bellard
openstack:~/qemu-6.0.0-rc1/build$ sudo qemu-img check /mnt/esxi/name.vmdk
No errors were found on the image.

openstack:~/qemu-6.0.0-rc1/build$ ./qemu-img -V
qemu-img version 5.2.91
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
openstack:~/qemu-6.0.0-rc1/build$ sudo ./qemu-img check /mnt/esxi/name.vmdk
qemu-img: Could not open '/mnt/esxi/name.vmdk': Failed to lock byte 100: Input/output error

As the command output, the qemu-img 5.2.91 can't check the vmdk file, but qemu-img 2.5 works fine.

qemu-img 5.2.91 --help get this:

Supported formats: blkdebug blklogwrites blkverify bochs cloop compress copy-on-read dmg file host_cdrom host_device luks nbd null-aio null-co nvme preallocate qcow qcow2 qed quorum raw rbd replication throttle vdi vhdx vmdk vpc vvfat

How can I fix it? THX

I don't have a solid answer for you, but it might help to know if the vmdk file is currently in use by a VM, since the error indicates a failure to lock it. And if it IS in use, kill the VM first and try again? — Aiken Drum
– Aiken Drum, Commented Apr 22, 2021 at 22:12
The VM is shutoff, and why the old version(2.5) qemu-img check it was OK but the 5.2.91 version check it can not open? — Victor Lee
– Victor Lee, Commented Apr 23, 2021 at 1:30
I'm just guessing that the locking protocol was either different, or absent, in the old version — Aiken Drum
– Aiken Drum, Commented Apr 23, 2021 at 1:39
Are there any files in the same folder, or elsewhere, that have similar filenames to the vmdk, but with "lock" appended? Something like that? Perhaps a previous VM session left a stale lock file. — Aiken Drum
– Aiken Drum, Commented Apr 23, 2021 at 1:39
Maybe it not about the stale lock file.Check the picture I update the question. — Victor Lee
– Victor Lee, Commented Apr 23, 2021 at 1:53

Victor Lee · Accepted Answer · 2021-04-25 03:29:07Z

0

Because the vmdk file in NFS directory, add this option -o nolock fixed it.

nolock — Disables file locking. This setting is occasionally required when connecting to older NFS servers. noexec — Prevents execution of binaries on mounted file systems. This is useful if the system is mounting a non-Linux file system via NFS containing incompatible binaries.

answered Apr 25, 2021 at 3:29

Victor Lee

2,7164 gold badges22 silver badges48 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Qemu-img 5.2.91 can't open vmdk, Failed to lock byte 100: Input/output error, but qemu-img 2.5 work

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related