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 15:02:00 +0100 [thread overview]
Message-ID: <f7ca4caa0702080602v76c7a4f9x8cf1b208b7b40022@mail.gmail.com> (raw)
In-Reply-To: <1170941171.11001.496.camel@quoit.chygwyn.com>
ok , i have build kernel from your git (
git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-nmw.git)
Linux version 2.6.20-xmpp2-ga2cf8222-dirty (root at xmpp-alt2) (gcc version
3.4.4 20050314 (prerelease) (Debian 3.4.3-13sarge1)) #1 Thu Feb 8 14:51:21
CET 2007
and there is the same problem;
kernel BUG at fs/gfs2/glock.c:704!
invalid opcode: 0000 [#2]
Modules linked in: lock_nolock lock_dlm gfs2 dlm configfs
CPU: 0
EIP: 0060:[<f8950173>] Not tainted VLI
EFLAGS: 00000282 (2.6.20-xmpp2-ga2cf8222-dirty #1)
EIP is at gfs2_glmutex_unlock+0x18/0x1c [gfs2]
and so one....
ok so waiting patiently for solution....
On 2/8/07, Steven Whitehouse <swhiteho@redhat.com> wrote:
>
> Hi,
>
> On Thu, 2007-02-08 at 14:04 +0100, Zbyszek ???kiewski wrote:
> > sorry - mail went only to Steven, now to group....
> >
> >
> > On 2/8/07, Zbyszek ???kiewski <zbyszek@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,
> It looks like what is happening is that a glmutex_unlock() is
> discovering that its spinlock has been dropped by glock.c:run_queue()
> which should be impossible, so something odd is happening here I think.
>
> The daemons implicated in this are there to demote unused locks on a
> periodic basis, so its presumably one of the locks used during mounting
> of the filesystem thats at fault.
>
> > (the changes to kernel you was talking about: you mean: git1
> > for 2.6.20?)
> >
> I'm not sure if its in git1 or not, I suspect it will be git2 since it
> was only yesterday that the patches went in. Linus' current git tree
> seems to be broken (both gitweb and direct via the git tools) otherwise
> I'd post a URL to the changes. In the mean time you can find them in my
> -nmw tree which will get updated just as soon as git it working again at
> kernel.org,
>
> Steve.
>
>
>
--
pozdrawiam,
Zbyszek ???kiewski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070208/748a6f60/attachment.htm>
next prev parent reply other threads:[~2007-02-08 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 12:15 [Cluster-devel] Kernel panic on mounting gfs2: kernel 2.6.19 and 2.6.20 Zbyszek Żółkiewski
2007-02-08 12:57 ` 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 [this message]
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=f7ca4caa0702080602v76c7a4f9x8cf1b208b7b40022@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).