Re: Deleted table file behavior!
Any changes you make to data are first made in memory, then written to the binary log file and finally (indeed, eventually) to the data file(s).
I suspect what you're seeing is a change still "in flight".
The second change, made while the data file is unavailable, is made to an in-memory data block and to the binary log file but can't been written to the [missing] data file; this is perfectly acceptable, normal behaviour for MySQL.
After the restart, MySQL tries to sort this "mess", that is:
* what's in the data files,
* what's written to the binary log but not yet applied to the data file(s), and
* what's written to the binary log but that shouldn't be applied (i.e., uncommited changes).
As part of this, it notes the "reappearence" of your data file and applies the necessary changes - your new record - into the data file.
All that said, ripping bits of out of any DBMS while it's running is a seriously Bad Idea! 8-0
Regards, Phill W.