|
Hi, I’ve run into a kernel bug, triggered by using gluster through FUSE. Wondering if any of you have encountered a similar problem and have worked around it by using an updated version of the kernel, gluster, or FUSE. Here’s
the bug: KERNEL: /usr/lib/debug/lib/modules/2.6.32-220.el6.x86_64/vmlinux DUMPFILE: /var/crash/127.0.0.1-2013-12-21-13:55:32/vmcore [PARTIAL DUMP] CPUS: 64 DATE: Sat Dec 21 13:52:33 2013 UPTIME: 16 days, 23:17:25 LOAD AVERAGE: 3.22, 3.36, 3.57 TASKS: 5598 NODENAME: uca-amm3.cnda.avaya.com RELEASE: 2.6.32-220.el6.x86_64 VERSION: #1 SMP Wed Nov 9 08:03:13 EST 2011 MACHINE: x86_64 (2892 Mhz) MEMORY: 32 GB PANIC: "kernel BUG at fs/inode.c:322!" PID: 259 COMMAND: "kswapd1" TASK: ffff880433108b00 [THREAD_INFO: ffff88043310e000] CPU: 8 STATE: TASK_RUNNING (PANIC) crash> bt PID: 259 TASK: ffff880433108b00 CPU: 8 COMMAND: "kswapd1" #0 [ffff88043310f7b0] machine_kexec at ffffffff81031fcb #1 [ffff88043310f810] crash_kexec at ffffffff810b8f72 #2 [ffff88043310f8e0] oops_end at ffffffff814f04b0 #3 [ffff88043310f910] die at ffffffff8100f26b #4 [ffff88043310f940] do_trap at ffffffff814efda4 #5 [ffff88043310f9a0] do_invalid_op at ffffffff8100ce35 #6 [ffff88043310fa40] invalid_op at ffffffff8100bedb [exception RIP: clear_inode+248] RIP: ffffffff81190fb8 RSP: ffff88043310faf0 RFLAGS: 00010202 RAX: 0000000000000000 RBX: ffff8800245ce980 RCX: 0000000000000001 RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8800245ce980 RBP: ffff88043310fb00 R8: 0000000000000000 R9: 000000000000000d R10: 0000000000000002 R11: 0000000000000001 R12: ffffffff81fbf340 R13: 0000000000000000 R14: ffff8800888014f8 R15: 0000000000000001 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #7 [ffff88043310fb08] generic_delete_inode at ffffffff811916f6 #8 [ffff88043310fb38] iput at ffffffff81190612 #9 [ffff88043310fb58] dentry_iput at ffffffff8118d170 #10 [ffff88043310fb78] d_kill at ffffffff8118d2d1 #11 [ffff88043310fb98] __shrink_dcache_sb at ffffffff8118d666 #12 [ffff88043310fc38] shrink_dcache_memory at ffffffff8118d7e9 #13 [ffff88043310fc98] shrink_slab at ffffffff811299aa #14 [ffff88043310fcf8] balance_pgdat at ffffffff8112c75d #15 [ffff88043310fe28] kswapd at ffffffff8112caf6 #16 [ffff88043310fee8] kthread at ffffffff81090886 #17 [ffff88043310ff48] kernel_thread at ffffffff8100c14a This bug is reported here:
http://fuse.996288.n3.nabble.com/Kernel-panic-when-using-fuse-with-distributed-filesystem-while-doing-heavy-i-o-td10373.html, which shows that this bug is reported on two different bugzilla bug reports
https://bugzilla.redhat.com/show_bug.cgi?id=644085 and
https://bugzilla.kernel.org/show_bug.cgi?id=15927. All of these reports mention using FUSE with high volume on the 2.6 kernel (which we are using). There’s another entry on the red hat network,
but I can’t see it (don’t have the subscription)
https://access.redhat.com/site/solutions/72383 Thanks, Anne |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
