mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Claudio Martins <ctpm@rnl.ist.utl.pt>
To: Mark Fasheh <mark.fasheh@oracle.com>
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: Wed, 15 Feb 2006 03:17:56 +0000	[thread overview]
Message-ID: <200602150317.57250.ctpm@rnl.ist.utl.pt> (raw)
In-Reply-To: <20060214201946.GD20175@ca-server1.us.oracle.com>


On Tuesday 14 February 2006 20:19, Mark Fasheh wrote:
>
> 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.1
>6-rc3-mm1/broken-out/git-ocfs2.patch
>

 OK, will do.

>
> 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.

debugfs.ocfs2 1.1.5
debugfs: locate <M0000000000000000d4a94b05ae097f>
13936971        /ctpm/dir2/build-AMD-linux-2.6.16-rc2-git3-jbdfix1/drivers/media/video/cx25840/cx25840-core.c


 This is a file from the kernel build tree I untarred on node 1. So I suppose 
the other two nodes eventually were trying to read it.


Regards

Claudio


  reply	other threads:[~2006-02-15  3:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10  5:36 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
2006-02-15  3:17           ` Claudio Martins [this message]
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
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=200602150317.57250.ctpm@rnl.ist.utl.pt \
    --to=ctpm@rnl.ist.utl.pt \
    --cc=akpm@osdl.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.fasheh@oracle.com \
    --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

all inboxes | Powered by JetHome®