The driver gets stuck when the hard drive is unexpectedly physically detached and attached back

[JusSergey]

My steps:

1. attach external hard-drive
2. create a file on the hard-drive which will be used for creating a loopback device
3. attach the file as a block device (by losetup), part it, create an ext4 fs, mount it
4. run ingest for the loopback device (you should pass a partition to ./elastio like /dev/loop0p1).
5. physically detach the hard drive and attach it again (in my case it was simulated when my laptop went to sleep mode, it looks like the hard drive turned off and then turned on with ~1-second interval)
6. try to destroy snapshot by sudo elioctl destroy 0 and this is the point where the driver gets stuck

Expected behavior: the driver should somehow handle this case, maybe it should just write an error somewhere but, definitely, it shouldn't be stuck because in my case it has lead to a hard reboot (press and hold the power button, that's very bad, it could lead to data corruption if some process has been writing some critical/important data to a disk at this moment)