Hide Forgot
Description of problem: As reported in http://www.mysqlperformanceblog.com/2012/03/15/ext4-vs-xfs-on-ssd/ and in commented http://www.mysqlperformanceblog.com/2012/03/15/ext4-vs-xfs-on-ssd/comment-page-1/#comment-903938 There is contention problem in XFS, and the fix is available http://oss.sgi.com/archives/xfs/2012-02/msg00219.html Would be good to have a fix in RedHat, as it allows to gain performance 4x. Version-Release number of selected component (if applicable): RedHat 6.2
Not an xfsdump bug.
FWIW, that patch is not yet upstream. I'll leave it to Dave's judgement about when it may be ready for RHEL backport.
(In reply to comment #3) > FWIW, that patch is not yet upstream. I'll leave it to Dave's judgement > about when it may be ready for RHEL backport. The patch was superceded by this series of commits: 507630b xfs: use shared ilock mode for direct IO writes by default 193aec1 xfs: push the ilock into xfs_zero_eof f38996f xfs: reduce ilock hold times in xfs_setattr_size 467f789 xfs: reduce ilock hold times in xfs_file_aio_write_checks b4d05e3 xfs: avoid taking the ilock unnessecarily in xfs_qm_dqattach which have gone upstream into 3.5-rc1. I'll be backporting those.... Cheers, Dave.
Assigning over to Dave, given the last comment.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Posted to rhkernel-list: http://post-office.corp.redhat.com/archives/rhkernel-list/2012-September/msg02828.html
Patch(es) available on kernel-2.6.32-328.el6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0496.html