MySQL Bugs: #29514: Removing Falcon file and querying object from removed file crashes the server

Bug #29514	Removing Falcon file and querying object from removed file crashes the server
Submitted:	3 Jul 2007 13:31	Modified:	11 Aug 2007 21:48
Reporter:	Robin Schumacher	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Falcon storage engine	Severity:	S2 (Serious)
Version:	6.0	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
If a falcon tablespace file is deleted, any object queried from the deleted file will crash the server. 

How to repeat:
Stop MySQL server, delete tablespace file, start server, issue query for object in  the tablespace with now-deleted file crashes the server.

Thank you for the bug report. Could you please print here the exactly
steps you did. I got the below result after deleting the Falcon's tablespace
files:

c:\mysql-6.0.0-alpha-win32>bin\mysql -uroot gimf
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 6.0.0-alpha-community-nt-debug MySQL Community Server (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> create tablespace gimfdata1
    -> add datafile 'c:/dev/gimf1.fts'
    -> engine=falcon;
Query OK, 0 rows affected (0.26 sec)

mysql> create table tb1 (id serial, col1 char(20))
    -> tablespace gimfdata1 engine=falcon;
Query OK, 0 rows affected (0.41 sec)

mysql> insert into tb1 values (NULL,'test');
Query OK, 1 row affected (0.00 sec)

mysql> select * from tb1;
+----+------+
| id | col1 |
+----+------+
|  1 | test |
+----+------+
1 row in set (0.00 sec)

mysql> exit
Bye

c:\mysql-6.0.0-alpha-win32>bin\mysqladmin -uroot shutdown

c:\mysql-6.0.0-alpha-win32>bin\mysql -uroot gimf
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 6.0.0-alpha-community-nt-debug MySQL Community Server (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> select * from tb1;
ERROR 1030 (HY000): Got error 157 from storage engine
mysql>

Thanks in advance.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".