[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [Linux-cluster] GFS crashing on 2.6.18.6



People,

This problem does not occure with kernel 2.6.17.14

> 
> People,
> 
> We have build the stable GFS tree againt 2.6.18.6. After we executed
> ccs,cman, fenced and clvmd we tried to mount the GFS filesystems, with
> the following result:
> 
> 
> CMAN: Waiting to join or form a Linux-cluster
> CMAN: sending membership request
> CMAN: got node ifs4
> CMAN: got node ifs3
> CMAN: got node ifs2
> CMAN: got node ifs1
> CMAN: quorum regained, resuming activity
> GFS: Trying to join cluster "lock_dlm", "lisa:lisa_vg1_local"
> GFS: fsid=lisa:lisa_vg1_local.1: Joined cluster. Now mounting FS...
> GFS: fsid=lisa:lisa_vg1_local.1: jid=1: Trying to acquire journal
> lock...
> GFS: fsid=lisa:lisa_vg1_local.1: jid=1: Looking at journal...
> GFS: fsid=lisa:lisa_vg1_local.1: jid=1: Done
> GFS: fsid=lisa:lisa_vg1_local.1: Scanning for log elements...
> GFS: fsid=lisa:lisa_vg1_local.1: Found 0 unlinked inodes
> GFS: fsid=lisa:lisa_vg1_local.1: Found quota changes for 0 IDs
> GFS: fsid=lisa:lisa_vg1_local.1: Done
> BUG: unable to handle kernel NULL pointer dereference at 
> virtual address
> 0000001
> 8
>  printing eip:
> c0164efc
> *pde = 36d55001
> *pte = 00000000
> Oops: 0000 [#1]
> SMP
> Modules linked in: lock_dlm dlm dm_round_robin dm_multipath sg
> ide_floppy ide_cd
>  cdrom qla2xxx firmware_class scsi_transport_fc siimage piix e1000 gfs
> lock_harn
> ess cman dm_mod
> CPU:    0
> EIP:    0060:[<c0164efc>]    Tainted: GF     VLI
> EFLAGS: 00010293   (2.6.18.6-sara1 #1)
> EIP is at do_add_mount+0x66/0xeb
> eax: 0000000c   ebx: f79e5200   ecx: 00000000   edx: c5900cc0
> esi: f6cfbf34   edi: ffffffea   ebp: f6cfbef4   esp: f6cfbee4
> ds: 007b   es: 007b   ss: 0068
> Process mount (pid: 6360, ti=f6cfa000 task=f6d96ab0 task.ti=f6cfa000)
> Stack: 00000000 f6d0e000 f6d2b000 f6d0e003 f6cfbf10 c0164e8a 00000000
> f6cfbf34
>        00000000 00000000 f6cfbf34 f6cfbf90 c016546d 00000000 f73d6000
> f6d2b000
>        00000000 f6d0e000 f6d73000 f73d6000 f7816894 c5900cc0 000000d0
> 0805b5f0
> Call Trace:
>  [<c0103560>] show_stack_log_lvl+0x8f/0x97
>  [<c01036d0>] show_registers+0x125/0x18e
>  [<c01038c3>] die+0x116/0x1c8
>  [<c010e7bf>] do_page_fault+0x4a3/0x57b
>  [<c0103245>] error_code+0x39/0x40
>  [<c0164e8a>] do_new_mount+0x67/0x73
>  [<c016546d>] do_mount+0x162/0x179
>  [<c01656fe>] sys_mount+0x6a/0xa6
>  [<c010279f>] syscall_call+0x7/0xb
> Code: ff ff 8b 00 8b 80 48 04 00 00 39 42 64 75 7d 8b 43 14 
> bf f0 ff ff
> ff 39 42 14 75 07 8b 06 39 42 10 74 69 8b 43 10 bf ea ff ff ff <8b> 40
> 0c 0f b7 40 28 25 00 f0 00 00 3d 00 a0 00 00 74 4e 8b 45
> EIP: [<c0164efc>] do_add_mount+0x66/0xeb SS:ESP 0068:f6cfbee4
> 
> 
> Does anyone have a clue what happend here?
> 
> 
> Met vriendelijke groet, Kind Regards,
> 
> Jaap P. Dijkshoorn
> Group Leader Cluster Computing
> Systems Programmer
> mailto:jaap sara nl    http://home.sara.nl/~jaapd
> 
> SARA Computing & Networking Services
> Kruislaan 415     1098 SJ  Amsterdam
> Tel: +31-(0)20-5923000
> Fax: +31-(0)20-6683167
> http://www.sara.nl
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]