Oops, totally missed that, thanks.
Reindl Harald <h.reindl@stripped> wrote:
>Am 24.06.2013 18:47, schrieb Johan De Meersman:
>> ----- Original Message -----
>>> From: "nixofortune" <nixofortune@stripped>
>>> Hi guys,
>>> any suggestions? I just repaired 90G MyISAM table with REPAIR TABLE
>>> command. the space on the hard drive gone down from 165 Gig to 70
>>> Gig. I understand that during repair process MySQL creates temp file
>>> remove it after the job done. Or removal process executes on the
>>> restart? how can I get that space back? I can't check the table
>>> directory as I don't have root perm on that box.
>> Oops... Can you run [show global variables like
>> I kind of expect it to be OFF, which means that the temp table would
>have been created in the main tablespace. If that's the case, that
>space has been permanently assimilated by the global tablespace; the
>only way to get it back would be a full dump of all your (innodb)
>tables, stop server, delete tablespace, start server and import the
>data again. Be sure to read the documentation carefully before doing
>such an intrusive operation.
>> While you're doing that, use the opportunity to set
>innodb_file_per_table to ON :-p
>he spoke about MYISAM table
>>> the space on the hard drive gone down from 165 Gig to 70 Gig
>>> how can I get that space back?
>>> I can't check the table directory as I don't have root perm
>well, someone should look at the dadadir and error-log
>it is not uncommon that a repair to such large tables
>fails due too small "myisam_sort_buffer_size" and i
>suspect the operation failed and some temp file is
Sent from Kaiten Mail. Please excuse my brevity.