Elena Stepanova added a comment - 2014-07-08 15:14 Hi, Did you change configuration or move your database-related files (physically, on disk) together with the upgrade? Have you had any hardware or environment changes, especially related to storage? Do your datadir, innodb_data_home_dir, and innodb_data_file_path all point at a local storage? Please attach your ini file(s) and/or SHOW VARIABLES output.

Adrian Nicoara added a comment - 2014-07-08 15:47 Here are Ini files and SHOW VARIABLES. I didn't changed anything before and after upgrade. I only replaced all files except "data" folder and i ran mysql upgrade

Elena Stepanova added a comment - 2014-07-08 15:52 - edited Hi, Is this F: disk where the datadir/basedir are located a normal local HDD/SSD, or is it a network or an external storage? Do you have any kind of monitoring on the machine? Does it show any errors related to access to disk F:?

Adrian Nicoara added a comment - 2014-07-08 16:52 Hello, All(C,D,E,F,G,H) are partitions on the same disk, i use every partition for specific kinds of operations. On F i have the database and all my php projects and sources, I check the disk frequently(once at 2 days) for errors, and everything seems to work, fine. All the other stuffs works without any problems. I never had a disk read/write error. I also checked SMART monitor and windows performance logs and i saw no error regarding disk access. The disk is 1 year old and is used on a high perfomance dell xps laptop. I have 8GB of RAM. I can try to downgrade and check if the errors still persist.

Elena Stepanova added a comment - 2014-07-19 12:30 Thanks for the information. Actually, it's a weird error in itself: "InnoDB: 512 bytes should have been written, only 512 were written." Maybe this weirdness will somehow help jplindst to see what could cause it.

Adrian Nicoara added a comment - 2014-07-21 17:55 - edited Hello, I tested a while 10.0.10 and didn't had problems. I did the same stuffs(my workflow) and didn't crashed, everything worked fine. I upgraded today again to 10.0.12 and imported the sql files and it worked until i had to do something with the full text indexes. For example I inserted in a new table some rows, and after i saw that i forgot to create the full text indexes for the columns, so i created them and then inserted a new row for my application testing and then DB crashed again(server process died) The row i wanted to insert didn't commit into the DB. I didn't used transactions, just the regular INSERT INTO. I have a text column inside but the length of the data was very small(about 20 characters). BTW I'm using ZEND Framework 1 DB adapter and i use the php 5.4 builtin connector. Nothing on the log. If i want to reproduce it I can't, but if I use it for normal work flow it crashes from time to time Hopefully i get a test case for it soon.

Adrian Nicoara added a comment - 2014-07-21 18:25 After DB restart : InnoDB: Transaction 114408 was in the XA prepared state. InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 0 row operations to undo InnoDB: Trx id counter is 114688 InnoDB: Last MySQL binlog file position 0 48142942, file name .\mysql-bin.000010 140721 18:23:09 [Note] InnoDB: 128 rollback segment(s) are active. InnoDB: Starting in background the rollback of uncommitted transactions 2014-07-21 18:23:09 2124 InnoDB: Rollback of non-prepared transactions completed So query was commited finally after restart.

Jan Lindström (Inactive) added a comment - 2014-07-22 10:10 This sounds like a permission problem, your my.ini is that correct one, why no innodb related configuration is not given ? Note that when InnoDB creates indexes, it creates temporal files, make sure that these temporal files are created on place where there is enough space and sufficient permissions.

Adrian Nicoara added a comment - 2014-07-22 11:10 Hello, There is no problem with permissions. Space is a lot. FS is NTFS. I dont use security stuffs because is dev env. Mariadb has access to write anywhere. This things happens from time to time. Here is the full start log. I cropped it last time to what i was thinking that is needed. 140721 18:22:59 [Note] InnoDB: Using mutexes to ref count buffer pool pages 140721 18:22:59 [Note] InnoDB: The InnoDB memory heap is disabled 140721 18:22:59 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 140721 18:22:59 [Note] InnoDB: Compressed tables use zlib 1.2.3 140721 18:22:59 [Note] InnoDB: Not using CPU crc32 instructions 140721 18:22:59 [Note] InnoDB: Initializing buffer pool, size = 128.0M 140721 18:22:59 [Note] InnoDB: Completed initialization of buffer pool 140721 18:22:59 [Note] InnoDB: Highest supported file format is Barracuda. 140721 18:22:59 [Note] InnoDB: The log sequence numbers 45902453 and 45902453 in ibdata files do not match the log sequence number 126208445 in the ib_logfiles! 140721 18:22:59 [Note] InnoDB: Database was not shutdown normally! 140721 18:22:59 [Note] InnoDB: Starting crash recovery. 140721 18:22:59 [Note] InnoDB: Reading tablespace information from the .ibd files... 140721 18:23:08 [Note] InnoDB: Restoring possible half-written data pages 140721 18:23:08 [Note] InnoDB: from the doublewrite buffer... InnoDB: Transaction 114408 was in the XA prepared state. InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 0 row operations to undo InnoDB: Trx id counter is 114688 InnoDB: Last MySQL binlog file position 0 48142942, file name .\mysql-bin.000010 140721 18:23:09 [Note] InnoDB: 128 rollback segment(s) are active. InnoDB: Starting in background the rollback of uncommitted transactions 2014-07-21 18:23:09 2124 InnoDB: Rollback of non-prepared transactions completed 140721 18:23:10 [Note] InnoDB: Waiting for purge to start 140721 18:23:10 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.17-65.0 started; log sequence number 126208445 140721 18:23:10 [Note] Plugin 'FEEDBACK' is disabled. 140721 18:23:10 [Note] Recovering after a crash using mysql-bin 140721 18:23:16 [Note] Starting crash recovery... 2014-07-21 18:23:16 1864 InnoDB: Starting recovery for XA transactions... 2014-07-21 18:23:16 1864 InnoDB: Transaction 114408 in prepared state after recovery 2014-07-21 18:23:16 1864 InnoDB: Transaction contains changes to 1 rows 2014-07-21 18:23:16 1864 InnoDB: 1 transactions in prepared state after recovery 140721 18:23:16 [Note] Found 1 prepared transaction(s) in InnoDB 140721 18:23:16 [Note] Crash recovery finished. 140721 18:23:16 [Note] Server socket created on IP: '::'. 140721 18:23:17 [Note] Event Scheduler: Loaded 0 events 140721 18:23:17 [Note] MySQL: ready for connections. Version: '10.0.12-MariaDB-log' socket: '' port: 3306 mariadb.org binary distribution 2014-07-21 18:46:09 15dc InnoDB: FTS Optimize Removing table wct/#sql2-1864-20 2014-07-21 18:46:25 15dc InnoDB: FTS Optimize Removing table timpmoca/#sql2-1864-23 2014-07-21 18:46:33 15dc InnoDB: FTS Optimize Removing table timpmoca/#sql2-1864-23 2014-07-21 18:50:31 15dc InnoDB: FTS Optimize Removing table timpmoca/#sql2-1864-22 2014-07-21 18:50:36 15dc InnoDB: FTS Optimize Removing table timpmoca/#sql2-1864-22 2014-07-21 18:51:02 15dc InnoDB: FTS Optimize Removing table wct/#sql2-1864-24 2014-07-21 18:51:06 15dc InnoDB: FTS Optimize Removing table wct/#sql2-1864-24