List:General Discussion« Previous MessageNext Message »
From:Reindl Harald Date:November 21 2013 6:03pm
Subject:Re: InnoDB error 5
View as plain text  

Am 21.11.2013 18:59, schrieb Paul Halliday:
> It was indeed corruption :/ what a day. I was able to move everything
> over to another partition and have managed to get mysql up and running
> again.  There was a single file I could not, an .idb (the ,.frm is
> there). Is it possible to fix this from ibdata or the logs?

no - that's what backups are for
lesson learned the hard way

for production you have usually a replication-slave in the same
network which is regulary stopped and it's datadir rsynced to a
offsite-backup (one possible backup strategy) and so if one
server get a corrupt filesystem there is a just-in-time backup
while if things are going terrible wrong (power outage and the
slave is also corrupt you rsync back the slightly outdated
offsite backup

> On Thu, Nov 21, 2013 at 9:46 AM, Manuel Arostegui <manuel@stripped> wrote:
>> 2013/11/21 Reindl Harald <h.reindl@stripped>
>>>
>>> Am 21.11.2013 13:51, schrieb Paul Halliday:
>>>> Had a system crash this morning and I can't seem to get mysql back up
>>>> and running. This is the error:
>>>>
>>>> InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
>>>> 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
>>>> 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
>>>> 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86
>>>> 87 88 89 90 91 92 93 94 95 96 97 98 99 2013-11-21 08:47:26 1570
>>>> [ERROR] InnoDB: Tried to read 16384 bytes at offset 589824. Was only
>>>> able to read -1.
>>>> 2013-11-21 08:47:26 802808c00  InnoDB: Operating system error number 5
>>>> in a file operation.
>>>> InnoDB: Error number 5 means 'Input/output error'.
>>>> InnoDB: Some operating system error numbers are described at
>>>> InnoDB:
>>> http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
>>>> 2013-11-21 08:47:26 802808c00  InnoDB: File operation call: 'read'
>>>> returned OS error 105.
>>>> 2013-11-21 08:47:26 802808c00  InnoDB: Cannot continue operation.
>>>>
>>>> I followed that link but it doesn't tell me anything outside of what
>>>> is above. Can I fix this?
>>>
>>> i would look in the *system logs* because this pretty sure comes
>>> from the underlying operating system and is *not* mysql specific
>>> which is also in the message statet with "returned OS error 105"
>>>
>>>
> http://lxr.free-electrons.com/source/include/uapi/asm-generic/errno-base.h#L8
>>>
>>>
>> Looks like a broken disk or FS corruption :-(


Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Thread
InnoDB error 5Paul Halliday21 Nov
  • Re: InnoDB error 5Reindl Harald21 Nov
    • Re: InnoDB error 5Manuel Arostegui21 Nov
      • Re: InnoDB error 5Nick Cameo21 Nov
      • Re: InnoDB error 5Paul Halliday21 Nov
        • Re: InnoDB error 5Reindl Harald21 Nov
Re: InnoDB error 5Nick Cameo21 Nov
  • Re: InnoDB error 5Shawn Green21 Nov