lp:1055547 repeatable on XFS

Bug #1190779 reported by Raghavendra D Prabhu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Medium
Alexey Kopytov
2.0
Fix Released
Medium
Alexey Kopytov
2.1
Fix Released
Medium
Alexey Kopytov

Bug Description

I am able to repeat this on XFS during prepare:

====================================
120629 6:12:19 InnoDB: Shutdown completed; log sequence number 3351590558
InnoDB: Error: tried to read 2048 bytes at offset 0 0.
InnoDB: Was only able to read 0.
120629 6:12:19 InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
innobackupex: Error:
==========================================

Does PXB testsuite run tests on XFS?

Tags: pxc

Related branches

affects: percona-xtradb-cluster → percona-xtrabackup
description: updated
Revision history for this message
Alexey Kopytov (akopytov) wrote :

It's not clear why it doesn't fail before prepare, as exactly the same I/O requests are issued. I think the fix is to disable O_DIRECT when manipulating xtrabackup_logfile before and after recovery.

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

The details of XFS filesystem where this happened (for those reproducing this):

xfs_info /dev/sda7
==========================

meta-data=/dev/sda7 isize=256 agcount=4, agsize=1387072 blks
         = sectsz=512 attr=2
data = bsize=4096 blocks=5548288, imaxpct=25
         = sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal bsize=4096 blocks=2709, version=2
         = sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0

Pretty much standard settings.

tags: added: pxc
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-640

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.