From: Guido Winkelmann <guido-ceph@thisisnotatest.de>
To: ceph-devel@vger.kernel.org
Subject: Kernel crash
Date: Wed, 30 May 2012 19:35:35 +0200 [thread overview]
Message-ID: <1934548.axdquzlaJh@pc10> (raw)
Hi,
I just saw a kernel crash on one of my machines. It had the cephfs from the
ceph cluster mounted using the in-kernel client:
[522247.751071] [<ffffffff814d3383>] ? release_sock+0xe3/0x110
[522247.751182] [<ffffffff815ea438>] __bad_area_nosemaphore+0x1d1/0x1f0
[522247.751290] [<ffffffff815ea46a>] bad_area_nosemaphore+0x13/0x15
[522247.751397] [<ffffffff815f7b76>] do_page_fault+0x416/0x4f0
[522247.751503] [<ffffffff814ce5dd>] ? sock_recvmsg+0x11d/0x140
[522247.751611] [<ffffffff812c0ea6>] ? cpumask_next_and+0x36/0x50
[522247.751718] [<ffffffff815f4475>] page_fault+0x25/0x30
[522247.751828] [<ffffffffa03ccba4>] ? ceph_x_destroy_authorizer+0x14/0x40
[libceph]
[522247.751995] [<ffffffffa040f9be>] get_authorizer+0x6e/0x140 [ceph]
[522247.752104] [<ffffffff814ce646>] ? kernel_recvmsg+0x46/0x60
[522247.752213] [<ffffffffa03b969a>] prepare_write_connect+0x17a/0x270
[libceph]
[522247.752378] [<ffffffffa03bba75>] con_work+0x755/0x2c40 [libceph]
[522247.752486] [<ffffffff810876a3>] ? update_rq_clock+0x43/0x1b0
[522247.752598] [<ffffffffa03bb320>] ? ceph_msg_new+0x2d0/0x2d0 [libceph]
[522247.752707] [<ffffffff810747ae>] process_one_work+0x11e/0x470
[522247.752815] [<ffffffff810755bf>] worker_thread+0x15f/0x360
[522247.752925] [<ffffffff81075460>] ? manage_workers+0x230/0x230
[522247.753032] [<ffffffff81079da3>] kthread+0x93/0xa0
[522247.753137] [<ffffffff815fd2a4>] kernel_thread_helper+0x4/0x10
[522247.753245] [<ffffffff81079d10>] ?
kthread_freezable_should_stop+0x70/0x70
[522247.753355] [<ffffffff815fd2a0>] ? gs_change+0x13/0x13
[522247.753459] ---[ end trace b9ba686594d99f89 ]---
These lines are all that I could still read on the screen. (Good thing there's
Opens Source OCR programs out there...) I do not know how to extract more
information about that crash (scrolling up does not work), but I'm leaving the
machine like that over night in case someone can tell me.
Kernel version was 3.3.6-3.fc16.x86_64, Ceph cluster is version 0.47.2. The
crash happened after I issued an rbd command. Another thing that might be
related is that I stopped and restarted the entire cluster twice since
mounting the cephfs. The first time, I disabled cephx, the second time I
enabled it again.
Regards,
Guido
next reply other threads:[~2012-05-30 17:35 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 17:35 Guido Winkelmann [this message]
2012-06-08 16:35 ` Kernel crash Tommi Virtanen
-- strict thread matches above, loose matches on Subject: below --
2014-01-16 10:24 Kernel Crash Nieścierowicz Adam
2011-10-06 21:59 kernel crash Pau Espin Pedrol
2011-09-22 18:45 M
2011-09-22 21:24 ` Dave Jones
2011-09-22 21:38 ` David Rientjes
2011-09-22 21:53 ` Dave Jones
2008-01-29 10:32 fenglg
2008-01-29 13:34 ` Patrick McHardy
2008-01-29 17:55 ` Jan Engelhardt
2008-01-29 17:59 ` Patrick McHardy
2007-12-30 18:25 Jerry Geis
2006-02-11 5:37 Kernel Crash Jayaprakash Shanmugam
2005-01-19 12:54 Kernel crash Ian Pratt
2005-01-19 14:04 ` Tobias Hunger
2005-01-19 15:12 ` Keir Fraser
2005-01-19 16:54 ` Derrik Pates
2005-01-19 21:05 ` Tobias Hunger
2005-01-20 8:56 ` Keir Fraser
2005-01-20 10:00 ` Tobias Hunger
2005-01-20 11:30 ` Keir Fraser
2005-01-20 22:55 ` Tobias Hunger
2005-01-19 17:46 ` Philip R Auld
2005-01-19 1:31 Ian Pratt
2005-01-19 10:52 ` Tobias Hunger
2005-01-18 21:50 Tobias Hunger
2004-09-05 18:51 Giuliano Pochini
2004-09-06 15:16 ` Takashi Iwai
2004-09-07 7:55 ` Giuliano Pochini
2003-05-29 20:41 kernel crash Gordon Messmer
2003-05-29 21:20 ` John M Flinchbaugh
2003-05-29 22:36 ` Martin Josefsson
2003-05-30 4:23 ` Gordon Messmer
2003-05-30 10:53 ` Martin Josefsson
2003-05-30 10:18 ` Eicke Friedrich
2002-06-26 11:02 Pavel Gulchouck
2002-06-26 19:03 ` James Stevenson
2002-06-27 8:00 ` Pavel Gulchouck
2001-04-12 15:16 Cyrille Ngalle
2001-04-12 15:31 ` Russell King
2001-04-13 13:16 ` nak
2001-04-02 16:40 Wayne.Brown
2001-04-01 10:15 nak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1934548.axdquzlaJh@pc10 \
--to=guido-ceph@thisisnotatest.de \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.