Thanks Milosz, I will test and check if I can apply the patch in my current kernel - 2.6.32-431.11.2.el6.x86_64 Upgrading the kernel to 3.x currently not an option for my systems since some does not work in kernel 3.x. Regards, Fernando -----Original Message----- From: Milosz Tanski [mailto:milosz@xxxxxxxxx] Sent: Friday, May 09, 2014 8:11 AM To: Fernando Santos Cc: linux-cachefs@xxxxxxxxxx Subject: Re: kernel BUG at fs/fscache/operation.c:384! Fernando, I think that's a bug that's been fixed in the upstream kernel. Somewhere around the time of ~ 3.10. Here's the link to the fix: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1bb4b7f98f361132ea322834515334d95b93c184 On Fri, May 9, 2014 at 11:03 AM, Fernando Santos <fernando.santos@xxxxxxxxxxxxxxxxxxxxx> wrote: > Hi, > > It happens again twice already since I posted this bug (last May 3r > and today May 9th), and it seems the same error. So far no changes > were made in the system. Here is the summary of the crash report: > > KERNEL: /usr/lib/debug/lib/modules/2.6.32-431.11.2.el6.x86_64/vmlinux > DUMPFILE: vmcore [PARTIAL DUMP] > CPUS: 24 > DATE: Fri May 9 14:10:00 2014 > UPTIME: 6 days, 00:02:57 > LOAD AVERAGE: 0.45, 0.61, 0.64 > TASKS: 697 > NODENAME: web141.dl > RELEASE: 2.6.32-431.11.2.el6.x86_64 > VERSION: 0000001 SMP Tue Mar 25 19:59:55 UTC 2014 > MACHINE: x86_64 (2299 Mhz) > MEMORY: 48 GB > PANIC: "kernel BUG at fs/fscache/operation.c:385!" > PID: 100 > COMMAND: "events/1" > TASK: ffff88067679aaa0 [THREAD_INFO: ffff8806767c2000] > CPU: 1 > STATE: TASK_RUNNING (PANIC) > > Attached here is the back trace and logs for the latest crash. When > checking on last command, it always seems like it was rebooted on > purpose but nobody is logged in and no crons/script setup to reboot it: > > [root@xxxxxxxxx ~]# last | more > root pts/1 inf001.dl Fri May 9 14:26 still logged in root pts/0 > inf001.dl Fri May 9 14:23 still logged in reboot system boot > 2.6.32-431.11.2. Fri May 9 14:13 - 14:50 (00:36) root pts/0 inf001.dl > Thu May 8 21:19 - 23:48 (02:28) root pts/1 inf001.dl Thu May 8 15:26 - > 16:08 (00:41) root pts/0 inf001.dl Wed May 7 18:46 - 18:46 (00:00) > root pts/1 inf001.dl Wed May 7 16:56 - 16:58 (00:01) root pts/1 > inf001.dl Wed May 7 16:56 - 16:56 (00:00) root pts/2 inf001.dl Wed May > 7 15:03 - 15:14 (00:10) root pts/1 inf001.dl Wed May 7 15:01 - 15:19 > (00:17) root pts/0 inf001.dl Wed May 7 13:57 - 13:57 (00:00) root > pts/1 inf001.dl Tue May 6 22:01 - 22:05 (00:04) root pts/1 inf001.dl > Mon May 5 16:28 - 16:28 (00:00) root pts/0 inf001.dl Mon May 5 14:26 - > 14:44 (00:18) reboot system boot 2.6.32-431.11.2. Sat May 3 14:06 - > 14:50 (6+00:43) root pts/0 inf001.dl Thu May 1 22:08 - 23:15 (01:06) > > Please help in troubleshooting and let me know suggesting in resolving > the error. > > Thanks, > Fernando > > -- > Linux-cachefs mailing list > Linux-cachefs@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cachefs -- Milosz Tanski CTO 10 East 53rd Street, 37th floor New York, NY 10022 p: 646-253-9055 e: milosz@xxxxxxxxx -- Linux-cachefs mailing list Linux-cachefs@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cachefs
