znaci, kako ja vidim linija greske je :
121211 16:01:39 InnoDB: Assertion failure in thread 1836 in file fsp0fsp.c line 3559
InnoDB: Failing assertion: xdes_get_bit(descr, XDES_FREE_BIT, header_page % FSP_EXTENT_SIZE, mtr) == FALSE
a evo i err fajla
121211 16:01:30 [Note] Plugin 'FEDERATED' is disabled.
121211 16:01:30 InnoDB: The InnoDB memory heap is disabled
121211 16:01:30 InnoDB: Mutexes and rw_locks use Windows interlocked functions
121211 16:01:30 InnoDB: Compressed tables use zlib 1.2.3
121211 16:01:30 InnoDB: Initializing buffer pool, size = 1.1G
121211 16:01:30 InnoDB: Completed initialization of buffer pool
121211 16:01:30 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 250 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200
121211 16:01:34 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 250 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200
121211 16:01:38 InnoDB: highest supported file format is Barracuda.
InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
121211 16:01:39 InnoDB: Assertion failure in thread 1836 in file fsp0fsp.c line 3559
InnoDB: Failing assertion: xdes_get_bit(descr, XDES_FREE_BIT, header_page % FSP_EXTENT_SIZE, mtr) == FALSE
InnoDB: 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, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB:
http://dev.mysql.com/doc/refma...n/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
121211 16:01:39 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.