InnoDB is different from MyISAM. It crashed intentionally, as stated in the log you posted, to avoid data corruption propagation.
Take a look at this page, so next time you can try to repair tables:
http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
Regards,
Federico
--------------------------------------------
Lun 6/6/16, Mark ha scritto:
Oggetto: Re: [Maria-discuss] Horrendeous InnoDB crash
A: maria-discuss@lists.launchpad.net
Data: Lunedì 6 giugno 2016, 12:23
#yiv2481875527
#yiv2481875527 --
_filtered #yiv2481875527 {font-family:Wingdings;panose-1:5
0 0 0 0 0 0 0 0 0;}
_filtered #yiv2481875527 {panose-1:2 4 5 3 5 4 6 3 2 4;}
_filtered #yiv2481875527 {font-family:Calibri;panose-1:2 15
5 2 2 2 4 3 2 4;}
_filtered #yiv2481875527 {font-family:Consolas;panose-1:2
11 6 9 2 2 4 3 2 4;}
#yiv2481875527
#yiv2481875527 p.yiv2481875527MsoNormal, #yiv2481875527
li.yiv2481875527MsoNormal, #yiv2481875527
div.yiv2481875527MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;color:black;}
#yiv2481875527 a:link, #yiv2481875527
span.yiv2481875527MsoHyperlink
{color:#0563C1;text-decoration:underline;}
#yiv2481875527 a:visited, #yiv2481875527
span.yiv2481875527MsoHyperlinkFollowed
{color:#954F72;text-decoration:underline;}
#yiv2481875527 p
{margin-right:0in;margin-left:0in;font-size:11.0pt;color:black;}
#yiv2481875527 pre
{margin:0in;margin-bottom:.0001pt;font-size:10.0pt;color:black;}
#yiv2481875527 p.yiv2481875527MsoListParagraph,
#yiv2481875527 li.yiv2481875527MsoListParagraph,
#yiv2481875527 div.yiv2481875527MsoListParagraph
{margin-top:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;font-size:11.0pt;color:black;}
#yiv2481875527 p.yiv2481875527msonormal0, #yiv2481875527
li.yiv2481875527msonormal0, #yiv2481875527
div.yiv2481875527msonormal0
{margin-right:0in;margin-left:0in;font-size:12.0pt;color:black;}
#yiv2481875527 span.yiv2481875527EmailStyle19
{color:windowtext;}
#yiv2481875527 span.yiv2481875527HTMLPreformattedChar
{color:black;}
#yiv2481875527 span.yiv2481875527EmailStyle22
{color:windowtext;}
#yiv2481875527 .yiv2481875527MsoChpDefault
{font-size:10.0pt;}
_filtered #yiv2481875527 {margin:1.0in 1.0in 1.0in 1.0in;}
#yiv2481875527 div.yiv2481875527WordSection1
{}
#yiv2481875527
_filtered #yiv2481875527 {}
_filtered #yiv2481875527 {}
_filtered #yiv2481875527 {}
_filtered #yiv2481875527 {font-family:Wingdings;}
_filtered #yiv2481875527 {font-family:Symbol;}
_filtered #yiv2481875527 {}
_filtered #yiv2481875527 {font-family:Wingdings;}
_filtered #yiv2481875527 {font-family:Symbol;}
_filtered #yiv2481875527 {}
_filtered #yiv2481875527 {font-family:Wingdings;}
#yiv2481875527 ol
{margin-bottom:0in;}
#yiv2481875527 ul
{margin-bottom:0in;}
#yiv2481875527 Sorry I wiped the
database; but it got to the point where MariaDB immediately
crashed upon startup (so the usual repair attempts were
futile, as they all kinda assume a MariaDB server that’s
up and running). I have years of experience (FreeBSD) with
myisam tables; but a crash like this is a first for me,
really, where the entire database was foobarred to the point
MariaDB wouldn’t even start any more. Thanks for
creating the bug report. I shall investigate myself too, in
trying to find a way to integrate the MariaDB shutdown
gracefully (in UNIX this is all much simpler and
straightforward). -
Mark
From: Vladislav Vaintroub
[mailto:vvaintroub@gmail.com]
Sent:
Monday, June 6, 2016 11:39
To: Mark
;
maria-discuss@lists.launchpad.net
Subject: Re: [Maria-discuss] Horrendeous
InnoDB crash Yes, it is possible
that Windows does not give enough time to MariaDB to shut
down gracefully. I just created a task for this one here https://jira.mariadb.org/browse/MDEV-10183.Still, Innodb should
handle this situation gracefully, and recover on startup, so
what you see is a bug. It is a pity that you wiped down the
database, it would be useful for a bug report. On 06.06.2016 11:08, Mark
wrote:Got a huge crash today, right
after initializing my first MariaDB database (see below).
Got several more errors about tables having crashed later
on, and MariaDB wouldn't even start up any more (I wound
up wiping the entire database). So, my question is, what could
cause MariaDB to fail so horrendeously?! I though InnoDB was
supposed to be *better* than myisam!? Is is because maybe
Windows 10 doesn't give MariaDB enough time to shut down
gracefully? Could it be because a Windows scheduler job
(potentially) aborts the fetcher script when it's still
running? (Again, I though InnoDB was supposed to be
transaction-safe). In its current state, MariaDB is
completely unusable for me. And no, I don't have hard disk
errors. :) Seriously, though, I could use
some major insight! Thanks. 2016-06-06 10:32:15 2552 [Note]
Server socket created on IP: '::'.2016-06-06 10:32:15 2552 [Note]
C:\xampp\mysql\bin\mysqld.exe: ready for
connections.Version:
'10.1.13-MariaDB' socket: '' port:
3306 mariadb.org binary distributionInnoDB: Error: trying to access
page number 251010 in space 69,InnoDB: space name
news/commentsxover,InnoDB: which is outside the
tablespace bounds.InnoDB: Byte offset 0, len 16384,
i/o type 10.InnoDB: If you get this error at
mysqld startup, please check thatInnoDB: your my.cnf matches the
ibdata files that you have in theInnoDB: MySQL server.2016-06-06 08:47:46 e08 InnoDB:
Assertion failure in thread 3592 in file fil0fil.cc line
5866InnoDB: We intentionally generate
a memory trap.InnoDB: Submit a detailed bug
report to http://bugs.mysql.com.InnoDB: If you get repeated
assertion failures or crashes, evenInnoDB: immediately after the
mysqld startup, there may beInnoDB: corruption in the InnoDB
tablespace. Please refer toInnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.htmlInnoDB: about forcing
recovery.160606 8:47:46 [ERROR] mysqld
got exception 0x80000003 ;This could be because you hit a
bug. It is also possible that this binaryor one of the libraries it was
linked against is corrupt, improperly built,or misconfigured. This error can
also be caused by malfunctioning hardware.
_______________________________________________Mailing
list: https://launchpad.net/~maria-discussPost
to : maria-discuss@lists.launchpad.netUnsubscribe
: https://launchpad.net/~maria-discussMore
help : https://help.launchpad.net/ListHelp
-----Segue allegato-----
_______________________________________________
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp
