From: Amir Goldstein <amir73il@gmail.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: [RFC] exclude_bitmap and uninit_bg features
Date: Wed, 13 Apr 2011 21:03:46 +0200 [thread overview]
Message-ID: <BANLkTimmRQtOiH2iunJczQOhxkB4uoCJ2g@mail.gmail.com> (raw)
Hi Ted,
I have been exploring the possibility to make exclude bitmap a compat feature
and I think I have come to a dead end with ext4_init_block_bitmap().
On old kernels, this function will disregard the exclude bitmap block and leave
it free in the block bitmap.
So that leaves us with the less attractive option to make it rocompat,
which leads to the following dilemma:
Once exclude bitmap is allocated by new mkfs or added by new tune2fs,
the fs can no longer be mounted by an older kernel.
How can we solve that problem?
We could use 2 features:
EXT4_FEATURE_COMPAT_EXCLUDE_BITMAP /* exclude bitmap is allocated */
EXT4_FEATURE_RO_COMPAT_UNINIT_EXCLUDE /* uninit_bg and exclude_bitmap are set */
New mkfs can allocate exclude bitmaps for uninit groups and set the 2
features by default.
tune2fs -O ^uninit_exclude can init all groups and remove the rocompat feature,
making the fs available for old kernels, while keeping the exclude
bitmap intact.
Does that make sense to you?
Amir.
next reply other threads:[~2011-04-13 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 19:03 Amir Goldstein [this message]
2011-04-15 1:54 ` [RFC] exclude_bitmap and uninit_bg features Amir Goldstein
2011-06-20 18:52 ` Amir Goldstein
2011-06-21 1:03 ` Yongqiang Yang
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=BANLkTimmRQtOiH2iunJczQOhxkB4uoCJ2g@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).