[Cluster-devel] Kernel panic on mounting gfs2: kernel 2.6.19 and 2.6.20.
Zbyszek Żółkiewski
zbyszek at toliman.pl
Thu Feb 8 13:04:11 UTC 2007
sorry - mail went only to Steven, now to group....
On 2/8/07, Zbyszek Żółkiewski <zbyszek at toliman.pl> wrote:
>
> well, thanks for answer, i have tried with nolock, and result is as
> follow:
> of course i made mkfs -t gfs2 -p lock_nolock -t xmpp-alt2:test -j 1
> /dev/sdb1 and then:
> mount -t gfs2 /dev/sdb1 /mnt -v
>
> and yes - the device is mounted,
> (the changes to kernel you was talking about: you mean: git1 for 2.6.20?)
>
>
> Feb 8 13:52:46 xmpp-alt2 kernel: Lock_Nolock (built Feb 8 2007 13:52:20)
> installed
> Feb 8 13:58:13 xmpp-alt2 kernel: GFS2: fsid=: Trying to join cluster
> "lock_nolock", "xmpp-alt2:test"
> Feb 8 13:58:13 xmpp-alt2 kernel: GFS2: fsid=xmpp-alt2:test.0: Joined
> cluster. Now mounting FS...
> Feb 8 13:58:13 xmpp-alt2 kernel: GFS2: fsid=xmpp-alt2:test.0: jid=0,
> already locked for use
> Feb 8 13:58:13 xmpp-alt2 kernel: GFS2: fsid=xmpp-alt2: test.0: jid=0:
> Looking at journal...
> Feb 8 13:58:13 xmpp-alt2 kernel: GFS2: fsid=xmpp-alt2:test.0: jid=0: Done
> Feb 8 13:58:13 xmpp-alt2 kernel: ------------[ cut here ]------------
> Feb 8 13:58:13 xmpp-alt2 kernel: kernel BUG at fs/gfs2/glock.c:738!
> Feb 8 13:58:13 xmpp-alt2 kernel: invalid opcode: 0000 [#1]
> Feb 8 13:58:13 xmpp-alt2 kernel: Modules linked in: lock_nolock lock_dlm
> gfs2 dlm configfs
> Feb 8 13:58:13 xmpp-alt2 kernel: CPU: 0
> Feb 8 13:58:13 xmpp-alt2 kernel: EIP: 0060:[<f895011e>] Not tainted
> VLI
> Feb 8 13:58:13 xmpp-alt2 kernel: EFLAGS: 00000282 (2.6.20-xmpp2 #1)
> Feb 8 13:58:13 xmpp-alt2 kernel: EIP is at gfs2_glmutex_unlock+0x18/0x1c
> [gfs2]
> Feb 8 13:58:13 xmpp-alt2 kernel: eax: f5085bbc ebx: f5085bec ecx:
> f5875000 edx: f5085bbc
> Feb 8 13:58:13 xmpp-alt2 kernel: esi: f5085b78 edi: f575ff88 ebp:
> f575ff94 esp: f575ff64
> Feb 8 13:58:13 xmpp-alt2 kernel: ds: 007b es: 007b ss: 0068
> Feb 8 13:58:13 xmpp-alt2 kernel: Process gfs2_glockd (pid: 2645,
> ti=f575e000 task=f58d3550 task.ti=f575e000)
> Feb 8 13:58:13 xmpp-alt2 kernel: Stack: f89518e5 f5875000 f5875364
> f8948861 00000000 f58d3550 c0123580 f575ffa0
> Feb 8 13:58:13 xmpp-alt2 kernel: f575ffa0 f575ffac c010f84f
> 00000000 00000000 f58d3550 c0123580 f575ffa0
> Feb 8 13:58:13 xmpp-alt2 kernel: f575ffa0 000004f8 b716dc5d
> 0024d983 f5011dc4 f5875000 f8948830 fffffffc
> Feb 8 13:58:13 xmpp-alt2 kernel: Call Trace:
> Feb 8 13:58:13 xmpp-alt2 kernel: [<f89518e5>]
> gfs2_reclaim_glock+0x8d/0x8f [gfs2]
> Feb 8 13:58:13 xmpp-alt2 kernel: [<f8948861>] gfs2_glockd+0x31/0xe4
> [gfs2]
> Feb 8 13:58:13 xmpp-alt2 kernel: [<c0123580>]
> autoremove_wake_function+0x0/0x43
> Feb 8 13:58:13 xmpp-alt2 kernel: [<c010f84f>] __wake_up_common+0x33/0x56
>
> Feb 8 13:58:13 xmpp-alt2 kernel: [<c0123580>]
> autoremove_wake_function+0x0/0x43
> Feb 8 13:58:13 xmpp-alt2 kernel: [<f8948830>] gfs2_glockd+0x0/0xe4
> [gfs2]
> Feb 8 13:58:13 xmpp-alt2 kernel: [<c012320b>] kthread+0x9d/0xce
> Feb 8 13:58:13 xmpp-alt2 kernel: [<c012316e>] kthread+0x0/0xce
> Feb 8 13:58:13 xmpp-alt2 kernel: [<c01034df>]
> kernel_thread_helper+0x7/0x10
> Feb 8 13:58:13 xmpp-alt2 kernel: =======================
> Feb 8 13:58:13 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:58:13 xmpp-alt2 kernel: EIP: [<f895011e>]
> gfs2_glmutex_unlock+0x18/0x1c [gfs2] SS:ESP 0068:f575ff64
> Feb 8 13:58:28 xmpp-alt2 kernel: <0>------------[ cut here ]------------
> Feb 8 13:58:28 xmpp-alt2 kernel: kernel BUG at fs/gfs2/glock.c:738!
> Feb 8 13:58:28 xmpp-alt2 kernel: invalid opcode: 0000 [#2]
> Feb 8 13:58:28 xmpp-alt2 kernel: Modules linked in: lock_nolock lock_dlm
> gfs2 dlm configfs
> Feb 8 13:58:28 xmpp-alt2 kernel: CPU: 0
> Feb 8 13:58:28 xmpp-alt2 kernel: EIP: 0060:[<f895011e>] Not tainted
> VLI
> Feb 8 13:58:28 xmpp-alt2 kernel: EFLAGS: 00000282 (2.6.20-xmpp2 #1)
> Feb 8 13:58:28 xmpp-alt2 kernel: EIP is at gfs2_glmutex_unlock+0x18/0x1c
> [gfs2]
> Feb 8 13:58:28 xmpp-alt2 kernel: eax: f5085bbc ebx: f5085b78 ecx:
> f5875000 edx: f5085bbc
> Feb 8 13:58:28 xmpp-alt2 kernel: esi: f5875000 edi: f5085b78 ebp:
> 00000001 esp: f577df98
> Feb 8 13:58:28 xmpp-alt2 kernel: ds: 007b es: 007b ss: 0068
> Feb 8 13:58:28 xmpp-alt2 kernel: Process gfs2_scand (pid: 2644,
> ti=f577c000 task=f58d3a70 task.ti=f577c000)
> Feb 8 13:58:28 xmpp-alt2 kernel: Stack: f8951940 f8951942 000001e0
> f5875000 f8948800 fffffffc f89519aa f5875000
> Feb 8 13:58:28 xmpp-alt2 kernel: f5875000 f894880c f5011dc4
> c012320b 00000001 ffffffff ffffffff c012316e
> Feb 8 13:58:28 xmpp-alt2 kernel: 00000000 00000000 00000000
> c01034df f5011dbc 00000000 00000000 00000000
> Feb 8 13:58:28 xmpp-alt2 kernel: Call Trace:
> Feb 8 13:58:28 xmpp-alt2 kernel: [<f8951940>] examine_bucket+0x59/0x5b
> [gfs2]
> Feb 8 13:58:28 xmpp-alt2 kernel: [<f8951942>] scan_glock+0x0/0x51 [gfs2]
> Feb 8 13:58:28 xmpp-alt2 kernel: [<f8948800>] gfs2_scand+0x0/0x30 [gfs2]
> Feb 8 13:58:28 xmpp-alt2 kernel: [<f89519aa>]
> gfs2_scand_internal+0x17/0x22 [gfs2]
> Feb 8 13:58:28 xmpp-alt2 kernel: [<f894880c>] gfs2_scand+0xc/0x30 [gfs2]
> Feb 8 13:58:28 xmpp-alt2 kernel: [<c012320b>] kthread+0x9d/0xce
> Feb 8 13:58:28 xmpp-alt2 kernel: [<c012316e>] kthread+0x0/0xce
> Feb 8 13:58:28 xmpp-alt2 kernel: [<c01034df>]
> kernel_thread_helper+0x7/0x10
> Feb 8 13:58:28 xmpp-alt2 kernel: =======================
> Feb 8 13:58:28 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:58:28 xmpp-alt2 kernel: EIP: [<f895011e>]
> gfs2_glmutex_unlock+0x18/0x1c [gfs2] SS:ESP 0068:f577df98
>
>
>
>
>
> On 2/8/07, Steven Whitehouse <swhiteho at redhat.com> wrote:
> >
> > Hi,
> >
> > On Thu, 2007-02-08 at 13:15 +0100, Zbyszek Żółkiewski wrote:
> > > 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?
> > >
> > It looks like the mount was successful, but that the problem occurred
> > right after mount. Just as a sanity check does the same thing happen if
> > you use lock_nolock?
> >
> > There have been a number of bug fixes since 2.6.20 which went into
> > Linus' kernel yesterday, so you might want to try the latest upstream
> > kernel, but I don't recognise this problem as being something we've seen
> > before,
> >
> > Steve.
> >
> >
>
> --
> pozdrawiam,
> Zbyszek Żółkiewski
--
pozdrawiam,
Zbyszek Żółkiewski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070208/84892e46/attachment.htm>
More information about the Cluster-devel
mailing list