What are the reasons that lead a table crash?
I have an application that writes and reads on a table "calls". The table
sometimes crashes.

By Andrea

wintelweb wrote:
> What are the reasons that lead a table crash?
> I have an application that writes and reads on a table "calls". The table
> sometimes crashes.
>
> By Andrea
>
>
describe "crashes" - error messages would be nice.. version of Mysql
would also be nice to know...

Log error:

071112 18:09:39 [ERROR] MySQL: Incorrect key file for table
'.\centralino\telefonate.MYI'; try to repair it
071112 18:09:39 [ERROR] MySQL: Incorrect key file for table
'.\centralino\telefonate.MYI'; try to repair it
071112 18:14:45 [Note] MySQL: Normal shutdown

071112 18:14:45 InnoDB: Starting shutdown...
071112 18:14:47 InnoDB: Shutdown completed; log sequence number 0 902948
071112 18:14:47 [Note] MySQL: Shutdown complete

071112 18:16:36 InnoDB: Started; log sequence number 0 902948
071112 18:16:36 [Note] MySQL: ready for connections.
Version: '5.0.15' socket: '' port: 3306 Official MySQL binary
071112 18:18:24 [ERROR] MySQL: Table '.\centralino\telefonate' is marked as
crashed and should be repaired

Version MySql : mysql-5.0.15-win32




"Michael Austin" <maustin@firstdbasource.com> ha scritto nel messaggio
news:xlPlj.1801$so6.1773@newssvr19.news.prodigy.ne t...
> wintelweb wrote:
>> What are the reasons that lead a table crash?
>> I have an application that writes and reads on a table "calls". The table
>> sometimes crashes.
>>
>> By Andrea
> describe "crashes" - error messages would be nice.. version of Mysql
> would also be nice to know...
>

On Mon, 28 Jan 2008 08:23:22 GMT, wintelweb wrote:
> Log error:
>
> 071112 18:09:39 [ERROR] MySQL: Incorrect key file for table
> '.\centralino\telefonate.MYI'; try to repair it
> 071112 18:09:39 [ERROR] MySQL: Incorrect key file for table
> '.\centralino\telefonate.MYI'; try to repair it
> 071112 18:14:45 [Note] MySQL: Normal shutdown
>
> 071112 18:14:45 InnoDB: Starting shutdown...
> 071112 18:14:47 InnoDB: Shutdown completed; log sequence number 0 902948
> 071112 18:14:47 [Note] MySQL: Shutdown complete
>
> 071112 18:16:36 InnoDB: Started; log sequence number 0 902948
> 071112 18:16:36 [Note] MySQL: ready for connections.
> Version: '5.0.15' socket: '' port: 3306 Official MySQL binary
> 071112 18:18:24 [ERROR] MySQL: Table '.\centralino\telefonate' is marked as
> crashed and should be repaired
>
> Version MySql : mysql-5.0.15-win32
>
>
>
>
> "Michael Austin" <maustin@firstdbasource.com> ha scritto nel messaggio
> news:xlPlj.1801$so6.1773@newssvr19.news.prodigy.ne t...
>> wintelweb wrote:
>>> What are the reasons that lead a table crash?
>>> I have an application that writes and reads on a table "calls". The table
>>> sometimes crashes.
>>>
>>> By Andrea
>> describe "crashes" - error messages would be nice.. version of Mysql
>> would also be nice to know...

That shows that the table IS damaged, not that it sometimes crashes.
Many things, but typically disk errors, can cause this. MySQL provides a
tool to help repair MyISAM tables.

http://dev.mysql.com/doc/refman/5.0/en/repair.html

--
49. If I learn the whereabouts of the one artifact which can destroy me, I
will not send all my troops out to seize it. Instead I will send them
out to seize something else and quietly put a want-ad in the local paper.
--Peter Anspach's list of things to do as an Evil Overlord

On 28 Jan, 14:08, "Peter H. Coffin" <hell...@ninehells.com> wrote:
> On Mon, 28 Jan 2008 08:23:22 GMT, wintelweb wrote:
> > Log error:
>
> > 071112 18:09:39 [ERROR] MySQL: Incorrect key file for table
> > '.\centralino\telefonate.MYI'; try to repair it
> > 071112 18:09:39 [ERROR] MySQL: Incorrect key file for table
> > '.\centralino\telefonate.MYI'; try to repair it
> > 071112 18:14:45 [Note] MySQL: Normal shutdown
>
> > 071112 18:14:45 InnoDB: Starting shutdown...
> > 071112 18:14:47 InnoDB: Shutdown completed; log sequence number 0 902948
> > 071112 18:14:47 [Note] MySQL: Shutdown complete
>
> > 071112 18:16:36 InnoDB: Started; log sequence number 0 902948
> > 071112 18:16:36 [Note] MySQL: ready for connections.
> > Version: '5.0.15' socket: '' port: 3306 Official MySQL binary
> > 071112 18:18:24 [ERROR] MySQL: Table '.\centralino\telefonate' is marked as
> > crashed and should be repaired
>
> > Version MySql : mysql-5.0.15-win32
>
> > "Michael Austin" <maus...@firstdbasource.com> ha scritto nel messaggio
> >news:xlPlj.1801$so6.1773@newssvr19.news.prodigy.n et...
> >> wintelweb wrote:
> >>> What are the reasons that lead a table crash?
> >>> I have an application that writes and reads on a table "calls". The table
> >>> sometimes crashes.
>
> >>> By Andrea
> >> describe "crashes" - error messages would be nice.. version of Mysql
> >> would also be nice to know...
>
> That shows that the table IS damaged, not that it sometimes crashes.
> Many things, but typically disk errors, can cause this. MySQL provides a
> tool to help repair MyISAM tables.

The log seems to suggest InnoDB

On Mon, 28 Jan 2008 06:38:25 -0800 (PST), Captain Paralytic wrote:
> On 28 Jan, 14:08, "Peter H. Coffin" <hell...@ninehells.com> wrote:
>> On Mon, 28 Jan 2008 08:23:22 GMT, wintelweb wrote:
>> > Log error:
>>
>> > 071112 18:09:39 [ERROR] MySQL: Incorrect key file for table
>> > '.\centralino\telefonate.MYI'; try to repair it
>> > 071112 18:09:39 [ERROR] MySQL: Incorrect key file for table
>> > '.\centralino\telefonate.MYI'; try to repair it
>> > 071112 18:14:45 [Note] MySQL: Normal shutdown
>>
>> > 071112 18:14:45 InnoDB: Starting shutdown...
>> > 071112 18:14:47 InnoDB: Shutdown completed; log sequence number 0 902948
>> > 071112 18:14:47 [Note] MySQL: Shutdown complete
>>
>> > 071112 18:16:36 InnoDB: Started; log sequence number 0 902948
>> > 071112 18:16:36 [Note] MySQL: ready for connections.
>> > Version: '5.0.15' socket: '' port: 3306 Official MySQL binary
>> > 071112 18:18:24 [ERROR] MySQL: Table '.\centralino\telefonate' is marked as
>> > crashed and should be repaired
>>
>> > Version MySql : mysql-5.0.15-win32
>>
>> > "Michael Austin" <maus...@firstdbasource.com> ha scritto nel messaggio
>> >news:xlPlj.1801$so6.1773@newssvr19.news.prodigy.n et...
>> >> wintelweb wrote:
>> >>> What are the reasons that lead a table crash?
>> >>> I have an application that writes and reads on a table "calls". The table
>> >>> sometimes crashes.
>>
>> >>> By Andrea
>> >> describe "crashes" - error messages would be nice.. version of Mysql
>> >> would also be nice to know...
>>
>> That shows that the table IS damaged, not that it sometimes crashes.
>> Many things, but typically disk errors, can cause this. MySQL provides a
>> tool to help repair MyISAM tables.
>
> The log seems to suggest InnoDB

Perhaps I am wrong in thinking that the '.\centralino\telefonate.MYI'
complaints are suggesting MyISAM tables, and the line about InnoDB is
just the storage engine shutting down as part of mysql shutdown.

--
"I know it's a buzzword [...], but fsckit, 'Enterprise' editions of things
*should* come with the phasers and photon torpedos and all.
Of course, the first vendor freebie you'd get would be a red shirt..."
-- Anthony de Boer in the Monastery

On 28 Jan, 15:35, "Peter H. Coffin" <hell...@ninehells.com> wrote:
> On Mon, 28 Jan 2008 06:38:25 -0800 (PST), Captain Paralytic wrote:
> > On 28 Jan, 14:08, "Peter H. Coffin" <hell...@ninehells.com> wrote:
> >> On Mon, 28 Jan 2008 08:23:22 GMT, wintelweb wrote:
> >> > Log error:
>
> >> > 071112 18:09:39 [ERROR] MySQL: Incorrect key file for table
> >> > '.\centralino\telefonate.MYI'; try to repair it
> >> > 071112 18:09:39 [ERROR] MySQL: Incorrect key file for table
> >> > '.\centralino\telefonate.MYI'; try to repair it
> >> > 071112 18:14:45 [Note] MySQL: Normal shutdown
>
> >> > 071112 18:14:45 InnoDB: Starting shutdown...
> >> > 071112 18:14:47 InnoDB: Shutdown completed; log sequence number 0 902948
> >> > 071112 18:14:47 [Note] MySQL: Shutdown complete
>
> >> > 071112 18:16:36 InnoDB: Started; log sequence number 0 902948
> >> > 071112 18:16:36 [Note] MySQL: ready for connections.
> >> > Version: '5.0.15' socket: '' port: 3306 Official MySQL binary
> >> > 071112 18:18:24 [ERROR] MySQL: Table '.\centralino\telefonate' is marked as
> >> > crashed and should be repaired
>
> >> > Version MySql : mysql-5.0.15-win32
>
> >> > "Michael Austin" <maus...@firstdbasource.com> ha scritto nel messaggio
> >> >news:xlPlj.1801$so6.1773@newssvr19.news.prodigy.n et...
> >> >> wintelweb wrote:
> >> >>> What are the reasons that lead a table crash?
> >> >>> I have an application that writes and reads on a table "calls". The table
> >> >>> sometimes crashes.
>
> >> >>> By Andrea
> >> >> describe "crashes" - error messages would be nice.. version of Mysql
> >> >> would also be nice to know...
>
> >> That shows that the table IS damaged, not that it sometimes crashes.
> >> Many things, but typically disk errors, can cause this. MySQL provides a
> >> tool to help repair MyISAM tables.
>
> > The log seems to suggest InnoDB
>
> Perhaps I am wrong in thinking that the '.\centralino\telefonate.MYI'
> complaints are suggesting MyISAM tables, and the line about InnoDB is
> just the storage engine shutting down as part of mysql shutdown.
>
> --
> "I know it's a buzzword [...], but fsckit, 'Enterprise' editions of things
> *should* come with the phasers and photon torpedos and all.
> Of course, the first vendor freebie you'd get would be a red shirt..."
> -- Anthony de Boer in the Monastery

You could be right there