#184 Unmount bug

[Grant Atoyan]

Dear developers and forumers!

I think it is better to address this problem to the developers here, since the forum is mainly for users and, to my mind, is not the right place to trace and debug the driver's code.

We still cannot use version 0.69, since the unmount bug persists! It reveals both under Windows 7 x64 and Windows Server 2012 R2 (and, probably, in other Windows versions). As there was no reaction to my previous messages (on the forun), I should mention the details to make you understand the problem better. I think many of us use the external USB HDD drives, particularly with NTFS partitions (with write caching enabled). The bug can be reproduced the following way.

1. Install Ext2fsd 0.69 driver under your Windows system with the command line:

setup.bat wxp amd64

(This syntax is also for Windows 7 )

Reboot the computer.

1. Mount the ext (ext2/ext3/ext4) partition on the internal HDD, assign the letter, create directory or write some files to the partition (i.e. write something there)

2. Plug in the external USB drive (with NTFS partition). Make sure that the letter is assigned, for e.g. k: (You may do some operations on the volume – read/write files, so on).

3. Make sure volume k: is unlocked, try to unmuont it. The easiest way to do it is to run

mountvol k: /p

The thread hangs on the unmounting!!!

The unmount attempt is effected, for e.g., when you run chkdsk with ‘/F’ parameter and it finishes checking the volume, when you try to reboot the computer with plugged-in USB drive. The USB drive partition may remain dirty then. So, I can niether check my USB drive, nor unplug the drive with unmouting, nor reboot the machine, if version 0.69 is installed! What is more important – access to EXT partitions or USB storage? Therefore, I have to use 0.52 by far!

So, who can tell me what is happening? I’m sure that many people have noticed the problem. With great pleasure I would assist in debugging the driver, in testing the attempts to correct the bug.