Hide Forgot
Description of problem: When running our coherency test case, after the test file is removed from the first node, another node will panic. If the removes are dropped from the test suite, the suite will run to completion. GFS2: fsid=buzzez:brawl0.3: fatal assertion failed ------------[ cut here ]------------ kernel BUG at fs/gfs2/inode.h:67! invalid opcode: 0000 [#1] SMP last sysfs file: /sys/devices/system/cpu/cpu15/cache/index2/shared_cpu_map CPU 3 Modules linked in: sctp libcrc32c gfs2 dlm configfs sunrpc bonding ipv6 dm_mirror dm_region_hash dm_log power_meter hwmon microcode dcdbas se rio_raw ghes hed iTCO_wdt iTCO_vendor_support qla2xxx scsi_transport_fc scsi_tgt i7core_edac edac_core sg bnx2 ext4 mbcache jbd2 sr_mod cdrom sd_mod crc_t10dif pata_acpi ata_generic ata_piix mpt2sas scsi_transport_sas raid_class dm_mod [last unloaded: speedstep_lib] Modules linked in: sctp libcrc32c gfs2 dlm configfs sunrpc bonding ipv6 dm_mirror dm_region_hash dm_log power_meter hwmon microcode dcdbas se rio_raw ghes hed iTCO_wdt iTCO_vendor_support qla2xxx scsi_transport_fc scsi_tgt i7core_edac edac_core sg bnx2 ext4 mbcache jbd2 sr_mod cdrom sd_mod crc_t10dif pata_acpi ata_generic ata_piix mpt2sas scsi_transport_sas raid_class dm_mod [last unloaded: speedstep_lib] Pid: 2775, comm: delete_workqueu Not tainted 2.6.32-131.0.10.el6.x86_64 #1 PowerEdge R710 RIP: 0010:[<ffffffffa0319f9c>] [<ffffffffa0319f9c>] do_strip+0x46c/0x470 [gfs2] RSP: 0018:ffff88061f04bb20 EFLAGS: 00010286 RAX: 0000000000000039 RBX: ffff88030f8238f0 RCX: 0000000000000ecc RDX: 0000000000000000 RSI: 0000000000000046 RDI: 0000000000000246 RBP: ffff88061f04bba0 R08: ffffffff81b9e280 R09: 0000000000000000 R10: ffff8803215bd8c8 R11: 0000000000000000 R12: ffff8803216340e8 R13: ffff88030f8875a8 R14: ffff880321635000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff880028220000(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 0000003b12454df0 CR3: 0000000001a25000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process delete_workqueu (pid: 2775, threadinfo ffff88061f04a000, task ffff8806208e0a80) Stack: ffff88061f04bb50 000000000000000a ffff88061b497000 ffff88030f823c08 <0> 000000011b497000 ffff88030f8875a8 0000000a00000002 ffff88031fd084c0 <0> ffff88031fd08a40 ffff88030f88b470 ffff88030f8875a8 ffff8803216340e8 Call Trace: [<ffffffffa031a060>] recursive_scan.clone.0+0xc0/0x1c0 [gfs2] [<ffffffff8115aaf5>] ? kmem_cache_alloc_notrace+0x115/0x130 [<ffffffffa031a26d>] trunc_dealloc+0x10d/0x130 [gfs2] [<ffffffffa0321f25>] ? gfs2_ea_dealloc+0x65/0x5d0 [gfs2] [<ffffffffa0326816>] ? gfs2_glock_wait+0x36/0x40 [gfs2] [<ffffffffa0329011>] ? gfs2_glock_nq+0x191/0x370 [gfs2] [<ffffffffa031a2a0>] gfs2_file_dealloc+0x10/0x20 [gfs2] [<ffffffffa03431ca>] gfs2_delete_inode+0x1aa/0x280 [gfs2] [<ffffffffa03430ad>] ? gfs2_delete_inode+0x8d/0x280 [gfs2] [<ffffffffa0343020>] ? gfs2_delete_inode+0x0/0x280 [gfs2] [<ffffffff8118d11e>] generic_delete_inode+0xde/0x1d0 [<ffffffffa0327940>] ? delete_work_func+0x0/0x80 [gfs2] [<ffffffff8118d275>] generic_drop_inode+0x65/0x80 [<ffffffffa0341c4e>] gfs2_drop_inode+0x2e/0x30 [gfs2] [<ffffffff8118c0e2>] iput+0x62/0x70 [<ffffffffa0327994>] delete_work_func+0x54/0x80 [gfs2] [<ffffffff81088830>] worker_thread+0x170/0x2a0 [<ffffffff8108e160>] ? autoremove_wake_function+0x0/0x40 [<ffffffff810886c0>] ? worker_thread+0x0/0x2a0 [<ffffffff8108ddf6>] kthread+0x96/0xa0 [<ffffffff8100c1ca>] child_rip+0xa/0x20 [<ffffffff8108dd60>] ? kthread+0x0/0xa0 [<ffffffff8100c1c0>] ? child_rip+0x0/0x20 Code: fe ff ff 48 89 df 48 89 4d 90 e8 80 65 02 00 48 8b 4d 90 e9 77 ff ff ff 48 8b 83 08 01 00 00 48 8b b8 90 02 00 00 e8 04 ae 02 00 <0f> 0 b eb fe 55 48 89 e5 48 83 ec 70 48 89 5d d8 4c 89 65 e0 4c Version-Release number of selected component (if applicable): kernel-2.6.32-131.0.10.el6.x86_64 How reproducible: Easily Steps to Reproduce: 1. Run coherency test case 2. 3. Actual results: Expected results: Additional info:
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
*** This bug has been marked as a duplicate of bug 699956 ***