Hi, I tried to compress some very big table on Linux and it seems to me that myisampack does not properly remove temporary files after abort.
After myisampack cannot write to a file (because the filesystem is full), it should at least remove the .TMD file after itself, I hope. :( Since then, all trial to compress next tables failed, because there're just few bytes left on the filesystem. This I got from myisampack: /usr/local/mysql/bin/myisampack: Error writing file '/usr/local/mysql/tmp/blast_data.TMD' (Errcode: 28) /usr/local/mysql/bin/myisampack: Got error 0 reading records Aborting: blast_data.MYD is not compressed And here's the /usr/local/mysql/tmp -rw-r--r-- 1 pedant users 32 Nov 16 23:50 blast.TMD -rw-r--r-- 1 pedant users 1307516928 Nov 16 23:48 blast_data.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:50 blimps.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:50 blimps_data.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:53 cogs.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:52 cogs_data.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:53 coils.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:53 coils_data.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:54 contig.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:54 contig_data.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:54 ecnum.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:54 exon.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:54 exon_data.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:56 funcat.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:56 funcat_data.TMD -rw-r--r-- 1 pedant users 0 Nov 16 23:57 known3d.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:57 known3d1.TMD -rw-r--r-- 1 pedant users 32 Nov 16 23:57 known3d_data.TMD $ df -k Filesystem 1k-blocks Used Available Use% Mounted on /dev/sda6 521748 79264 415980 16% / /dev/sda1 31079 6578 22897 22% /boot /dev/sda9 5336664 553204 4512368 11% /home /dev/sda5 2071384 1966172 0 100% /usr /dev/sda8 256667 9383 234032 4% /var /dev/sdb3 2071416 864 1965328 0% /var/tmp /dev/sdc1 175102767 145115962 19982328 88% /home/mysql $ After removing the stale blast_data.TMD my processes continue to compress tables. ---------------------- I was told by a colleague that our mysql does not handle properly situation, when the kernel does not allow to grow the table. The table get's corrupted, client get's disconnected (or perl DBI abort the connection itself, I can't say). However, I succed to run repair table on it. To be more specific, we run Linux with kernel 2.2.19 having 2GB filesize limit. $ /usr/local/mysql/bin/mysql --version mysql Ver 11.15 Distrib 3.23.42, for pc-linux-gnu (i686) $ I'll ask him for more details about this issue on monday. But maybe you already know enough. ;) -- Martin Mokrejs - PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs MIPS / Institute for Bioinformatics <http://mips.gsf.de> GSF - National Research Center for Environment and Health Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany tel.: +49-89-3187 3616 , fax: +49-89-3187 3585 --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
