[MDEV-707] LP:885132 - MyISAM optimize table wrongly reporting "status ok" Created: 2011-11-02  Updated: 2014-03-18  Resolved: 2014-03-18

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Dreas van Donselaar (Inactive) Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug885132.xml    

 Description   

We've table taking up a lot of disk:

-rw-rw----  1 mysql mysql  8.9K 2011-05-06 21:23 table.frm
 
-rw-rw----  1 mysql mysql  4.2G 2011-11-02 10:53 table.MYD
 
-rw-rw----  1 mysql mysql   43K 2011-11-02 10:53 table.MYI

It should be tiny though, since there is almost no data in it:

MariaDB [database]> select count(*) from table;
 
+----------+
 
| count(*) |
 
+----------+
 
|      155 |
 
+----------+
 
1 row in set (0.00 sec)

So we tried to optimize it:

MariaDB [database]> optimize table table;
 
+----------------------+----------+----------+--------------------------------------+
 
| Table                | Op       | Msg_type | Msg_text                             |
 
+----------------------+----------+----------+--------------------------------------+
 
| database.table | optimize | error    | myisam_sort_buffer_size is too small |
 
| database.table | optimize | status   | OK                                   |
 
+----------------------+----------+----------+--------------------------------------+
 
2 rows in set (5.56 sec)
 
 
 
MariaDB [database]> optimize table table;
 
+----------------------+----------+----------+-----------------------------+
 
| Table                | Op       | Msg_type | Msg_text                    |
 
+----------------------+----------+----------+-----------------------------+
 
| database.table | optimize | status   | Table is already up to date |
 
+----------------------+----------+----------+-----------------------------+
 
1 row in set (0.00 sec)

It's still taking the same diskspace though, so optimization seems to have failed. Running an "alter table table engine=MyISAM" does result in a rebuilt taking a lot less space (although still more than expected). The real bug here would be the optimize table not actually executing, and marking the table as optimized I presume.

 Comments   
Comment by Elena Stepanova [ 2012-05-04 ]

Re: MyISAM optimize table wrongly reporting "status ok"
Hi Dreas,

Do you still have this problem?
If so, could you please provide the table structure (to start with)?

Thank you

Comment by Dreas van Donselaar (Inactive) [ 2012-05-05 ]

Re: MyISAM optimize table wrongly reporting "status ok"
I'm afraid if I didn't upload any data to FTP related to this issue, I currently have no way of reproducing it. If I encounter it again I'll report it including the relevant data.

Comment by Rasmus Johansson (Inactive) [ 2012-05-05 ]

Launchpad bug id: 885132

Comment by Elena Stepanova [ 2014-03-18 ]

The report has never had enough information to reproduce it, and the reporter did not come back saying that it happened again.

Generated at Thu Feb 08 06:30:45 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.