#6 Bug under Win7/64 and using Ext2MGR

[mikhoul]

Hi,

Thanks for your software it's very useful.

I think I found a bug, I use ImDiskToolkit to access VMDK linux image with Ext2MGR and when I dismount the VMDK image the ImDisk-Dlg.exe process is stuck in limbo.

I'm not even able to kill it, I have to restart my computer to get rid of it.

It happen everytime I'm ready to unmount my VMDK image.

Let me know if you need more information.

Regards :-)

[v77]

Interesting. Could you please provide a small image file of the same type that the one you are using (vmdk with a partition formatted with ext2fs)?

[mikhoul]

Yes here it is archived with Rar: https://mega.nz/#!lwgUULbS!z-Ub6cVJ9gE-BiSzXCQQvhG5L77sa2wydsgiAx8I7JE

It is a Slitaz (linux VMDK) Main partition with a second small Swap partition.

Step to reproduce:

1- Start ext2fs to be able to read the partition
2- mouns the VMDK Volume choose the big one.
3- Look inside the archive if you see the files, everything should be fine.

4- Try do unmount the Volume, the Imdsk-dlg.exe process will be lock. :(

Let me know when you will have downloaded the file I will delete it ;-)

Have a nice week-end !

[v77]

OK thanks. I found the bug, and it's a strange one.
When the lock attempt of the volume fails, it seems to be stuck. But this does not occur when the command line (imdisk.exe) is used to dismount the volume, even if it performs the same thing.
The lock attempt is a call to the file system driver (FSCTL_LOCK_VOLUME), and when the bug occur, the execution point is in the kernel. This is why you cannot kill the process.

This is definitely a bug of ext2fsd. Perhaps there is a workaround, because it works with imdisk.exe (in an elevated command prompt, try imdisk -D -m P: ), but I am still perplexed.

[v77]

I created a ticket here.
For now, this is all I can do.

[mikhoul]

Thanks in meantime I will do a script to unmount the volume. :)