public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Claudio Martins <ctpm@rnl.ist.utl.pt>
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	Jan Kara <jack@suse.cz>, Nohez <nohez@cmie.com>
Subject: Re: OCFS2 Filesystem inconsistency across nodes
Date: Tue, 14 Feb 2006 12:19:46 -0800	[thread overview]
Message-ID: <20060214201946.GD20175@ca-server1.us.oracle.com> (raw)
In-Reply-To: <200602140616.11856.ctpm@rnl.ist.utl.pt>

On Tue, Feb 14, 2006 at 06:16:11AM +0000, Claudio Martins wrote:
>  This patch does indeed seem to fix this particular problem. Now creating and 
> deleting files/directories gives expected results across nodes.
Great!

>  The bad news is that it didn't last long. While doing some more tests I found 
> another problem, but judging from kernel messages I think this one is related 
> to the DLM code.
Not so great :/

We have some dlm fixes in our git tree which haven't made their way to Linus
yet (I wanted to run a few more tests). Would you be interested in patching
with them so we can see which bugs are left? The easiest way to get this is
to pull them out of 2.6.16-rc3-mm1:

http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc3/2.6.16-rc3-mm1/broken-out/git-ocfs2.patch

You'll also pull a performance fix in that patch. Of course, even easier
might be to just run 2.6.16-rc3-mm1 for now as it also contains the
checkpoint list split backout.

>  On node 0, tar exited with:
> tar: 
> build-AMD-linux-2.6.16-rc2-git3-jbdfix1/drivers/media/video/cx25840/cx25840-core.c: 
> Cannot stat: Invalid argument
> 
> On node 2, tar exited with a segmentation fault.
Could you load up debugfs.ocfs2 against your file system and run the
following command:

debugfs: locate <M0000000000000000d4a94b05ae097f>

It will tell me the path to the file which that metadata lock refers to.
The path may help us figure out what sort of access we're having problems on
here.
	--Mark

--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com

  reply	other threads:[~2006-02-14 20:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10  5:36 OCFS2 Filesystem inconsistency across nodes Claudio Martins
2006-02-10  6:46 ` Mark Fasheh
2006-02-10  7:20   ` Claudio Martins
2006-02-11  5:40   ` Claudio Martins
2006-02-13 22:26     ` Mark Fasheh
2006-02-14  0:00       ` Claudio Martins
2006-02-14  6:16       ` Claudio Martins
2006-02-14 20:19         ` Mark Fasheh [this message]
2006-02-15  3:17           ` Claudio Martins
2006-02-15 17:50           ` Nohez
2006-02-15 21:42             ` Claudio Martins
2006-02-14 12:17       ` Jan Kara
     [not found] ` <20060210054958.GG4755@ca-server1.us.oracle.com>
2006-02-10  7:11   ` Claudio Martins
  -- strict thread matches above, loose matches on Subject: below --
2006-02-13 15:08 Nohez

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=20060214201946.GD20175@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.com \
    --cc=akpm@osdl.org \
    --cc=ctpm@rnl.ist.utl.pt \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nohez@cmie.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=torvalds@osdl.org \
    /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