From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] block64 failure
Date: Wed, 07 Sep 2011 10:10:43 -0700 [thread overview]
Message-ID: <4E67A593.70302@oracle.com> (raw)
All,
So the patches added to allow mounting volumes > 16TB has a problem.
The feature check of the jbd2 superblock is being done before the
jbd2 superblock is actually read.
It is being done after the journal_init_inode() which is incorrect.
ocfs2_check_volume()
ocfs2_journal_init()
jbd2_journal_init_inode()
ocfs2_journal_addressable() <=== check
...
Currently the journal sb is first read during load_journal. Too late for us.
And journal_get_superblock() is not exported.
One solution is to call jbd2_journal_update_format() after jbd2_journal_init_inode().
This function is used by extX to update the journal format from V1 to V2. In our
case, we are always V2 so will be a null op. But will force read the journal sb.
Icky... hence my post.
The other option is exporting journal_get_superblock() to load the journal sb.
Suggestions?
Sunil
next reply other threads:[~2011-09-07 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 17:10 Sunil Mushran [this message]
2011-09-07 17:57 ` [Ocfs2-devel] block64 failure Joel Becker
2011-09-07 18:08 ` Sunil Mushran
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=4E67A593.70302@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.