From: Mark Fasheh <mfasheh@suse.de>
To: Richard Weinberger <richard@nod.at>
Cc: Jeff Liu <jeff.liu@oracle.com>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
"ocfs2-users@oss.oracle.com" <ocfs2-users@oss.oracle.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Sunil Mushran <sunil.mushran@gmail.com>
Subject: Re: OCFS2: ocfs2_read_blocks:285 ERROR: block 532737 had the JBD bit set while I was in lock_buffer!
Date: Tue, 3 Sep 2013 12:33:11 -0700 [thread overview]
Message-ID: <20130903193311.GR31381@wotan.suse.de> (raw)
In-Reply-To: <52262980.2050406@nod.at>
On Tue, Sep 03, 2013 at 08:25:04PM +0200, Richard Weinberger wrote:
> >> Hmm, not fun.
> >> In my case I'm not using NFS or any other network filesystem.
> >> The OCFS2 is also used in local mode (no cluster).
> >>
> >> What really worries me is that this another proof that Oracles OCFS2 branch is out of sync with mainline.
> >
> > Can you show me what branch you are talking about here?
>
> https://oss.oracle.com/git/?p=ocfs2-1.4.git seems to contain fixes for years
> which are not mainline.
Ok just FYI I don't believe that to actually be the case - there might be
one or two fixes that were changed when ported to mainline and
there's certainly the possiblity that a mistake was made. But generally
fixes went from mainline into the 1.4 repository and not the other way.
That's not to say things haven't been slow on the Ocfs2 front lately or
anything, but I don't believe it to be the case that fixees are regularly
being put into an Oracle tree that haven't seen mainline.
--Mark
--
Mark Fasheh
prev parent reply other threads:[~2013-09-03 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 20:32 OCFS2: ocfs2_read_blocks:285 ERROR: block 532737 had the JBD bit set while I was in lock_buffer! richard -rw- weinberger
2013-09-03 3:17 ` Jeff Liu
2013-09-03 6:42 ` Richard Weinberger
2013-09-03 8:08 ` Jeff Liu
2013-09-03 17:22 ` Mark Fasheh
2013-09-03 18:25 ` Richard Weinberger
2013-09-03 19:33 ` Mark Fasheh [this message]
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=20130903193311.GR31381@wotan.suse.de \
--to=mfasheh@suse.de \
--cc=jeff.liu@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-users@oss.oracle.com \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
--cc=sunil.mushran@gmail.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).