MySQL tables crashed
-
Hi everyone, I'm a software developer and just started my professional career life, question here i want to ask is ... that few days ago i was at client site to resolve some issue in application deployed by a company that uses MySQL for database, what i was found that there are four MySQL tables were crashed due to low harddisk space issue (I've searched on net that this is a usual problem with MySQL) that then i repaired by using
myisamchkcommand. Error shown by MySQL when these were accessing is[table name] marked as crashed and should be repaired. ok so this was the background scenario, now what i want to know/ask here is ... as described in above details that these 4 four tables were not accessible becuase they are crashed but I took a backup of this database and restore it to MySQL at another machine then i can access these table easily with no issue/error by MySQL, SO WHY THIS HAPPENS THAT AT ONE SIDE THESE ARE AS CRASHED AND ON ANOTHER THE BACKUP OF SAME DATABASE THAT WAS TAKEN WHEN THESE TABLES ARE CRASHED ARE THEN WORKING FINE. I really will appreciate any kind of help on this topic Im just asking this for knowlegde and second thing is my boss also asked me the same question ;P -
Hi everyone, I'm a software developer and just started my professional career life, question here i want to ask is ... that few days ago i was at client site to resolve some issue in application deployed by a company that uses MySQL for database, what i was found that there are four MySQL tables were crashed due to low harddisk space issue (I've searched on net that this is a usual problem with MySQL) that then i repaired by using
myisamchkcommand. Error shown by MySQL when these were accessing is[table name] marked as crashed and should be repaired. ok so this was the background scenario, now what i want to know/ask here is ... as described in above details that these 4 four tables were not accessible becuase they are crashed but I took a backup of this database and restore it to MySQL at another machine then i can access these table easily with no issue/error by MySQL, SO WHY THIS HAPPENS THAT AT ONE SIDE THESE ARE AS CRASHED AND ON ANOTHER THE BACKUP OF SAME DATABASE THAT WAS TAKEN WHEN THESE TABLES ARE CRASHED ARE THEN WORKING FINE. I really will appreciate any kind of help on this topic Im just asking this for knowlegde and second thing is my boss also asked me the same question ;Pkhurram_shahzad wrote:
..were crashed due to low harddisk space issue...SO WHY THIS HAPPENS
If I had to guess - because of low hard disk space. By the way...really, really bad idea to let a database server run out of hard drive space. Doesn't matter what type of database either.
-
Hi everyone, I'm a software developer and just started my professional career life, question here i want to ask is ... that few days ago i was at client site to resolve some issue in application deployed by a company that uses MySQL for database, what i was found that there are four MySQL tables were crashed due to low harddisk space issue (I've searched on net that this is a usual problem with MySQL) that then i repaired by using
myisamchkcommand. Error shown by MySQL when these were accessing is[table name] marked as crashed and should be repaired. ok so this was the background scenario, now what i want to know/ask here is ... as described in above details that these 4 four tables were not accessible becuase they are crashed but I took a backup of this database and restore it to MySQL at another machine then i can access these table easily with no issue/error by MySQL, SO WHY THIS HAPPENS THAT AT ONE SIDE THESE ARE AS CRASHED AND ON ANOTHER THE BACKUP OF SAME DATABASE THAT WAS TAKEN WHEN THESE TABLES ARE CRASHED ARE THEN WORKING FINE. I really will appreciate any kind of help on this topic Im just asking this for knowlegde and second thing is my boss also asked me the same question ;PThe message might be a bit misleading.
Crasheddoes not mean your tables are goofed up, it only means that the database engine has set an internal flag on those tables that indicate that the tables can no longer take new rows because of lack of space. Once you move your database to a new server, your database engine is smart enough to recalculate the new space and removes the flag. -
The message might be a bit misleading.
Crasheddoes not mean your tables are goofed up, it only means that the database engine has set an internal flag on those tables that indicate that the tables can no longer take new rows because of lack of space. Once you move your database to a new server, your database engine is smart enough to recalculate the new space and removes the flag.Yes thanks .. I'm also thinking the same.