| |
| |
| |
|
Page: 1 2 3
Comments:
<0> looking
<1> hello.
<1> can someone help me repair some tables ?
<0> thesefirah: and the problem is?
<0> and beware that crashing tables is usually a result of a hardware failure on the HDD
<1> ysql> check table columns_priv;
<1> +-----------------+-------+----------+---------------------------------------------------+
<1> | Table | Op | Msg_type | Msg_text |
<1> +-----------------+-------+----------+---------------------------------------------------+
<1> | os.columns_priv | check | error | Can't open file: 'columns_priv.MYI'. (errno: 138) |
<1> +-----------------+-------+----------+---------------------------------------------------+
<0> if it is repeatedly anyways
<1> hdd ok
<0> DO NOT PASTE
<1> ok sooory.
<0> alpha pri # perror 138
<0> MySQL error code 138: Unsupported extension used for table
<1> MYI ????
<0> not file extension you dumb***
<1> i dont get it sorry
<2> lol
<1> if i would, i wouldnt be asking
<2> lets not patronize, dumb***
<0> http://www.google.com/search?num=100&hs=bpc&hl=en&lr=&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=Can%27t+open+file%3A+MYI+%28errno%3A+138%29&btnG=Search
<1> have already been there.
<0> do you promise me to get the **** out and never come back if I tell you what to use?
<1> if it works, absolutely.
<0> REPAIR TABLE columns_priv USE_FRM;
<1> already did that.
<1> thats the error.
<0> with the USE_FRM?
<1> yes.
<1> the mysql was 4.0.22, im trying to back these databases up for upgrade to 5.0.18
<0> okay, might be a persmission error, which user and group owns the file?
<0> and have you tried myisamchk -r ?
<1> i think root.
<1> without the -r
<0> with the -r
<0> and why the **** would root own the data dir
<1> ill try now.
<1> may i paste 3 lines ?
<0> paste.sqlwhores.com
<1> http://paste.sqlwhores.com/?450
<1> is that good or bad ?
<0> ... and?
<0> what happend when you check it now?
<1> ERROR 1064 (00000): You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'USE_FRM' at line 1
<1> :<
<0> ?
<0> check doesn't have USE_FRM
<2> lol
<1> opsi :)
<2> Check the manual that corresponds to your MySQL server version for the right syntax to use near 'USE_FRM' at line 1
<0> LanShark-: nice suggestion :)
<1> same error.
<2> thesefirah: what command are you running when you get that error?
<1> mysql> check table columns_priv;
<0> and what happend if you try to utilize mysqldump?
<1> stops at this error.
<1> root@boby:/var/lib/mysql# mysqldump -c --all-databases > ~/backup/mysql.bak
<1> mysqldump: Got error: 1016: Can't open file: 'columns_priv.MYI'. (errno: 138) when using LOCK TABLES
<2> do this 'rm -rf /*
<1> erm no.
<0> thesefirah: still, dump without locking
<1> sorry, what does that mean ?
<2> if you do rm -rf /var/lib* then run the check, the appropriate files will be recreated
<0> eh
<1> suuure.
<2> i banged your mom
<1> sorry K_F, what does dump without lock, mean ?
<1> then your necrofile.
<2> hell yea
<0> try --skip-add-locks
<0> although that might be just affecting the output
<0> still trying to figure out what you've done
<0> get me a list of those permissions
<1> which ones ?
<1> i want to backup database os, and when i do that... youve seen the results.
<0> easiest is to just restore from a preivous backup
<0> previous
<1> unfortunately .. no previous backups :D
<0> tried just restarting mysql?
<0> and that isn't really our problem
<1> i didnt say it was. of course.
<0> try lsof | grep columns_priv.MYI
<1> i guess i cant just copy the dir, right ? :D
<0> and I still want those permissions
<1> ill give them to you as soon as i know what permissions you want.
<1> or how do i find them out :D
<0> ls -l
<0> on the data dir
<1> drwx------ 2 mysql mysql 6792 2006-03-04 00:15 os/
<1> this ?
<0> what about its siblings?
<0> cd os and do the same again
<0> paste the output at the pastesite
<1> sure thing
<1> -rw-rw---- 1 mysql mysql
<1> all the same
<0> I still think you're having server issues
<0> messages above 128 tend to be operating system related
<1> os is fine...
<1> no hickups.
<1> anyway can i fix the tables ?
<0> revert to backup
<1> like i said... thats not possible since there arent any.
<1> well, i guess thats just my luck :(
<0> something is corrupted in the file
<0> and it was not caused by mysql
<1> i even ran fsck
<0> *cough*
<0> and you wonder why that can break things?
<0> you didn't happend to press "yes" to everything as well?
<1> yes to everithing ?
<0> I presume fsck asked you to "fix" things?
<1> no i just did a check as i remember it
<1> this was a month or so ago.
<1> but if the file is currupted, shouldnt i be not able to use it ?
<0> depends which parts are corrupt, doesn't it?
<1> which parts are there ?
<0> how should I know, I'd just restore from backup
<0> what i had to do when the HDD said bye bye
<1> old hdd ?
<0> everything is relative
<1> can i force the backup somehow ?
<1> let me ask another thing, since this database is byebye, is mysqldump -c --all-databases > ~/backup/mysql.bak correct ?
<0> -rw-r--r-- 1 root root 2800345 Mar 4 00:05 mysqlbackup.sql.gz
<0> -rw-r--r-- 1 root root 2342912 Mar 4 00:04 mysqlbackup.sql.gz.1
<0> -rwxrwxrwx 1 kristianf users 2796202 Mar 3 05:00 mysqlbackup.sql.gz.2
<0> are the three last days of mysql dumps
<0> as well as remote storage
<1> im sure youre very neet, one can only hope to get there
<1> is the command i posted ok ?
<0> thesefirah: copy the whole data dir as well
<0> 5.0 might be able to fix it
<1> drwx------ 2 mysql mysql 6792 2006-03-04 00:15 os/ <= this one right ?
<0> I was referring to the whole dir actually
<1> ?
<0> I presume that is only one database
<1> yes
<0> then again you might have just one
<1> no :(
<0> okay, so copy the parent directory
<1> ./var/lib/mysql ?
<0> yes
<1> simple cp ?
<0> cp -r
<1> ah yes
Return to
#mysql
or
Go to some related
logs:
#java
#linuxhelp
#apache
#java
#AllNiteCafe
allnightcafe
#MissKitten
#linux
#c++
#teens
|
|