[Ocfs2-users] ocfs2_delete_inode kernel bug

Andre Nathan andre at digirati.com.br
Tue Oct 26 02:43:49 PDT 2010


On Thu, 2010-10-21 at 10:52 -0700, Sunil Mushran wrote:
> That said, the first issue (-17) is a known one that was fixed in
> 2.6.34.

I'm still seeing the same messages even after upgrading to 2.6.35:

[96387.917789] (ocfs2_wq,3467,0):ocfs2_delete_inode:1043 ERROR: status =
-17
[96387.920621] (ocfs2_wq,3467,0):ocfs2_query_inode_wipe:919 ERROR: Inode
16660075 (on-disk 16660075) not orphaned! Disk flags  0x9, inode flags
0x20
[96387.920724] (ocfs2_wq,3467,0):ocfs2_delete_inode:1043 ERROR: status =
-17
[96387.920801] ------------[ cut here ]------------
[96387.920847] kernel BUG at /mnt/ubuntu-maverick/fs/inode.c:1325!
[96387.920898] invalid opcode: 0000 [#1] SMP 
[96387.920948] last sysfs
file: /sys/devices/system/cpu/cpu15/cache/index2/shared_cpu_map
[96387.921031] CPU 0 
[96387.921040] Modules linked in: ocfs2 quota_tree drbd lru_cache
ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue
configfs dummy aoe bonding joydev ixgbe ioatdma i7core_edac edac_core
shpchp lp mdio hed parport raid10 raid456 async_pq async_xor xor
async_memcpy async_raid6_recov usbhid hid e1000e megaraid_sas igb dca
raid6_pq async_tx raid1 raid0 multipath linear
[96387.921449] 
[96387.921486] Pid: 3467, comm: ocfs2_wq Not tainted 2.6.35-23-server
#36 S5520HC/S5520HC
[96387.922815] RIP: 0010:[<ffffffff8116a259>]  [<ffffffff8116a259>] iput
+0x69/0x70
[96387.922902] RSP: 0018:ffff880455d19cd0  EFLAGS: 00010246
[96387.922951] RAX: 0000000000000020 RBX: ffff8802a40823e0 RCX:
0200000000004081
[96387.923005] RDX: 0000000000000000 RSI: ffffea00093e1c00 RDI:
ffff8802a40823e0
[96387.923060] RBP: ffff880455d19ce0 R08: 6018000000000000 R09:
fd3df85c52072c03
[96387.923115] R10: ffff8802a4084aa0 R11: 0000000000000001 R12:
ffff8802a4082338
[96387.923169] R13: ffff8802a40842e0 R14: 0000000000000000 R15:
ffff88045821adc0
[96387.923225] FS:  0000000000000000(0000) GS:ffff880001e00000(0000)
knlGS:0000000000000000
[96387.923309] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[96387.923359] CR2: 00007f3006207f70 CR3: 0000000456689000 CR4:
00000000000006f0
[96387.923413] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[96387.923468] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[96387.923523] Process ocfs2_wq (pid: 3467, threadinfo ffff880455d18000,
task ffff88045821adc0)
[96387.923608] Stack:
[96387.923644]  ffff880455d19ce0 ffff8802a4081f00 ffff880455d19d50
ffffffffa039ff4c
[96387.923707] <0> ffff8802dc048a40 ffff880455d19d10 0000000000000282
ffff88045821b218
[96387.923801] <0> ffff880455d19d60 ffff8802a40823e0 0000000000000000
ffff88018facdc00
[96387.923926] Call Trace:
[96387.923985]  [<ffffffffa039ff4c>] ocfs2_recover_orphans+0xfc/0x230
[ocfs2]
[96387.924054]  [<ffffffffa03a0287>] ocfs2_complete_recovery+0x207/0x6a0
[ocfs2]
[96387.924112]  [<ffffffff810710e8>] ? add_timer+0x18/0x20
[96387.924176]  [<ffffffffa03a0080>] ? ocfs2_complete_recovery+0x0/0x6a0
[ocfs2]
[96387.924232]  [<ffffffff8107a295>] run_workqueue+0xc5/0x1a0
[96387.924283]  [<ffffffff8107a413>] worker_thread+0xa3/0x110
[96387.924334]  [<ffffffff8107f0b0>] ? autoremove_wake_function+0x0/0x40
[96387.924388]  [<ffffffff8107a370>] ? worker_thread+0x0/0x110
[96387.924438]  [<ffffffff8107eb56>] kthread+0x96/0xa0
[96387.924487]  [<ffffffff8100aee4>] kernel_thread_helper+0x4/0x10
[96387.924539]  [<ffffffff8107eac0>] ? kthread+0x0/0xa0
[96387.924587]  [<ffffffff8100aee0>] ? kernel_thread_helper+0x0/0x10
[96387.924638] Code: 30 48 c7 c0 10 b8 16 81 48 85 d2 74 12 48 8b 42 20
48 c7 c2 10 b8 16 81 48 85 c0 48 0f 44 c2 48 89 df ff d0 48 83 c4 08 5b
c9 c3 <0f> 0b eb fe 0f 1f 00 55 48 89 e5 41 55 41 54 53 48 83 ec 08 0f 
[96387.925001] RIP  [<ffffffff8116a259>] iput+0x69/0x70
[96387.925051]  RSP <ffff880455d19cd0>
[96387.925453] ---[ end trace fe0ba9ac9551a18e ]---


Do you know what could this be?

Best regards,
Andre




More information about the Ocfs2-users mailing list