cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2] Git tree update
Date: Mon, 12 Nov 2007 12:48:52 +0100	[thread overview]
Message-ID: <47383DA4.2050405@ubuntu.com> (raw)
In-Reply-To: <473348F4.1040208@ubuntu.com>

Fabio Massimo Di Nitto wrote:
> Hi Steven,
> 
> a quick update on this issue. I am still looking into it.
> 
> I was able to reproduce the problem in .22/.23/.24 vanilla but NOT on .22 ubuntu
> kernel that has a .22 + a pull from at the time -22-nwm.
> 
> I start to strongly believe that the problem is caused by either a gcc bug OR my
> kernel config.

I can confirm this is a kernel config issue.

I just booted 2.6.24-rc2 and here are the results:

http://people.ubuntu.com/~fabbione/oops/

bad.config will OOPS on mount with the same OOPS as posted before.
good.config will mount and operate fine. We get an OOPS on umount on 2/3 of the
nodes.

dmesg.node* have the umount OOPS.

If you have any suggestion on what kernel options might cause the mount failure,
I will dedicate time to test them one at a time.

Cheers
Fabio

-- 
I'm going to make him an offer he can't refuse.



  reply	other threads:[~2007-11-12 11:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29  8:29 [Cluster-devel] [GFS2] Git tree update Steven Whitehouse
2007-10-29 10:25 ` Fabio Massimo Di Nitto
2007-10-31 15:34   ` Steven Whitehouse
2007-11-01  7:30     ` Fabio Massimo Di Nitto
2007-11-08 17:35     ` Fabio Massimo Di Nitto
2007-11-12 11:48       ` Fabio Massimo Di Nitto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-28  8:42 [Cluster-devel] GFS2: " Steven Whitehouse
2007-09-25  8:55 [Cluster-devel] GFS2 git " Steven Whitehouse
2007-08-06  7:37 Steven Whitehouse
2007-04-06  9:19 [Cluster-devel] [GFS2] Git " Steven Whitehouse

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=47383DA4.2050405@ubuntu.com \
    --to=fabbione@ubuntu.com \
    /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).