Hello.
On Tue, Apr 03, 2001 at 11:51:47AM +0200, [EMAIL PROTECTED] wrote:
> Hi,
>
> we currently have a situation with our mysql-3.22.29 under
> Solaris-2.7, where the databases itself are put on an NFS-mounted
> filesystem. Yesterday we had a crash of the system and isamcheck
> tried to recover some databases - but some people have reached or
> already exceeded their quotas, therefore isamcheck can not recover
> the files. The result are damaged indexes which causes crashes on
> the mysqld, and tables which have only part of the filelenght it
> should have.
>
> has this behaviour changed in 3.23.*? Is it there handled gracefully?
Hm. I am not sure, how you expect this to be handled. isamchk can not
recover the files, because it's not allowed to use the needed space.
Normally, it will not change the damaged files, but only replace them
by a repaired version. So what should it do?
IMO, mysqld may not be started, if isamchk failed, therefore the
crashes are the result of using MySQL in an undefined way.
It may be, that 3.23.x doesn't crash, as it knows (with MyISAM
tables), that they were not closed properly and need a check, but I
don't know what happens, after the automatic repair failed. Maybe it
just shuts down. *shrug*
Or did I miss your point?
Bye,
Benjamin.
---------------------------------------------------------------------
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
