From: Mingming Cao <cmm@us.ibm.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Missing JBD2_FEATURE_INCOMPAT_64BIT in ext4
Date: Thu, 19 Apr 2007 12:15:00 -0700 [thread overview]
Message-ID: <1177010100.6703.8.camel@dyn9047017103.beaverton.ibm.com> (raw)
In-Reply-To: <20070415161606.GG5967@schatzie.adilger.int>
On Sun, 2007-04-15 at 10:16 -0600, Andreas Dilger wrote:
> Just a quick note before I forget. I thought there was a call in ext4
> to set JBD2_FEATURE_INCOMPAT_64BIT at mount time if the filesystem has
> more than 2^32 blocks?
Question about the online resize case. If the fs is increased to more
than 2^32 blocks, we should set this JBD2_FEATURE_INCOMPAT_64BIT in the
journal. What about existing transactions that still stores 32 bit block
numbers? I guess the journal need to commit them all so that revoke
will not get confused about the bits for block numbers later. After
that done then JBD2 can set this feature safely.
> Cheers, Andreas
> --
> Andreas Dilger
> Principal Software Engineer
> Cluster File Systems, Inc.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-04-19 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 16:16 Missing JBD2_FEATURE_INCOMPAT_64BIT in ext4 Andreas Dilger
2007-04-19 19:15 ` Mingming Cao [this message]
2007-04-19 21:18 ` Andreas Dilger
2007-04-20 0:41 ` Mingming Cao
2007-04-20 5:03 ` Andreas Dilger
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=1177010100.6703.8.camel@dyn9047017103.beaverton.ibm.com \
--to=cmm@us.ibm.com \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.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