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>
Subject: Re: OCFS2 Filesystem inconsistency across nodes
Date: Tue, 14 Feb 2006 00:00:48 +0000	[thread overview]
Message-ID: <200602140000.48593.ctpm@rnl.ist.utl.pt> (raw)
In-Reply-To: <20060213222606.GC20175@ca-server1.us.oracle.com>


On Monday 13 February 2006 22:26, Mark Fasheh wrote:
> On Sat, Feb 11, 2006 at 05:40:57AM +0000, Claudio Martins wrote:
> > This is my /etc/ocfs2/cluster.conf on every node:
>
> Hi Claudio,
> 	Thanks for sending me your config files. Everything seems in order.
> I was easily able to reproduce your problem on my cluster and was able to
> git-bisect my way to some JBD changes which seem to be causing the issue.
> Reverting those patches fixes things. Can you apply the attached patch and
> confirm that it also fixes this particular problem for you? You'll have to
> apply to all kernels in your cluster and either run fsck.ocfs2 or create a
> new file system before testing again.

 Hi Mark,

 I'll apply the patch and rebuild my kernels and filesystem. Will be reporting 
the results ASAP.

Thanks

Claudio

>
> Linus, Andrew, Jan,
> 	OCFS2 uses journal_flush() to sync metadata out to disk when another
> node wants to obtain a lock on an inode which has pending journaled
> changes. Something in Jan Kara's patch titled "jbd: split checkpoint lists"
> broke this for OCFS2 (and I suspect for other users of JBD as well). As a
> result metadata is not always completely flushed to disk by the end of the
> journal_flush() call.


  reply	other threads:[~2006-02-14  0:00 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 [this message]
2006-02-14  6:16       ` Claudio Martins
2006-02-14 20:19         ` Mark Fasheh
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
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=200602140000.48593.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=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®