Red Hat Bugzilla – Bug 690224
Veritas SF 5.1 disagrees about version of symbol aio_complete
Last modified: 2013-07-03 08:13:39 EDT
Description of problem: Just last Thursday I was able to get the Veritas Storage Foundation and High Availability 5.1 SP1PR2 test to run on RHEL 6.0. The test sets up a cluster between two systems and does some failover and filesystem checks. After it ran successfully I upgraded the kernel to the 6.1-beta version and saw the following during the test run: vxfs: module license 'Proprietary' taints kernel. vxfs: disagrees about version of symbol aio_complete vxfs: Unknown symbol aio_complete vxfs: disagrees about version of symbol aio_put_req vxfs: Unknown symbol aio_put_req Shortly thereafter I lost my connection to one of the nodes in the cluster and had to reboot it. Version-Release number of selected component (if applicable): kernel-2.6.32-122.el6.x86_64 How reproducible: Always. Steps to Reproduce: 1. Verify that the test works on RHEL6 2. Upgrade kernel to 6.1-beta 3. Run the test again. Actual results: One of the nodes in the cluster dies. Expected results: Test should complete as it does on RHEL 6. Additional info: I was able to verify that the test works with kernel-2.6.32-71.18.2.el6.x86_64.rpm.
aio_complete and aio_put_req should be on the whitelist. We'll need two bugs for this, one for the abi breakage (we can use this one) and another (that I'll file) for the whitelist addition.
Hi, Talking with Dan (the reporter), this regression seems serious, could I request that we consider this for snapshot 1 or 2 ...? (adding "snapshot 2" to devel whiteboard to get it on the radar) Regards, Brock
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Created attachment 487317 [details] fix the abi breakage
Patch(es) available on kernel-2.6.32-128.el6
I had a chance to test on kernel-2.6.32-128.el6. The vxfs complaints that I saw before have gone away. Instead I now see: vxdmp: disagrees about version of symbol __invalidate_device vxdmp: Unknown symbol __invalidate_device
(In reply to comment #10) > I had a chance to test on kernel-2.6.32-128.el6. The vxfs complaints that I > saw before have gone away. > > Instead I now see: > vxdmp: disagrees about version of symbol __invalidate_device > vxdmp: Unknown symbol __invalidate_device Right, that symbol is not on the whitelist, and will not be added to the white list. We'll need to engage Veritas about that one and see if we can get them using more standard interfaces.
It looks like they've been using this call for a while. I installed Veritas Storage Foundation 5.0MP3, which was the version run for RHEL 5.x ISV-qe testing. [root@dell-pe6800-01 certification]# nm -g /lib/modules/2.6.18-238.el5/veritas/vxvm/vxdmp.ko | grep __ U __bdevname U __bitmap_weight 000000006f6ea93d A __crc_vxvm_imc_cleanup 00000000cf454acc A __crc_vxvm_imc_deport 000000008231343d A __crc_vxvm_imc_export 000000000af88ef8 A __crc_vxvm_imc_import w __crc_vxvm_imc_setup 0000000006439a4d A __crc_vxvm_imc_unexport U __elv_add_request U __generic_unplug_device U __get_free_pages U __init_rwsem U __invalidate_device U __kmalloc U __list_add U __memcpy U __mod_timer 0000000000000000 D __this_module U __wake_up [root@dell-pe6800-01 certification]# uname -a Linux dell-pe6800-01.rhts.eng.bos.redhat.com 2.6.18-238.el5 #1 SMP Sun Dec 19 14:22:44 EST 2010 x86_64 x86_64 x86_64 GNU/Linux What's the more standard interface that they should be using?
> What's the more standard interface that they should be using? That depends on what they're trying to do. It requires their developers to explain that to us. This bug is not really a good place for that discussion, though.
Ok, marking this verified since the original vxfs symbol problem has gone away.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0542.html