Comment 13 for bug 870119

okay

Matt

On Jun 15, 2012, at 4:03 AM, Stewart Smith wrote:

> As 1.6 is the old stable release, I don't think we need to fix there
> unless somebody explicitly needs it. If you do need a fix for this bug,
> contact us (Percona) and we can sort something out (or post here).
>
> ** Changed in: percona-xtrabackup/1.6
> Milestone: 1.6.7 => None
>
> ** Changed in: percona-xtrabackup/1.6
> Status: Triaged => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/870119
>
> Title:
> assertion failure while trying to read InnoDB partition
>
> Status in Percona XtraBackup:
> Triaged
> Status in Percona XtraBackup 1.6 series:
> Won't Fix
> Status in Percona XtraBackup 2.0 series:
> Triaged
>
> Bug description:
> I am consistently getting the following error when trying to backup a
> partitioned InnoDB table. InnoDB is configured with file_per_table.
> The particular partition on which the read fails varies. There does
> not seem to be file corruption since I can stop/restart the database
> without problem and InnoDB itself reports no problems with the table.
> It is a large table with ~500 partitions.
>
>
> InnoDB: Error: tried to read 1048576 bytes at offset 1 60817408.
> InnoDB: Was only able to read 0.
> InnoDB: Fatal error: cannot read from file. OS error number 17.
> 111007 0:09:02 InnoDB: Assertion failure in thread 140202726008576 in file os/os0file.c line 2460
> InnoDB: We intentionally generate a memory trap.
>
>
> System configuration is as follows:
> Ubuntu Linux 10.04 LTS kernel 2.6.32-25-server x86_64
> MySQL Ver 14.14 Distrib 5.1.41, for debian-linux-gnu (x86_64) using readline 6.1
> InnoDB Plugin version 1.0.5
> xtrabackup version 1.6.3 for Percona Server 5.1.55 unknown-linux-gnu (x86_64) (revision id: undefined)
>
> xtrabackup is invoked with 16 parallel threads.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/percona-xtrabackup/+bug/870119/+subscriptions