[Linux-cluster] GFS2: kernel oops on mount with lock_nolock
Cyril
cbay at excellency.fr
Tue Jan 2 10:47:38 UTC 2007
Hello,
First of all, happy new year to everyone :-)
I compiled a 2.6.19.1 kernel with GFS2 and lock_nolock. When trying to mount the newly created GFS2 partition, I get 2 successive identical kernel oops (see [1], at the end of this mail). The second oops appears about 15 seconds after the first one.
Nevertheless, the FS is mounted and I can make basic file operations on it. However, extracting kernel sources triggers another oops and tar exits with a segmentation fault:
dbx5:/mnt# tar xjvf /root/linux-2.6.19.tar.bz2
[...]
linux-2.6.19/include/asm-h8300/shmbuf.h
Segmentation fault
See the oops in [2]. Now the FS seems stuck, and trying to remove a file hangs forever.
These errors happen on a freshly installed Debian stable with my custom kernel. I get the same oops with a 2.6.20-rc2 kernel.
Steps to reproduce:
- install Debian stable
- install the kernel compiled with my .config (can be found on http://dev.excellency.fr/cbay/config)
- install mkfs.gfs2 (from latest cluster CVS, compiled myself) and libvolume_id.so (from udev 0.94, compiled myself)
- # mkfs -t gfs2 -p lock_nolock -t test:test /dev/sda3
- # mount -t gfs2 /dev/sda3 /mnt/
/dev/sda3 is 10GB.
Any idea?
Thanks!
[1] :
GFS2: fsid=: Trying to join cluster "lock_nolock", "test:test"
GFS2: fsid=test:test.0: Joined cluster. Now mounting FS...
GFS2: fsid=test:test.0: jid=0, already locked for use
GFS2: fsid=test:test.0: jid=0: Looking at journal...
GFS2: fsid=test:test.0: jid=0: Done
------------[ cut here ]------------
kernel BUG at fs/gfs2/glock.c:738!
invalid opcode: 0000 [#1]
Modules linked in:
CPU: 0
EIP: 0060:[<c023d206>] Not tainted VLI
EFLAGS: 00010286 (2.6.19.1 #1)
EIP is at gfs2_glmutex_unlock+0x26/0x30
eax: f788dbbc ebx: f788dbec ecx: 00000001 edx: f788dbbc
esi: f788db78 edi: f5022388 ebp: f5415f94 esp: f5415f48
ds: 007b es: 007b ss: 0068
Process gfs2_glockd (pid: 1892, ti=f5414000 task=f7e6e030 task.ti=f5414000)
Stack: f788db78 c023ee95 f788db78 00000283 f5022000 f5415f88 c0234a28 f5022000
00000000 f7e6e030 c012d760 f5415f94 f5415f94 c052b7a0 00000000 00000000
00000000 f7e6e030 c012d760 f5415f94 f5415f94 f7014fe8 000000cc c1bc8550
Call Trace:
[<c023ee95>] gfs2_reclaim_glock+0x85/0xb0
[<c0234a28>] gfs2_glockd+0xe8/0x110
[<c012d760>] autoremove_wake_function+0x0/0x60
[<c012d760>] autoremove_wake_function+0x0/0x60
[<c0234940>] gfs2_glockd+0x0/0x110
[<c012d3a7>] kthread+0xb7/0xc0
[<c012d2f0>] kthread+0x0/0xc0
[<c0103f17>] kernel_thread_helper+0x7/0x10
=======================
Code: bf 00 00 00 00 83 ec 04 b8 01 00 00 00 8b 54 24 08 0f b3 42 08 c7 42 24 00 00 00 00 c7 42 28 00 00 00 00 89 14 24 e8 2a fe ff ff <0f> 0b e2 02 81 d4 3b c0 58 c3 55 57 56 31 f6 53 83 ec 10 8b 7c
EIP: [<c023d206>] gfs2_glmutex_unlock+0x26/0x30 SS:ESP 0068:f5415f48
<0>------------[ cut here ]------------
kernel BUG at fs/gfs2/glock.c:738!
invalid opcode: 0000 [#2]
Modules linked in:
CPU: 0
EIP: 0060:[<c023d206>] Not tainted VLI
EFLAGS: 00010286 (2.6.19.1 #1)
EIP is at gfs2_glmutex_unlock+0x26/0x30
eax: f5757e2c ebx: f5757de8 ecx: 00000001 edx: f5757e2c
esi: f5757de8 edi: f5022000 ebp: 00000001 esp: f55b3f78
ds: 007b es: 007b ss: 0068
Process gfs2_scand (pid: 1891, ti=f55b2000 task=c19a8030 task.ti=f55b2000)
Stack: f5757de8 c023ef23 f5757de8 0000090e f5022000 c0234900 fffffffc c023efc5
c023ef30 f5022000 0000090d f5022000 f5022000 c0234921 f5022000 f7813d7c
c012d3a7 f5022000 f55b3fcc 00000000 00000001 ffffffff ffffffff c012d2f0
Call Trace:
[<c023ef23>] examine_bucket+0x63/0x70
[<c0234900>] gfs2_scand+0x0/0x40
[<c023efc5>] gfs2_scand_internal+0x25/0x40
[<c023ef30>] scan_glock+0x0/0x70
[<c0234921>] gfs2_scand+0x21/0x40
[<c012d3a7>] kthread+0xb7/0xc0
[<c012d2f0>] kthread+0x0/0xc0
[<c0103f17>] kernel_thread_helper+0x7/0x10
=======================
Code: bf 00 00 00 00 83 ec 04 b8 01 00 00 00 8b 54 24 08 0f b3 42 08 c7 42 24 00 00 00 00 c7 42 28 00 00 00 00 89 14 24 e8 2a fe ff ff <0f> 0b e2 02 81 d4 3b c0 58 c3 55 57 56 31 f6 53 83 ec 10 8b 7c
EIP: [<c023d206>] gfs2_glmutex_unlock+0x26/0x30 SS:ESP 0068:f55b3f78
[2] :
<0>------------[ cut here ]------------
kernel BUG at fs/gfs2/log.c:74!
invalid opcode: 0000 [#3]
Modules linked in:
CPU: 0
EIP: 0060:[<c02430cb>] Not tainted VLI
EFLAGS: 00010292 (2.6.19.1-alwaysdata #1)
EIP is at gfs2_ail1_start_one+0xb/0x150
eax: f5532380 ebx: f5022000 ecx: f5022000 edx: 00000000
esi: f5532380 edi: 00000000 ebp: f502269c esp: f70cfcc4
ds: 007b es: 007b ss: 0068
Process tar (pid: 2032, ti=f70ce000 task=f7e6e030 task.ti=f70ce000)
Stack: 000001f6 000001f7 f502263c 00000000 f70cfcd4 f70cfcd4 00000004 f5022000
00000000 00000000 f502269c c0243378 f5022000 f5532380 f5022000 00000000
f5532380 f502267c f5022000 00000002 00000125 f5022658 c0243732 f5022000
Call Trace:
[<c0243378>] gfs2_ail1_start+0x68/0x120
[<c0243732>] gfs2_log_reserve+0x92/0x110
[<c023e0ea>] gfs2_glock_nq+0x4a/0xa0
[<c025986f>] gfs2_trans_begin+0xff/0x160
[<c0241a31>] link_dinode+0xe1/0x230
[<c0241df8>] gfs2_createi+0x268/0x300
[<c024d0c6>] gfs2_create+0x66/0x130
[<c0241c01>] gfs2_createi+0x71/0x300
[<c023e508>] gfs2_glock_nq_num+0x78/0xa0
[<c024d060>] gfs2_create+0x0/0x130
[<c016b4c9>] vfs_create+0xa9/0x190
[<c016b8a0>] open_namei_create+0x60/0xb0
[<c016bf3d>] open_namei+0x64d/0x680
[<c01162e0>] default_wake_function+0x0/0x20
[<c01615f0>] do_filp_open+0x40/0x60
[<c01617f6>] get_unused_fd+0x66/0xc0
[<c0161937>] do_sys_open+0x57/0xf0
[<c01619f7>] sys_open+0x27/0x30
[<c0102e17>] syscall_call+0x7/0xb
=======================
Code: 89 c3 8d 44 08 ff f7 f3 8d 68 01 89 e8 8b 1c 24 8b 74 24 04 8b 7c 24 08 8b 6c 24 0c 83 c4 10 c3 55 57 56 53 83 ec 1c 8b 74 24 34 <0f> 0b 4a 00 29 d8 3b c0 8d 6e 0c 8d 76 00 8d bc 27 00 00 00 00
EIP: [<c02430cb>] gfs2_ail1_start_one+0xb/0x150 SS:ESP 0068:f70cfcc4
--
Cyril B.
excelleNCy
More information about the Linux-cluster
mailing list