From: Bas van der Vlies <basv@sara.nl>
To: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: NFSD crashes with oops
Date: Wed, 08 Mar 2006 16:23:16 +0100 [thread overview]
Message-ID: <440EF6E4.4080109@sara.nl> (raw)
In-Reply-To: <1141830321.8214.21.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> On Wed, 2006-03-08 at 15:08 +0100, Bas van der Vlies wrote:
>> Bas van der Vlies wrote:
>>> At our side we have an 4 node GFS cluster. The nodes act as an
>>> NFS-server to +/- 640 nodes.
>>>
>> Just upgraded to 2.6.16-rc5 and still nfsd crashes. With more debug
>> output. So some code is fixed in this release. Nfsd crashes instead
>> of 128 we now have 127, nfsd still runing now.
>>
>> == Crash Output ==
>> Unable to handle kernel NULL pointer dereference at virtual address 00000038
>> printing eip:
>> f89a4be3
>> *pde = 37809001
>> *pte = 00000000
>> Oops: 0000 [#1]
>> SMP
>> Modules linked in: lock_dlm dlm cman dm_round_robin dm_multipath sg
>> ide_floppy ide_cd cdrom qla2xxx siimage piix e1000 gfs lock_harness dm_mod
>> CPU: 0
>> EIP: 0060:[<f89a4be3>] Tainted: GF VLI
>> EFLAGS: 00010246 (2.6.16-rc5-sara3 #1)
>> EIP is at gfs_create+0x6f/0x153 [gfs]
>
> This is Oopsing in the GFS code, not nfsd.
>
Thanks for the info. Just for my knowledge. The nfsd crashes because
there is an error in the gfs_create code?
The problem is that gfs-filesystems are still accesible and if we are
lucky we have on thread less else the load on the gfs-fileserver is sky
high and it does not respond to the nfs-requests anymore. So all nfsd
processes are locked.
Regards
--
--
********************************************************************
* *
* Bas van der Vlies e-mail: basv@sara.nl *
* SARA - Academic Computing Services phone: +31 20 592 8012 *
* Kruislaan 415 fax: +31 20 6683167 *
* 1098 SJ Amsterdam *
* *
********************************************************************
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-03-08 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 8:00 NFSD crashes with oops Bas van der Vlies
2006-03-08 14:08 ` Bas van der Vlies
2006-03-08 15:01 ` Bas van der Vlies
2006-03-08 15:05 ` Trond Myklebust
2006-03-08 15:23 ` Bas van der Vlies [this message]
2006-03-08 15:36 ` Trond Myklebust
2006-03-09 7:39 ` NFSD/gfs " Bas van der Vlies
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=440EF6E4.4080109@sara.nl \
--to=basv@sara.nl \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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