The fs is oopsing when trying to remove a entry from the orphan dir. It could be that that orphaned inode is corrupted. You could try running fsck.ocfs2 - fy /dev/sdX. Better if you ping Novell support for assistance.
On May 17, 2010, at 6:01 AM, Georg Höllrigl <georg.hoellr...@xidras.com> wrote: > Hi Folks, > > I´v got a strange Problem regarding accessing or writing to an OCFS2 > mount. If I try writing or > sometimes changing path to the OCFS2 mount point the process for > example a "vi" or a "tail" is put > to into the process state D. > I´v noticed that on one of my two nodes the [ocfs2_wq] is missing. A > fter a reboot of the node it is > running but dieing on the other one and vice versa. > > A dmesg tells me : > > Pid: 8423, comm: ocfs2_wq Tainted: G 2.6.27.45-0.1-xen #1 > RIP: e030:[<ffffffffa0385203>] [<ffffffffa0385203>] > ocfs2_commit_truncate+0x1d8/0x107e [ocfs2] > RSP: e02b:ffff8805e1f0dbd0 EFLAGS: 00010286 > RAX: 0000000000000020 RBX: 0000000000000000 RCX: ffff880556369340 > RDX: ffff880556369360 RSI: ffff8800c4c46030 RDI: ffff8800ba335408 > RBP: 0000000000000000 R08: 0000000000fc0000 R09: 00000000010eb960 > R10: 00002525802498c8 R11: 0000000000000000 R12: 0000000000000000 > R13: ffff880274710d80 R14: ffff8800ba325528 R15: ffff8805e4a67000 > FS: 00007f47809036f0(0000) GS:ffffffff80763080(0000) knlGS:0000000000000000 > CS: e033 DS: 0000 ES: 0000 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 > Process ocfs2_wq (pid: 8423, threadinfo ffff8805e1f0c000, task > ffff8805e09321c0) > Stack: 0000000000000000 0000000000000000 ffff8800ba325528 > ffff8805e1737ae0 > ffff8800ba335678 ffff8805e4a67000 ffff8805e075ace0 0000000000000000 > ffff8805e075ac28 ffff880556369340 ffff8800ba325080 00000000ccf749d8 > Call Trace: > [<ffffffffa03a4a5b>] ocfs2_delete_inode+0x842/0x10f1 [ocfs2] > [<ffffffff802b3520>] generic_delete_inode+0xf9/0x1a3 > [<ffffffffa03a85c6>] ocfs2_complete_recovery+0x5f4/0x713 [ocfs2] > [<ffffffff80243381>] run_workqueue+0xbe/0x18b > [<ffffffff80243526>] worker_thread+0xd8/0xe7 > [<ffffffff802466a4>] kthread+0x47/0x73 > [<ffffffff8020bd69>] child_rip+0xa/0x11 > > Code: d3 3c a0 89 d2 48 c7 c7 a5 14 3d a0 31 c0 e8 72 fd 0d e0 e9 1e > 0e 00 00 48 8b 54 24 48 48 63 > 02 48 c1 e0 04 48 01 c2 48 8b 5a 10 <8b> 43 04 66 85 c0 75 35 48 8b > 42 08 49 8b be f8 00 00 00 48 c7 > RIP [<ffffffffa0385203>] ocfs2_commit_truncate+0x1d8/0x107e [ocfs2] > RSP <ffff8805e1f0dbd0> > CR2: 0000000000000004 > ---[ end trace fc0c127e36c8fbfa ]--- > > > > In this setup I use : 2.6.27.45-0.1-xen with SUSE Linux Enterprise > Server 11 (x86_64) > and > > > ocfs2-kmp-default-1.4_2.6.27.45_0.1-4.3.4 > ocfs2-kmp-xen-1.4_2.6.27.45_0.1-4.3.4 > ocfs2-tools-o2cb-1.4.1-29.1 > ocfs2console-1.4.1-24.8.11 > ocfs2-tools-1.4.1-29.1 > > Any ideas or comments about how to fix this would be appreciated. > > Thx > > > Georg > > _______________________________________________ > Ocfs2-users mailing list > Ocfs2-users@oss.oracle.com > http://oss.oracle.com/mailman/listinfo/ocfs2-users _______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
