From: Zbyszek Żółkiewski <zbyszek@toliman.pl>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Kernel panic on mounting gfs2: kernel 2.6.19 and 2.6.20.
Date: Thu, 8 Feb 2007 13:15:17 +0100 [thread overview]
Message-ID: <f7ca4caa0702080415occ815ddke218b12efb3f89b4@mail.gmail.com> (raw)
Hi,
I have recently setup cluster on Debian systems and i got issues related
with kernel panic:
systems affected: Debian 4.0 (testing) and Debian 3.1 (r4)
gcc: 3.4 and 4.1.2
kernels: 2.6.19 and 2.6.20
cluster from latest cvs
command invoked: mount -t gfs2 /dev/sdb1 /mnt/
docs that i followed :
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/doc/usage.txt?cvsroot=cluster
any clue?
here are detailed logs:
Feb 8 13:05:18 xmpp-alt2 kernel: dlm: test: add member 1
Feb 8 13:05:18 xmpp-alt2 kernel: dlm: test: total members 1 error 0
Feb 8 13:05:18 xmpp-alt2 kernel: dlm: test: dlm_recover_directory
Feb 8 13:05:18 xmpp-alt2 kernel: dlm: test: dlm_recover_directory 0 entries
Feb 8 13:05:18 xmpp-alt2 kernel: dlm: test: recover 1 done: 0 ms
Feb 8 13:05:18 xmpp-alt2 kernel: GFS2: fsid=xmpp-alt2:test.0: Joined
cluster. Now mounting FS...
Feb 8 13:05:21 xmpp-alt2 kernel: GFS2: fsid=xmpp-alt2:test.0: jid=0,
already locked for use
Feb 8 13:05:21 xmpp-alt2 kernel: GFS2: fsid=xmpp-alt2:test.0: jid=0:
Looking at journal...
Feb 8 13:05:21 xmpp-alt2 kernel: GFS2: fsid=xmpp-alt2:test.0: jid=0: Done
Feb 8 13:05:21 xmpp-alt2 kernel: ------------[ cut here ]------------
Feb 8 13:05:21 xmpp-alt2 kernel: kernel BUG at fs/gfs2/glock.c:738!
Feb 8 13:05:21 xmpp-alt2 kernel: invalid opcode: 0000 [#1]
Feb 8 13:05:21 xmpp-alt2 kernel: Modules linked in: lock_dlm dlm configfs
gfs2
Feb 8 13:05:21 xmpp-alt2 kernel: CPU: 0
Feb 8 13:05:21 xmpp-alt2 kernel: EIP: 0060:[<f890f11e>] Not tainted
VLI
Feb 8 13:05:21 xmpp-alt2 kernel: EFLAGS: 00000282 (2.6.20-xmpp2 #1)
Feb 8 13:05:21 xmpp-alt2 kernel: EIP is at gfs2_glmutex_unlock+0x18/0x1c
[gfs2]
Feb 8 13:05:21 xmpp-alt2 kernel: eax: f3aa1bbc ebx: f3aa1bec ecx:
00007080 edx: f3aa1bbc
Feb 8 13:05:22 xmpp-alt2 kernel: esi: f3aa1b78 edi: f15a3f88 ebp:
f15a3f94 esp: f15a3f64
Feb 8 13:05:22 xmpp-alt2 kernel: ds: 007b es: 007b ss: 0068
Feb 8 13:05:22 xmpp-alt2 kernel: Process gfs2_glockd (pid: 7013,
ti=f15a2000 task=f3ad9a70 task.ti=f15a2000)
Feb 8 13:05:22 xmpp-alt2 kernel: Stack: f89108e5 f34f6000 f34f6364 f8907861
00000000 f3ad9a70 c0123580 f15a3fa0
Feb 8 13:05:22 xmpp-alt2 kernel: f15a3fa0 f15a3fac c010f84f 00000000
00000000 f3ad9a70 c0123580 f15a3fa0
Feb 8 13:05:22 xmpp-alt2 kernel: f15a3fa0 000004c1 f9a6da64 0024d65b
f348ddc4 f34f6000 f8907830 fffffffc
Feb 8 13:05:22 xmpp-alt2 kernel: Call Trace:
Feb 8 13:05:22 xmpp-alt2 kernel: [<f89108e5>] gfs2_reclaim_glock+0x8d/0x8f
[gfs2]
Feb 8 13:05:22 xmpp-alt2 kernel: [<f8907861>] gfs2_glockd+0x31/0xe4 [gfs2]
Feb 8 13:05:22 xmpp-alt2 kernel: [<c0123580>]
autoremove_wake_function+0x0/0x43
Feb 8 13:05:22 xmpp-alt2 kernel: [<c010f84f>] __wake_up_common+0x33/0x56
Feb 8 13:05:22 xmpp-alt2 kernel: [<c0123580>]
autoremove_wake_function+0x0/0x43
Feb 8 13:05:22 xmpp-alt2 kernel: [<f8907830>] gfs2_glockd+0x0/0xe4 [gfs2]
Feb 8 13:05:22 xmpp-alt2 kernel: [<c012320b>] kthread+0x9d/0xce
Feb 8 13:05:22 xmpp-alt2 kernel: [<c012316e>] kthread+0x0/0xce
Feb 8 13:05:22 xmpp-alt2 kernel: [<c01034df>]
kernel_thread_helper+0x7/0x10
Feb 8 13:05:22 xmpp-alt2 kernel: =======================
Feb 8 13:05:22 xmpp-alt2 kernel: Code: c3 65 a1 08 00 00 00 89 42 24 8b 04
24 89 42 28 89 c8 c3 0f ba 70 08 01 c7 40 24 00 00 00 00 c7 40 28 00 00 00
00 e8 7a fe ff ff <0f> 0b eb fe 55 89 d5 57 89 c7 56 31 f6 53 8d 58 3c 83 ec
04 8b
Feb 8 13:05:22 xmpp-alt2 kernel: EIP: [<f890f11e>]
gfs2_glmutex_unlock+0x18/0x1c [gfs2] SS:ESP 0068:f15a3f64
Feb 8 13:05:33 xmpp-alt2 kernel: <0>------------[ cut here ]------------
Feb 8 13:05:33 xmpp-alt2 kernel: kernel BUG at fs/gfs2/glock.c:738!
Feb 8 13:05:33 xmpp-alt2 kernel: invalid opcode: 0000 [#2]
Feb 8 13:05:33 xmpp-alt2 kernel: Modules linked in: lock_dlm dlm configfs
gfs2
Feb 8 13:05:33 xmpp-alt2 kernel: CPU: 0
Feb 8 13:05:33 xmpp-alt2 kernel: EIP: 0060:[<f890f11e>] Not tainted
VLI
Feb 8 13:05:33 xmpp-alt2 kernel: EFLAGS: 00000282 (2.6.20-xmpp2 #1)
Feb 8 13:05:34 xmpp-alt2 kernel: EIP is at gfs2_glmutex_unlock+0x18/0x1c
[gfs2]
Feb 8 13:05:34 xmpp-alt2 kernel: eax: f3aa1bbc ebx: f3aa1b78 ecx:
00007080 edx: f3aa1bbc
Feb 8 13:05:34 xmpp-alt2 kernel: esi: f34f6000 edi: f3aa1b78 ebp:
00000001 esp: f34f5f98
Feb 8 13:05:34 xmpp-alt2 kernel: ds: 007b es: 007b ss: 0068
Feb 8 13:05:34 xmpp-alt2 kernel: Process gfs2_scand (pid: 7012, ti=f34f4000
task=f3bef030 task.ti=f34f4000)
Feb 8 13:05:34 xmpp-alt2 kernel: Stack: f8910940 f8910942 000002be f34f6000
f8907800 fffffffc f89109aa f34f6000
Feb 8 13:05:34 xmpp-alt2 kernel: f34f6000 f890780c f348ddc4 c012320b
00000001 ffffffff ffffffff c012316e
Feb 8 13:05:34 xmpp-alt2 kernel: 00000000 00000000 00000000 c01034df
f348ddbc 00000000 00000000 00000000
Feb 8 13:05:34 xmpp-alt2 kernel: Call Trace:
Feb 8 13:05:34 xmpp-alt2 kernel: [<f8910940>] examine_bucket+0x59/0x5b
[gfs2]
Feb 8 13:05:34 xmpp-alt2 kernel: [<f8910942>] scan_glock+0x0/0x51 [gfs2]
Feb 8 13:05:34 xmpp-alt2 kernel: [<f8907800>] gfs2_scand+0x0/0x30 [gfs2]
Feb 8 13:05:34 xmpp-alt2 kernel: [<f89109aa>]
gfs2_scand_internal+0x17/0x22 [gfs2]
Feb 8 13:05:34 xmpp-alt2 kernel: [<f890780c>] gfs2_scand+0xc/0x30 [gfs2]
Feb 8 13:05:34 xmpp-alt2 kernel: [<c012320b>] kthread+0x9d/0xce
Feb 8 13:05:34 xmpp-alt2 kernel: [<c012316e>] kthread+0x0/0xce
Feb 8 13:05:34 xmpp-alt2 kernel: [<c01034df>]
kernel_thread_helper+0x7/0x10
Feb 8 13:05:34 xmpp-alt2 kernel: =======================
Feb 8 13:05:34 xmpp-alt2 kernel: Code: c3 65 a1 08 00 00 00 89 42 24 8b 04
24 89 42 28 89 c8 c3 0f ba 70 08 01 c7 40 24 00 00 00 00 c7 40 28 00 00 00
00 e8 7a fe ff ff <0f> 0b eb fe 55 89 d5 57 89 c7 56 31 f6 53 8d 58 3c 83 ec
04 8b
Feb 8 13:05:34 xmpp-alt2 kernel: EIP: [<f890f11e>]
gfs2_glmutex_unlock+0x18/0x1c [gfs2] SS:ESP 0068:f34f5f98
--
pozdrawiam,
Zbyszek ???kiewski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070208/9fb2115b/attachment.htm>
next reply other threads:[~2007-02-08 12:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 12:15 Zbyszek Żółkiewski [this message]
2007-02-08 12:57 ` [Cluster-devel] Kernel panic on mounting gfs2: kernel 2.6.19 and 2.6.20 Steven Whitehouse
[not found] ` <f7ca4caa0702080502m723d4bc3r3dbdb9302a942bff@mail.gmail.com>
2007-02-08 13:04 ` Zbyszek Żółkiewski
2007-02-08 13:26 ` Steven Whitehouse
2007-02-08 14:02 ` Zbyszek Żółkiewski
2007-02-08 16:26 ` Steven Whitehouse
2007-02-08 17:21 ` Zbyszek Żółkiewski
2007-02-09 10:32 ` Steven Whitehouse
2007-02-09 10:34 ` Zbyszek Żółkiewski
2007-02-09 11:41 ` Steven Whitehouse
2007-02-09 12:01 ` Zbyszek Żółkiewski
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=f7ca4caa0702080415occ815ddke218b12efb3f89b4@mail.gmail.com \
--to=zbyszek@toliman.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).